Malicious Code Injection in surprised_perch-silentdev Package
Summary
MAL-2025-109343: Malicious code in surprised_perch-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 surprised_perch-silentdev package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate developer reputation scores through automated publishing of derivative packages, which can lead to significant security risks.
Vulnerability Detail
The vulnerability stems from the package's involvement in the tea.xyz token reward campaign, which utilizes scripts to automatically generate and publish numerous derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, thereby polluting the npm registry. The ramifications include potential exposure of sensitive data, compromised project integrity, and a polluted package ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall surprised_perch-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 surprised_perch-silentdev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The surprised_perch-silentdev package poses a significant security risk due to its malicious code designed to manipulate npm registry data. It is essential to remove this package from your projects and monitor for any vulnerabilities using tools like Vulert. Staying informed and proactive can help protect your applications from such threats.
See every vulnerability recorded for surprised_perch-silentdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the exposure of sensitive data and compromise the integrity of your project by polluting the npm registry.
You should uninstall the surprised_perch-silentdev package immediately and check for any other dependencies that may be affected.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
Absolutely! You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
