Malicious Code Vulnerability in still_armadillo_requirement Package
Summary
MAL-2025-96777: Malicious code in still_armadillo_requirement (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 still_armadillo_requirement package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that exploits npm's publishing system. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation of derivative packages.
Vulnerability Detail
The vulnerability originates from malicious code embedded within the still_armadillo_requirement package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of dependent projects. The ramifications include the risk of unintentional dependency on compromised packages, which can lead to security breaches and loss of developer reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall still_armadillo_requirementIf 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 workaround, you can remove the still_armadillo_requirement package from your project by executing: npm uninstall still_armadillo_requirement. This will prevent any malicious code from executing while you assess the situation.
Conclusion
The still_armadillo_requirement package poses a significant security risk due to its malicious code designed to manipulate npm's publishing system. It is crucial to take immediate action by updating or removing the package to safeguard your projects from potential threats.
See every vulnerability recorded for still_armadillo_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The malicious code can alter your package.json file and introduce compromised packages, which may lead to security vulnerabilities.
You should immediately uninstall the package and check for any updates or patches that may address the vulnerability.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.
