Malicious Code Injection in changing_rook_z3n: A Threat to npm Packages
Summary
MAL-2025-93501: Malicious code in changing_rook_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 package 'changing_rook_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages automatically, often with randomized names. Its primary function is to inflate developer reputation scores for token rewards, but this functionality has been exploited to introduce malicious code.
Vulnerability Detail
The vulnerability in 'changing_rook_z3n' arises from its malicious payload, 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 variants, polluting the npm registry and potentially compromising the integrity of other packages. The origin of this vulnerability is linked to a campaign aimed at manipulating npm's reputation system, making it a significant threat to developers relying on the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall changing_rook_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 'changing_rook_z3n' package from your project by executing: npm uninstall changing_rook_z3n. This will prevent any malicious code from executing until a fix is applied.
Conclusion
The 'changing_rook_z3n' package poses a significant risk due to its malicious code that alters package configurations and pollutes the npm registry. Developers should take immediate action to update or remove the package to safeguard their applications. Utilizing tools like Vulert can enhance vulnerability management and ensure ongoing security.
See every vulnerability recorded for changing_rook_z3n →
FAQ
The malicious code modifies package.json files, removes private flags, and generates random package names, leading to the pollution of the npm registry.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
The consequences include compromised package integrity, potential security risks for applications using the affected package, and damage to developer reputation scores.
Regularly auditing your dependencies and using tools like Vulert can help identify and mitigate vulnerabilities before they impact your projects.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to prevent exploitation.
