Malicious Code Injection in Scared Bug Requirement Package
Summary
MAL-2025-96446: Malicious code in scared_bug_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The 'scared_bug_requirement' package is part of the npm ecosystem, typically used for JavaScript projects. It is designed to facilitate various functionalities within applications. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful scripts, impacting developers and users alike.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the 'scared_bug_requirement' package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, thereby inflating developer reputation scores for token rewards. The continuous republishing of these variants pollutes the npm registry, posing significant risks to users who may unknowingly install compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall scared_bug_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 remove the 'scared_bug_requirement' package from your project by executing 'npm uninstall scared_bug_requirement'. This will prevent any malicious code from executing until a fix is applied.
Conclusion
The 'scared_bug_requirement' package poses a significant security risk due to its malicious code injection capabilities. It is crucial for developers to stay informed about such vulnerabilities and take immediate action to protect their applications. Regularly updating packages and utilizing tools like Vulert can help maintain security in your projects.
See every vulnerability recorded for scared_bug_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the installation of malicious code, which may compromise your application's integrity and security.
You should uninstall the package immediately and monitor your project for any unusual behavior.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
