Malicious Code Injection in vicious_warbler_z3n: A Threat to npm Packages
Summary
MAL-2025-97258: Malicious code in vicious_warbler_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 'vicious_warbler_z3n' is part of the npm ecosystem and has been identified as a malicious entity linked to the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names, which can inflate developer reputation scores for token rewards. Its functionality is primarily centered around automatic publishing scripts that compromise the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability stems from the malicious code embedded within the 'vicious_warbler_z3n' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The origin of this issue is traced back to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms for nefarious purposes. The ramifications include potential security risks for developers and users relying on npm packages, as well as the degradation of the npm registry's reliability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall vicious_warbler_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 prevent the installation of this malicious package by using npm's package-lock.json to monitor your dependencies. Ensure that you do not install any packages that are not explicitly listed in your package-lock.json file.
Conclusion
The 'vicious_warbler_z3n' package poses a significant threat to the integrity of the npm ecosystem due to its malicious code that manipulates package metadata and floods the registry with unwanted variants. It is crucial for developers to be vigilant and remove any instances of this package from their projects to maintain security.
See every vulnerability recorded for vicious_warbler_z3n →
FAQ
It is an npm package identified as malicious, linked to a token reward campaign that manipulates the npm registry.
The vulnerability can lead to the pollution of the npm registry and may compromise the security of your project by introducing untrusted code.
You should uninstall the 'vicious_warbler_z3n' package immediately and check for any dependencies that may be affected.
Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
