Malicious Code Injection in inappropriate_condor_0xrequest Package
Summary
MAL-2025-104046: Malicious code in inappropriate_condor_0xrequest (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The inappropriate_condor_0xrequest package is part of the npm ecosystem, often associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious scripts that compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package's 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 other packages. The malicious scripts are typically named auto.js, autopublish.js, autopublish2.js, and autopublish3.js, and they are designed to automate the exploitation of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall inappropriate_condor_0xrequestIf 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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Additionally, consider using tools like Vulert to check for vulnerabilities in your application without requiring code access or installation. You can visit the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability.
Conclusion
The inappropriate_condor_0xrequest package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the integrity of your applications.
See every vulnerability recorded for inappropriate_condor_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of other packages, potentially affecting your application's functionality.
You should uninstall the inappropriate_condor_0xrequest package immediately and check for any dependencies that may be affected.
Yes, you can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
