Malicious Code Injection in likely_wolverine-toolteadev Package
Summary
MAL-2025-105143: Malicious code in likely_wolverine-toolteadev (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 likely_wolverine-toolteadev package is part of the npm ecosystem, primarily used for development purposes. It is designed to facilitate various development tasks but has been compromised as part of a malicious campaign. This package has been associated with the tea.xyz token reward initiative, which has led to the proliferation of numerous derivative packages aimed at inflating developer reputation scores.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the likely_wolverine-toolteadev package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, often themed around Indonesian culture. The primary risk is that it allows for the automatic generation and publication of numerous derivative packages, which can clutter the npm registry and potentially lead to security risks for developers who unknowingly install these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall likely_wolverine-toolteadevIf 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 likely_wolverine-toolteadev package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The likely_wolverine-toolteadev package has been identified as containing malicious code that poses a risk to developers. It is crucial to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in real-time.
See every vulnerability recorded for likely_wolverine-toolteadev →
FAQ
It is an npm package used for development tasks but has been compromised with malicious code.
The malicious code can modify your package.json, inflate developer reputation scores, and clutter the npm registry with unwanted packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
You should update the package to the latest version or remove it from your project until a secure version is available.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to minimize security risks.
