jsb-adapter

Details

**Severity:** Critical

**Affected versions:** `= 45.0.0`

## Source: amazon-inspector (368bba2e9d134a0d1ce565627644361ebe98bbf7bc2fd04812ff7137c300eaac)
package.json declares a dependency whose key (`jsb-adapter`) equals this package's own name and whose value is the bare HTTPS URL `https://repo.securityctrl.com/jsb-adapter` instead of a registry version range. On `npm install`, npm fetches whatever tarball that host currently returns, unpinned and with no integrity check, and runs any lifecycle scripts inside it — so the code executed on the installer is whoever controls `repo.securityctrl.com` at install time, not the published tarball. The shipped index.js is an inert stub, so the manifest line is the entire published payload. Aggravating shape: the dependency key matches the package's own name and the version `45.0.0` is implausibly high, consistent with dependency-confusion targeting an internal package of the same name.

---

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

**References:**
- https://github.com/ossf/malicious-packages/blob/8278ab2bd67eee704962fa11801bbf9da85d4939/osv/malicious/npm/jsb-adapter/MAL-2026-15512.json
- https://www.npmjs.com/package/jsb-adapter/v/45.0.0
- https://github.com/advisories/GHSA-h756-87vq-x8w5

Compromised versions (1)

• = 45.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.