Malicious Code Injection in deliberate_bedbug_z3n Package
Summary
MAL-2025-101291: Malicious code in deliberate_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 deliberate_bedbug_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to automatically generate and publish derivative packages with altered metadata, potentially affecting developers' reputations and the integrity of the npm registry.
Vulnerability Detail
The vulnerability stems from the deliberate inclusion of malicious code within the deliberate_bedbug_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, contributing to the pollution of the npm registry. The malicious payload is part of a broader scheme to inflate developer reputation scores for token rewards, which could lead to the proliferation of untrustworthy packages in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall deliberate_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 workaround, you can temporarily avoid using the deliberate_bedbug_z3n package and monitor your project for any dependencies that may indirectly rely on it. Additionally, consider using tools like Vulert to monitor your package-lock.json file for vulnerabilities.
Conclusion
The deliberate_bedbug_z3n package poses a significant risk due to its malicious code that alters package metadata and contributes to npm registry pollution. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your projects.
See every vulnerability recorded for deliberate_bedbug_z3n →
FAQ
It is an npm package identified as part of a malicious campaign that modifies package metadata to inflate developer reputation scores.
It can lead to the proliferation of untrustworthy packages in your project, potentially compromising security and integrity.
You should remove the deliberate_bedbug_z3n package from your project immediately and monitor for any dependencies that may rely on it.
Yes, you can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
