Malicious Code Injection in driving_sloth_0xrequest Package
Summary
MAL-2025-101779: Malicious code in driving_sloth_0xrequest (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 driving_sloth_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate various functionalities, but it has been compromised to include malicious code that affects its integrity and security. The package is primarily used for generating and publishing derivative packages, which can lead to reputation inflation for developers involved in the tea protocol.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the driving_sloth_0xrequest package. This payload 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. The malicious code is designed to continuously republish variants of the package, thereby increasing the risk of exploitation and misuse by attackers. The ramifications include potential security breaches, loss of developer reputation, and the proliferation of untrustworthy packages in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall driving_sloth_0xrequestIf 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 prevent the installation of the compromised package by using the npm shrinkwrap feature or by specifying a version range that excludes the vulnerable versions. For example, you can add the following to your package.json: "driving_sloth_0xrequest": "<0.1.0" to avoid installing any affected versions.
Conclusion
The driving_sloth_0xrequest package has been identified as containing malicious code that poses significant risks to developers and their projects. It is crucial to take immediate action to remove the package and monitor for any further vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your open-source dependencies.
See every vulnerability recorded for driving_sloth_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed for generating and publishing derivative packages.
The vulnerability can lead to the modification of your package.json file, potentially compromising your project's integrity and security.
You should immediately remove the driving_sloth_0xrequest package from your project and update to a patched version if available.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just 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 any signup.
