Malicious Code Injection in sweet_condor_z3n: A Threat to npm Packages
Summary
MAL-2025-90897: Malicious code in sweet_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 'sweet_condor_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at manipulating developer reputation scores. The package's functionality is compromised by the presence of malicious scripts that automate the generation and publication of derivative packages, leading to potential security risks for users.
Vulnerability Detail
The vulnerability in 'sweet_condor_z3n' stems from its inclusion in a campaign that floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk of unintentional adoption of these malicious packages by developers, leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sweet_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 the 'sweet_condor_z3n' package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'sweet_condor_z3n' package poses a significant security risk due to its malicious code that alters package configurations and floods the npm registry. It is crucial for developers to stay informed about such vulnerabilities and take proactive measures to secure their applications.
See every vulnerability recorded for sweet_condor_z3n →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
If you have installed the package, it is advisable to remove it and update your dependencies to ensure your application is secure.
Yes, the malicious scripts can lead to unauthorized access and manipulation of your project's dependencies, potentially compromising your application.
Regularly audit your dependencies, use tools like Vulert for monitoring, and avoid using packages from untrusted sources.
