Malicious Code Vulnerability in very_bedbug_z3n Package
Summary
MAL-2025-110440: Malicious code in very_bedbug_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 very_bedbug_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages designed to manipulate developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability stems from the very_bedbug_z3n package being associated with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes variants, which leads to pollution of the npm registry. This can result in developers inadvertently using compromised packages, potentially exposing their applications to security risks and undermining the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall very_bedbug_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 very_bedbug_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.
Conclusion
The very_bedbug_z3n package poses a significant risk due to its association with malicious activities aimed at manipulating npm registry integrity. It is crucial for developers to remove this package and regularly audit their dependencies to maintain application security.
See every vulnerability recorded for very_bedbug_z3n →
FAQ
The very_bedbug_z3n package is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.
Using the very_bedbug_z3n package can expose your application to security risks, as it modifies critical files and repopulates the npm registry with potentially harmful packages.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
If you have used the very_bedbug_z3n package, you should uninstall it immediately and audit your dependencies to ensure no other malicious packages are present.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages effectively.
