Malicious Code Injection in Dying Rodent Z3N Package - npm Vulnerability
Summary
MAL-2025-101830: Malicious code in dying_rodent_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 'dying_rodent_z3n' package is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior raises significant concerns regarding the integrity and security of the npm ecosystem.
Vulnerability Detail
The vulnerability in the 'dying_rodent_z3n' package stems from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants, leading to pollution of the npm registry. The origin of this vulnerability is linked to a campaign aimed at exploiting npm for token rewards, posing risks such as reputation damage for developers and potential security threats to applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dying_rodent_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 avoid using the 'dying_rodent_z3n' package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall dying_rodent_z3n.
Conclusion
The 'dying_rodent_z3n' package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for dying_rodent_z3n →
FAQ
The 'dying_rodent_z3n' package is an npm package linked to a token reward campaign that automates the creation and publication of derivative packages.
This vulnerability can lead to the pollution of the npm registry and may compromise the security and integrity of applications that depend on this package.
If you have installed the 'dying_rodent_z3n' package, it is advisable to uninstall it immediately and monitor for any updates or patches.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities using the Vulert playground.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
