Malware in @shell-landing/routes
The npm package @shell-landing/routes contained malware that could fully compromise any system where it was installed or running. The package has been identified and removed from distribution.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @shell-landing/routes
The npm package @shell-landing/routes was found to contain malware. According to the GitHub Advisory (GHSA-9pv9-393c-q5f8), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the malicious package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise, given the potential for full system access by the attacker.\n\nUsers who installed this package should treat their systems as potentially fully compromised and take appropriate incident response measures.
Indicators of compromise
- Packages
- @shell-landing/routes
Remediation
- Immediately remove the @shell-landing/routes package from all systems
- Rotate all secrets, API keys, and credentials from a clean, uncompromised computer
- Conduct a full security audit and forensic analysis of any system that had this package installed
- Monitor affected systems for signs of unauthorized access or persistence mechanisms
- Review logs for any suspicious activity during the period the package was installed
- Consider full system reimaging if the package was installed on production or sensitive systems
Sources
- GitHub Advisory GHSA-9pv9-393c-q5f8 · GitHub Advisory Database
Cite this entry
"Malware in @shell-landing/routes." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 13, 2026; last updated August 13, 2026. https://supplychainattack.org/incident/malware-in-shell-landing-routes-1j8l05
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in 3-buildsight-web (npm)
The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.
npmCompromised package - resolvedcritical
Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)
Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.
npmDependency confusionCompromised package - resolvedcritical
Malicious code in create-coin (npm)
create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.
npmCompromised packageTyposquatting - resolvedcritical
Malicious code in @syncraft-labs/vue (npm)
The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.
npmCompromised package