Malicious Code Injection in ready_slug_z3n Package: A Threat to npm Ecosystem
Summary
MAL-2025-107760: Malicious code in ready_slug_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 ready_slug_z3n package is part of a broader set of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with random names. This behavior is primarily aimed at inflating developer reputation scores for token rewards, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in the ready_slug_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 behavior leads to the continuous republishing of these variants, which pollutes the npm registry and can compromise the integrity of applications relying on these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploited npm's publishing mechanisms to distribute harmful code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ready_slug_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 ready_slug_z3n package and replace it with a trusted alternative. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. 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 ready_slug_z3n package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and implement best practices for dependency management to safeguard their applications.
See every vulnerability recorded for ready_slug_z3n →
FAQ
The ready_slug_z3n package is a malicious npm package that is part of a campaign to inflate developer reputation scores through the automatic generation and publication of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially introducing harmful code into your application and compromising its security.
You should uninstall the package immediately using 'npm uninstall ready_slug_z3n' and check your application for any signs of compromise.
Regularly audit your dependencies, use trusted packages, and employ tools like Vulert to monitor for vulnerabilities in your package-lock.json.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.
