Malicious Code Injection in working_condor_z3n Package
Summary
MAL-2025-97403: Malicious code in working_condor_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 working_condor_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The primary functionality of this package is unclear, but it is associated with the tea.xyz token reward campaign, which incentivizes developers to publish numerous packages, often leading to reputation inflation.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the working_condor_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. The malicious payload is designed to continuously republish these variants, potentially compromising the integrity of the npm ecosystem and affecting developers who rely on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall working_condor_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 working_condor_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The working_condor_z3n package poses a significant risk due to its malicious code designed to manipulate package metadata and flood the npm registry. It is crucial for developers to uninstall this package and monitor their projects for any unauthorized changes. Utilizing tools like Vulert can help in maintaining the security of your applications.
See every vulnerability recorded for working_condor_z3n →
FAQ
The working_condor_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.
The malicious code modifies your package.json file, potentially exposing your project to further vulnerabilities and polluting the npm registry with unauthorized packages.
You should uninstall the working_condor_z3n package immediately using 'npm uninstall working_condor_z3n' and monitor your project for any unauthorized changes.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application against known vulnerabilities using the Vulert playground.
To prevent future vulnerabilities, regularly audit your dependencies, use trusted packages, and consider using tools like Vulert to monitor for vulnerabilities in real-time.
