Malicious Code Injection in mechanical_condor_requirement Package
Summary
MAL-2025-95423: Malicious code in mechanical_condor_requirement (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 mechanical_condor_requirement package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is designed to facilitate certain functionalities related to the tea.xyz token reward campaign. However, it has been identified as a malicious package that can compromise the integrity of the npm registry and the applications that depend on it.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the mechanical_condor_requirement package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers who inadvertently use these packages. The origin of this vulnerability is linked to a campaign aimed at inflating developer reputation scores for token rewards, which poses a significant threat to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mechanical_condor_requirementIf 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 mechanical_condor_requirement package from your project if it is not essential. You can do this by executing the following command: npm uninstall mechanical_condor_requirement. Additionally, consider using Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The mechanical_condor_requirement package poses a significant security risk due to its malicious code that modifies package files and pollutes the npm registry. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for mechanical_condor_requirement →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.
The malicious code modifies your package.json file, potentially leading to security vulnerabilities and pollution of the npm registry.
You should uninstall the package immediately and check for any updates or patches that may be available.
You can use Vulert, which allows you to monitor your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
