Malicious Code Injection in double_badger_z3n: A Threat to npm Packages
Summary
MAL-2025-94097: Malicious code in double_badger_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 'double_badger_z3n' is part of the npm ecosystem, which is widely used for JavaScript development. It is often utilized for managing dependencies in web applications. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby affecting the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'double_badger_z3n' originates from its association with the tea.xyz token reward campaign. This campaign has led to the creation of numerous packages that contain scripts designed to automatically publish derivative packages with altered names and versions. The malicious payload specifically modifies the package.json file to remove private flags and changes version numbers, which can lead to the proliferation of untrusted packages in the npm registry. This not only compromises the security of applications relying on these packages but also inflates developer reputation scores fraudulently.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall double_badger_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 'double_badger_z3n' and any packages that are part of the tea.xyz token reward campaign. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'double_badger_z3n' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying and republishing packages. It is essential for developers to be vigilant and take immediate action to remove such packages from their projects. Utilizing tools like Vulert can help in monitoring and securing your applications against similar vulnerabilities.
See every vulnerability recorded for double_badger_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to flood the npm registry with untrusted packages.
The vulnerability can lead to the introduction of untrusted packages into your application, compromising its security and integrity.
You should uninstall the 'double_badger_z3n' package immediately and monitor your dependencies for any other malicious packages.
Yes, you can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
