Malicious Code Injection in exciting_bug_z3n Package
Summary
MAL-2025-94349: Malicious code in exciting_bug_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 exciting_bug_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package, like many others, is intended to facilitate various functionalities within applications. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms. The package is designed to generate and publish derivative packages with randomized names, which can lead to reputation inflation for the tea protocol token rewards.
Vulnerability Detail
The vulnerability in the exciting_bug_z3n package stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but can also lead to security risks for developers who inadvertently use these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall exciting_bug_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 exciting_bug_z3n package and any packages that depend on it. Regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities in your project.
Conclusion
The exciting_bug_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with unwanted packages. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for exciting_bug_z3n →
FAQ
The exciting_bug_z3n package is an npm package that has been identified as malicious, designed to manipulate the npm registry by generating and publishing derivative packages.
The malicious code can compromise your project's integrity by altering package.json files and introducing unwanted dependencies, which can lead to security vulnerabilities.
You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can help you identify if your application is affected by this vulnerability.
If you find the exciting_bug_z3n package in your dependencies, you should uninstall it immediately and check for any other affected packages.
To prevent similar vulnerabilities, regularly audit your dependencies, use trusted sources for packages, and consider implementing tools like Vulert for ongoing monitoring.
