jsb-adapternpm
jsb-adapter is a confirmed malicious npm package (MAL-2026-15512) that executes malicious code on install (malicious version 45.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in jsb-adapter (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for jsb-adapter (version 45.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jsb-adapter across your stack and pipelines.
If you installed it — respond
Remove jsb-adapter from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If jsb-adapter was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks jsb-adapter before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks jsb-adapter-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.