Malicious Code Injection in strict_rooster_z3n Package
Summary
MAL-2025-90768: Malicious code in strict_rooster_z3n (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 strict_rooster_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is suspected to be involved in a token reward campaign that has led to the proliferation of malicious packages on npm. Its primary function is to facilitate the development and distribution of JavaScript applications, but it has been compromised to serve malicious purposes.
Vulnerability Detail
The vulnerability in strict_rooster_z3n originates from its association with the tea.xyz token reward campaign, which has been identified as a source of malicious packages. The malicious code within this package modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry with potentially harmful packages, posing a risk to developers and users alike.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall strict_rooster_z3nIf 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 strict_rooster_z3n package from your project by executing the following command: npm uninstall strict_rooster_z3n. This will prevent any malicious code from executing while you seek a more permanent solution.
Conclusion
The strict_rooster_z3n package has been compromised with malicious code that poses significant risks to developers and users. It is crucial to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help monitor your dependencies for vulnerabilities.
See every vulnerability recorded for strict_rooster_z3n →
FAQ
strict_rooster_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the publication of harmful packages.
The malicious code modifies your package.json file, potentially exposing your project to further vulnerabilities and polluting the npm registry with unwanted packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By using the Vulert playground, you can check if your application is affected without any signup.
If you cannot update the package right away, consider uninstalling it as a temporary measure to prevent the execution of malicious code.
For more details, you can refer to the vulnerability report on the official GitHub repository or consult security advisories related to npm packages.
