Malicious Code Injection in due_sloth_jade-66 Package - npm Vulnerability
Summary
MAL-2025-101800: Malicious code in due_sloth_jade-66 (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 due_sloth_jade-66 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages aimed at inflating developer reputation scores through automated scripts.
Vulnerability Detail
The vulnerability in due_sloth_jade-66 originates from its involvement in the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. These actions lead to the continuous republishing of derivative packages, which pollutes the npm registry and can compromise the integrity of the ecosystem. The malicious payload can potentially affect developers by misrepresenting their contributions and leading to security risks in applications that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall due_sloth_jade-66If 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 due_sloth_jade-66 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in your package-lock.json file.
Conclusion
The due_sloth_jade-66 package poses a significant risk due to its malicious code that alters package configurations and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies to ensure the security of their applications.
See every vulnerability recorded for due_sloth_jade-66 →
FAQ
The due_sloth_jade-66 package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
This vulnerability can compromise the integrity of your application by introducing malicious code that modifies your package configurations and republishing harmful variants.
You should uninstall the due_sloth_jade-66 package immediately and monitor your dependencies for any further vulnerabilities.
You can use tools like Vulert, which allows you to monitor and alert for open-source vulnerabilities in real-time using your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring a signup.
