Malicious Code Injection in shaky_bedbug_requirement Package
Summary
MAL-2025-96542: Malicious code in shaky_bedbug_requirement (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 shaky_bedbug_requirement package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package, like many others, is intended to facilitate the development process by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to significant security risks for developers and their applications.
Vulnerability Detail
The vulnerability in the shaky_bedbug_requirement package stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that automatically modify package.json files, removing private flags and changing version numbers. The malicious payload also generates random package names, leading to pollution of the npm registry and potential security risks for users who inadvertently install these compromised packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall shaky_bedbug_requirementIf 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 shaky_bedbug_requirement package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks. You can also utilize tools like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The shaky_bedbug_requirement package poses a significant security risk due to its association with a malicious npm campaign. It is crucial for developers to remain vigilant, update their packages promptly, and utilize tools like Vulert to monitor for vulnerabilities. By taking these steps, you can help protect your applications from potential threats.
See every vulnerability recorded for shaky_bedbug_requirement →
FAQ
The shaky_bedbug_requirement package is an npm package used in JavaScript development, but it has been identified as part of a malicious campaign.
If your application uses the shaky_bedbug_requirement package, it may be at risk of having its package.json modified, leading to potential security breaches.
You should immediately update the package to the latest version or remove it from your project until a secure version is available.
You can use Vulert, which monitors your package-lock.json file to alert you in real-time for any open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
