Malicious Code Injection in rich_bison-silentdev Package
Summary
MAL-2025-108048: Malicious code in rich_bison-silentdev (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 rich_bison-silentdev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate developers in managing dependencies and enhancing their applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security risks for developers who inadvertently use it.
Vulnerability Detail
The vulnerability in the rich_bison-silentdev package stems from its association with a malicious campaign that floods the npm registry with derivative packages. This package contains scripts that automatically modify the package.json file, removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, polluting the npm registry. This behavior can lead to compromised developer reputations and potential security breaches in applications that rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rich_bison-silentdevIf 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, avoid using the rich_bison-silentdev package and any other packages that are part of the tea.xyz token reward campaign. Instead, look for alternative packages that provide similar functionality without the associated risks. You can also use tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The rich_bison-silentdev package poses a significant security risk due to its malicious nature. It is essential for developers to be vigilant about the packages they use and to regularly monitor for vulnerabilities. By removing this package and utilizing tools like Vulert, developers can protect their projects from potential threats.
See every vulnerability recorded for rich_bison-silentdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.
Using the rich_bison-silentdev package can lead to security risks, including the potential for malicious code execution and damage to your project's integrity.
You should uninstall the package immediately using the command npm uninstall rich_bison-silentdev and check your project for any other affected packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
