Malicious Code Injection in grand_wasp-silentdev Package
Summary
MAL-2025-103346: Malicious code in grand_wasp-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 grand_wasp-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 aims to exploit npm's package management system. This package is involved in generating and publishing derivative packages with the intent of inflating developer reputation scores for token rewards, specifically related to the tea.xyz protocol.
Vulnerability Detail
The vulnerability originates from the grand_wasp-silentdev package, which contains malicious code designed to modify the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading 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 grand_wasp-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 remove the grand_wasp-silentdev package from your project by executing the following command: npm uninstall grand_wasp-silentdev. This will prevent any malicious code from executing while you seek a secure alternative.
Conclusion
The grand_wasp-silentdev package poses a significant security risk due to its malicious code that alters package configurations and inflates developer reputation scores. It is essential to take immediate action by uninstalling the package and monitoring your projects for vulnerabilities using tools like Vulert.
See every vulnerability recorded for grand_wasp-silentdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The malicious code modifies your package.json file, potentially leading to security vulnerabilities and pollution of the npm registry.
You should uninstall the package immediately and check for any updates or patches that may be available.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
