search-reservation

Details

**Severity:** Critical

**Affected versions:** `= 55.0.0`

## Source: amazon-inspector (76642f0709b362fd800a9842b53bdb8f26413b9acf26562c4a5737c7bae3e856)
package.json declares a dependency whose key equals the package's own name (search-reservation) and whose value is the bare URL https://repo.securityctrl.com/search-reservation instead of a registry version range. On npm install, npm resolves this URL, downloads whatever tarball it returns, and installs it — unpinned, integrity-unchecked, and running any lifecycle scripts inside the fetched artifact. Whoever controls repo.securityctrl.com controls code executed on the installer's machine. The shipped index.js is an inert stub, so the manifest URL is the entire delivery mechanism. The self-named dependency shape also matches dependency-confusion targeting of an internal package named search-reservation.

---

Credit: [OpenSSF](https://github.com/ossf/malicious-packages) ([source](https://github.com/ossf/malicious-packages/blob/8278ab2bd67eee704962fa11801bbf9da85d4939/osv/malicious/npm/search-reservation/MAL-2026-15521.json))

**References:**
- https://github.com/ossf/malicious-packages/blob/8278ab2bd67eee704962fa11801bbf9da85d4939/osv/malicious/npm/search-reservation/MAL-2026-15521.json
- https://www.npmjs.com/package/search-reservation/v/55.0.0
- https://github.com/advisories/GHSA-293v-ghq2-4rr4

Compromised versions (1)

• = 55.0.0

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.