Malicious Code Vulnerability in depressed_turtle-silentdev Package
Summary
MAL-2025-101360: Malicious code in depressed_turtle-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 depressed_turtle-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 derivative packages. This package is designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant issues in the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign associated with the tea.xyz token reward initiative. It contains scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior results in the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall depressed_turtle-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 remove the package from your project dependencies by executing the following command: npm uninstall depressed_turtle-silentdev. This will help mitigate the risks associated with the malicious code until a secure version is released.
Conclusion
The depressed_turtle-silentdev package poses a significant security risk due to its malicious code designed to manipulate npm registry entries. It is essential to remove this package from your project and monitor for updates or patches. Utilizing tools like Vulert can enhance your ability to detect and respond to such vulnerabilities effectively.
See every vulnerability recorded for depressed_turtle-silentdev →
FAQ
The malicious code is designed to modify package.json files, remove private flags, and continuously publish variants to the npm registry, thereby inflating developer reputation scores.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By utilizing the Vulert playground, you can check if your application is affected without any signup.
Using this package can lead to security vulnerabilities in your application, as it may introduce malicious code that compromises the integrity of your software.
Regularly auditing your dependencies and using tools like Vulert can help identify and mitigate vulnerabilities before they affect your application.
It is crucial to remove the package immediately and monitor your application for any unusual behavior. Consider replacing it with a secure alternative.
