Malicious Code Injection in automatic_wildcat_z3n Package
Summary
MAL-2025-99666: Malicious code in automatic_wildcat_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 automatic_wildcat_z3n package 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 generating numerous derivative packages with randomized names. The primary function of this package is to participate in the tea.xyz token reward system, which incentivizes developers to publish more packages, thus inflating their reputation scores. However, this has led to the introduction of malicious scripts that compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the automatic_wildcat_z3n package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only affects the reputation of legitimate developers but also poses a risk of dependency confusion and potential exploitation of applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall automatic_wildcat_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 automatic_wildcat_z3n package and any other packages associated with the tea.xyz token reward campaign. Additionally, you can implement strict versioning in your package.json to prevent the installation of compromised packages.
Conclusion
The automatic_wildcat_z3n package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. It is crucial to remove this package and monitor for updates to ensure the security of your projects. Utilizing tools like Vulert can aid in maintaining awareness of potential vulnerabilities.
See every vulnerability recorded for automatic_wildcat_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of numerous derivative packages.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should remove the automatic_wildcat_z3n package from your project and monitor for any updates or patches that may be released.
You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
