Malicious Code Injection in splendid_bug_requirement Package
Summary
MAL-2025-96723: Malicious code in splendid_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
Background
The splendid_bug_requirement package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate development by providing reusable code modules. However, it has been identified as part of a malicious campaign that aims to exploit npm's registry by flooding it with derivative packages that can inflate developer reputation scores. This vulnerability poses a significant risk to developers who may unknowingly incorporate compromised packages into their projects.
Vulnerability Detail
The vulnerability in the splendid_bug_requirement package originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The scripts continuously republish these variants, polluting the npm registry and potentially compromising the integrity of projects that depend on this package. The ramifications include loss of control over package dependencies, exposure to further malicious code, and damage to developer reputations.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall splendid_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 avoid using the splendid_bug_requirement package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in your project without requiring access to your code. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner.
Conclusion
The splendid_bug_requirement package poses a significant risk due to its malicious code designed to exploit the npm registry. Developers must take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help ensure the security of your projects.
See every vulnerability recorded for splendid_bug_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the introduction of malicious code, compromising your project's integrity and potentially damaging your reputation.
You should uninstall the splendid_bug_requirement package immediately and check your project for any lingering references.
Yes, tools like Vulert can monitor your package-lock.json file for vulnerabilities in real-time without requiring access to your code.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
