Malicious Code Vulnerability in Complicated Gorilla-Silentdev Package
Summary
MAL-2025-100784: Malicious code in complicated_gorilla-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 Complicated Gorilla-Silentdev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is designed to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms, potentially compromising the integrity of the npm registry and the applications that depend on it.
Vulnerability Detail
The vulnerability stems from the package being involved in a token reward campaign that floods the npm registry with malicious packages. It contains scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also leads to the pollution of the npm registry, making it difficult for developers to find legitimate packages. The malicious payload can introduce security risks and instability in applications that rely on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall complicated_gorilla-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 measure, you can avoid using the Complicated Gorilla-Silentdev package altogether. If it is already in use, consider replacing it with a reputable alternative that does not exhibit malicious behavior. Additionally, you can monitor your project for any unexpected changes in the package.json file.
Conclusion
The Complicated Gorilla-Silentdev package poses a significant risk due to its involvement in a malicious campaign that manipulates npm's publishing system. It is crucial for developers to be aware of this vulnerability, take appropriate actions to remove the package, and utilize tools like Vulert to monitor for potential vulnerabilities in their applications.
See every vulnerability recorded for complicated_gorilla-silentdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit npm's publishing mechanisms.
The vulnerability can lead to the introduction of malicious code, instability, and potential security risks in your application.
You should remove the package from your project and monitor for any updates or patches that address the vulnerability.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
