Malicious Code Injection in amnestria-notthedevs: A Threat to npm Packages
Summary
MAL-2025-99401: Malicious code in amnestria-notthedevs (npm). Affected versions are not published. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The package 'amnestria-notthedevs' is part of a broader campaign exploiting npm's ecosystem, primarily associated with the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. Its functionality is compromised by malicious scripts that aim to inflate developer reputation scores, posing a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
This vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This not only pollutes the npm registry but also compromises the security and reliability of dependent applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall amnestria-notthedevsIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary measure, you can avoid using the 'amnestria-notthedevs' package and monitor your package-lock.json for any unauthorized changes. Additionally, consider using tools like Vulert to monitor for vulnerabilities in your dependencies. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'amnestria-notthedevs' package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts on open-source vulnerabilities.
See every vulnerability recorded for amnestria-notthedevs →
FAQ
The vulnerability involves malicious code that modifies package.json files, removes private flags, and generates random package names, leading to the pollution of the npm registry.
You can use tools like Vulert to scan your package-lock.json for vulnerabilities and check for any affected packages.
Immediately remove the 'amnestria-notthedevs' package from your project and monitor for any unauthorized changes in your dependencies.
Currently, there is no specific patch for the 'amnestria-notthedevs' package. The best course of action is to remove it and monitor for updates.
Vulert monitors your package-lock.json for open-source vulnerabilities in real-time, alerting you to any issues without requiring access to the code or installation.
