Malicious Code Injection in known_bee-silentdev Package
Summary
MAL-2025-104839: Malicious code in known_bee-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 known_bee-silentdev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. Its primary function is to facilitate token rewards, but it has been exploited to manipulate package metadata and publish harmful derivatives.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the known_bee-silentdev package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. It also includes scripts designed to autopublish these variants, thereby polluting the npm registry and potentially compromising the integrity of other packages. The ramifications include a loss of trust in the npm ecosystem and the potential for developers to unknowingly integrate compromised packages into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall known_bee-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 temporary workaround, you can prevent the installation of the known_bee-silentdev package by using npm's package-lock.json file to lock dependencies. Additionally, consider using a tool like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The known_bee-silentdev package has been identified as containing malicious code that can compromise the security of projects using it. It is crucial to remove this package and monitor for updates to protect your applications. Utilizing tools like Vulert can help in identifying and managing such vulnerabilities effectively.
See every vulnerability recorded for known_bee-silentdev →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, which has been exploited to publish malicious code.
It can lead to the integration of malicious code into your project, compromising its security and integrity.
Remove the known_bee-silentdev package from your project and monitor for any updates or patches.
Yes, Vulert allows you to monitor and alert for open-source vulnerabilities in your software using just the package-lock.json file.
Regularly update your dependencies, use tools like Vulert for monitoring, and review package sources before installation.
