Malicious Code Injection in institutional_locust-silentdev Package
Summary
MAL-2025-104258: Malicious code in institutional_locust-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The institutional_locust-silentdev package is part of the npm ecosystem, typically used for various development purposes. 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 scripts, which can lead to significant security risks for users and developers alike.
Vulnerability Detail
The vulnerability in the institutional_locust-silentdev package stems from its involvement in the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants can pollute the npm registry, potentially leading to the installation of compromised packages by unsuspecting developers. The origin of this vulnerability is traced back to automated scripts designed to inflate reputation scores for token rewards, posing a serious threat to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall institutional_locust-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 workaround, you can avoid using the institutional_locust-silentdev package altogether. If it is already included in your project, consider removing it and replacing it with a trusted alternative. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The institutional_locust-silentdev package poses a significant security risk due to its involvement in malicious activities aimed at manipulating npm registry reputation scores. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for institutional_locust-silentdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the installation of compromised packages, potentially exposing your project to security risks.
Remove the institutional_locust-silentdev package from your project and monitor for any updates or patches.
You can use Vulert, which allows you to monitor your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
