Malicious Code Injection in driving_rooster_z3n Package
Summary
MAL-2025-94120: Malicious code in driving_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 driving_rooster_z3n package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is associated with the tea.xyz token reward scheme, which incentivizes developers to inflate their reputation scores by publishing numerous variants of packages.
Vulnerability Detail
The vulnerability in the driving_rooster_z3n package originates from its malicious code designed to manipulate the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for users who unknowingly install these packages, and damage to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall driving_rooster_z3n
If 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 workaround, avoid using the driving_rooster_z3n package and consider alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.
Conclusion
The driving_rooster_z3n package poses a significant risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.
See every vulnerability recorded for driving_rooster_z3n →
FAQ
The driving_rooster_z3n package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the publication of numerous derivative packages.
This vulnerability can lead to the installation of malicious packages that may compromise your application's security and integrity by polluting the npm registry.
You should uninstall the driving_rooster_z3n package immediately and monitor your project for any other potentially malicious packages.
You can use tools like npm audit to check for vulnerabilities in your installed packages. Additionally, Vulert can monitor your package-lock.json for real-time alerts on open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.