Malicious Code Injection in remaining_dragon-silentdev Package
Summary
MAL-2025-107878: Malicious code in remaining_dragon-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 remaining_dragon-silentdev package is part of the npm ecosystem, often used in JavaScript applications 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 particularly vulnerable due to its association with scripts designed to manipulate package metadata and inflate developer reputation scores.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign linked to the tea.xyz token reward initiative. It contains scripts that modify the package.json file to remove private flags, alter 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 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 remaining_dragon-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 avoid using the remaining_dragon-silentdev package and replace it with a trusted alternative. Additionally, you can lock your dependencies using package-lock.json to prevent automatic updates to malicious versions.
Conclusion
The remaining_dragon-silentdev package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package and monitor your dependencies for vulnerabilities using tools like Vulert.
See every vulnerability recorded for remaining_dragon-silentdev →
FAQ
The vulnerability involves malicious code that alters package metadata and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.
Remove the remaining_dragon-silentdev package from your project and replace it with a trusted alternative.
Currently, there is no specific patch for the remaining_dragon-silentdev package. It is recommended to remove it instead.
Vulert uses package-lock.json to monitor for vulnerabilities and can alert you in real-time, helping you maintain the security of your software.
