Malicious Code Vulnerability in dependent_moth-silentdev Package
Summary
MAL-2025-101351: Malicious code in dependent_moth-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 dependent_moth-silentdev package is part of the npm ecosystem, often used in JavaScript projects. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that contain malicious scripts. These scripts are designed to manipulate package metadata and inflate developer reputation scores through automated publishing of derivative packages.
Vulnerability Detail
This vulnerability originates from the malicious code embedded in the dependent_moth-silentdev package. The code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to the pollution of the npm registry. This not only affects the integrity of the npm ecosystem but also poses a risk to developers who may unknowingly use these compromised packages in their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dependent_moth-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 dependent_moth-silentdev package from your project by executing: npm uninstall dependent_moth-silentdev. This will prevent any malicious code from executing while you seek a secure alternative or wait for a patched version.
Conclusion
The dependent_moth-silentdev package contains a significant vulnerability that can compromise the integrity of npm projects. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in your dependencies.
See every vulnerability recorded for dependent_moth-silentdev →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, known for containing malicious scripts.
The vulnerability can lead to the modification of your package.json file and the introduction of unwanted packages, compromising your project's integrity.
You should uninstall the package immediately and check for any unauthorized changes in your project files.
Yes, you can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
