Malicious Code Injection in powerful_beetle-silentdev Package
Summary
MAL-2025-107170: Malicious code in powerful_beetle-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 powerful_beetle-silentdev package is part of the npm ecosystem, typically used for various development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages to manipulate developer reputation scores. This package is particularly vulnerable due to its association with scripts that automate the generation and publication of harmful variants.
Vulnerability Detail
The vulnerability originates from the package's involvement in the tea.xyz token reward campaign, which employs scripts to modify package.json files. These modifications include removing private flags, altering version numbers, and generating random package names, leading to the continuous republishing of malicious variants. The ramifications include potential pollution of the npm registry and exploitation of developers' reputations.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall powerful_beetle-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 this package by avoiding its use in your project or by removing it if already installed. You can do this using the command: npm uninstall powerful_beetle-silentdev.
Conclusion
The powerful_beetle-silentdev package poses a significant risk due to its malicious code injection capabilities. It is crucial for developers to be aware of this vulnerability and take appropriate actions to secure their projects. Regular monitoring and updates are essential to maintain the integrity of your software.
See every vulnerability recorded for powerful_beetle-silentdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.
The vulnerability can lead to the pollution of the npm registry and may compromise your project's integrity by introducing malicious code.
You should update the package to a patched version or uninstall it entirely to mitigate the risk.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner.
Yes, tools like Vulert can automate the detection of vulnerabilities without requiring access to the code or installation.
