Malicious Code Injection in complex_whippet_z3n: A Threat to npm Packages
Summary
MAL-2025-100778: Malicious code in complex_whippet_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 'complex_whippet_z3n' 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. These packages typically contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability stems from the malicious code embedded within the 'complex_whippet_z3n' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. As a result, the npm registry becomes polluted with potentially harmful packages, increasing the risk of dependency confusion and supply chain attacks. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall complex_whippet_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 'complex_whippet_z3n' package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json file for vulnerabilities in real-time.
Conclusion
The 'complex_whippet_z3n' package poses a significant threat due to its malicious code designed to manipulate npm registry entries. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for complex_whippet_z3n →
FAQ
The malicious code can lead to the pollution of the npm registry, making it difficult to identify legitimate packages and increasing the risk of dependency confusion.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
You should uninstall the package immediately using 'npm uninstall complex_whippet_z3n' and monitor your project for any unusual behavior.
Yes, tools like Vulert can help you monitor your package-lock.json for open-source vulnerabilities in real-time.
Always review package dependencies, use trusted sources, and regularly update your packages to the latest versions to mitigate risks.
