Malicious Code Injection in distinct_vulture-silentdev Package
Summary
MAL-2025-101647: Malicious code in distinct_vulture-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 distinct_vulture-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 aims to inflate developer reputation scores through the autopublishing of derivative packages. This package's functionality has been compromised, making it a vector for malicious activities.
Vulnerability Detail
The vulnerability originates from the package being involved in the tea.xyz token reward campaign, which floods npm with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of dependent projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall distinct_vulture-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 distinct_vulture-silentdev package from your project by executing: npm uninstall distinct_vulture-silentdev. This will prevent any malicious code from executing until a fix is applied.
Conclusion
The distinct_vulture-silentdev package poses a significant risk due to its involvement in malicious activities aimed at manipulating the npm registry. It is crucial to take immediate action by updating or removing the package to safeguard your projects.
See every vulnerability recorded for distinct_vulture-silentdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The vulnerability can lead to the automatic generation of malicious packages, which can compromise your project's integrity and security.
You should uninstall the package immediately and check for any updates or patches from the package maintainers.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
