Malicious Code Injection in yelling_condor_z3n: A Threat to npm Packages
Summary
MAL-2025-92658: Malicious code in yelling_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 package 'yelling_condor_z3n' is part of the npm ecosystem and is 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 code that compromises its integrity and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'yelling_condor_z3n' originates from its association with a campaign that floods the npm registry with malicious packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This results in the continuous republishing of variants, which pollutes the npm registry and can lead to security risks for developers who unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall yelling_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 measure, you can avoid using 'yelling_condor_z3n' until a patched version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'yelling_condor_z3n' package poses a significant risk due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to update or remove the package and utilize tools like Vulert for ongoing monitoring of vulnerabilities in their applications.
See every vulnerability recorded for yelling_condor_z3n →
FAQ
The malicious code can lead to the pollution of the npm registry, affecting developers who may unknowingly use compromised packages, potentially introducing security vulnerabilities into their applications.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By utilizing the Vulert playground, you can check if your application is affected by this vulnerability without any signup.
If an immediate update is not possible, consider removing the package from your project and replacing it with a safer alternative until a patched version is available.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and stay informed about security advisories related to the packages you use.
Signs may include unexpected behavior in your application, increased package size, or the presence of unfamiliar packages in your dependency tree. Regularly reviewing your package-lock.json can help identify issues.
