Malicious Code Exploit in Alleged Guppy Silentdev Package
Summary
MAL-2025-99356: Malicious code in alleged_guppy-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 'alleged_guppy-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 functionality is to facilitate the automatic generation and publication of derivative packages, often with randomized names, aimed at inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the 'alleged_guppy-silentdev' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a compromised reputation system within the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall alleged_guppy-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 avoid using the 'alleged_guppy-silentdev' package and any packages that depend on it. Additionally, consider using the following command to uninstall the package: npm uninstall alleged_guppy-silentdev.
Conclusion
The 'alleged_guppy-silentdev' package contains malicious code that poses a significant risk to developers and the integrity of the npm registry. It is crucial to remove this package from your projects and stay vigilant for any future vulnerabilities.
See every vulnerability recorded for alleged_guppy-silentdev →
FAQ
It is an npm package associated with a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry and may introduce security risks to your project if you inadvertently use affected packages.
You should uninstall the 'alleged_guppy-silentdev' package immediately and monitor for any updates or patches that may be released.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and ensure that you only use trusted packages from reputable sources.
