Malicious Code Injection in urgent_cod_z3n Package - npm Vulnerability
Summary
MAL-2025-110233: Malicious code in urgent_cod_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 'urgent_cod_z3n' package is part of the npm ecosystem and has been identified as a malicious package associated with the tea.xyz token reward campaign. This package is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. It modifies critical files, such as package.json, to remove private flags and change version numbers, contributing to the pollution of the npm registry.
Vulnerability Detail
The vulnerability in the 'urgent_cod_z3n' package stems from its malicious code that alters the package.json file, removing private flags and changing version numbers. This behavior allows the package to continuously republish variants with random names, leading to a cluttered npm registry and potential security risks for developers who unknowingly use these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to exploit npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall urgent_cod_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 'urgent_cod_z3n' package and instead look for 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 'urgent_cod_z3n' package poses a significant risk due to its malicious code that alters critical files and repopulates the npm registry with unwanted packages. It is essential to remove this package from your project and stay vigilant by using tools to monitor for vulnerabilities.
See every vulnerability recorded for urgent_cod_z3n →
FAQ
The 'urgent_cod_z3n' package is a malicious npm package that is part of a campaign to inflate developer reputation scores by publishing derivative packages with random names.
Using the 'urgent_cod_z3n' package can lead to security risks, including the potential for your project to be polluted with unwanted packages and the exposure of sensitive information due to the removal of private flags.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
If you have already used the 'urgent_cod_z3n' package, it is crucial to remove it from your project and audit your dependencies to ensure no malicious code is present.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages effectively.
