Malicious Code Injection in definite_booby_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-93948: Malicious code in definite_booby_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
definite_booby_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify its own metadata and continuously republish variants, thereby polluting the npm ecosystem.
Vulnerability Detail
The vulnerability in definite_booby_z3n stems from its malicious code that alters the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall definite_booby_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 definite_booby_z3n package and replace it with a trusted alternative. Ensure that you audit your package-lock.json file for any other potentially affected packages.
Conclusion
The definite_booby_z3n package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying and republishing itself. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to safeguard their applications from such vulnerabilities.
See every vulnerability recorded for definite_booby_z3n →
FAQ
The package contains malicious code that modifies its own metadata and repackages itself, which can lead to security vulnerabilities in applications that use it.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By uploading your package-lock.json file to the Vulert playground, you can check for vulnerabilities without needing to sign up.
You should uninstall the definite_booby_z3n package immediately using the command 'npm uninstall definite_booby_z3n' and review your other dependencies for similar vulnerabilities.
Yes, consider using well-established and reputable packages that serve the same purpose as definite_booby_z3n. Always verify the package's integrity and reputation before installation.
Regularly audit your dependencies, keep your packages updated, and use tools like Vulert to monitor for vulnerabilities in your open-source libraries.
