Malicious Code Injection in stormy_wombat-toolteadev: A Threat to npm Ecosystem
Summary
MAL-2025-109160: Malicious code in stormy_wombat-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 package stormy_wombat-toolteadev is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised by the presence of malicious scripts that manipulate its metadata and behavior.
Vulnerability Detail
The vulnerability stems from the inclusion of malicious code within the stormy_wombat-toolteadev package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants to pollute the npm registry, posing a significant risk to developers who may unknowingly use these compromised packages. The origin of this vulnerability is tied to the tea.xyz token reward campaign, which has flooded the npm ecosystem with such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall stormy_wombat-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 remove the stormy_wombat-toolteadev package from your project by executing: npm uninstall stormy_wombat-toolteadev. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The stormy_wombat-toolteadev package poses a significant risk due to its malicious code that alters package metadata and inflates developer reputation scores. It is crucial for developers to stay informed about such vulnerabilities and take immediate action to secure their projects.
See every vulnerability recorded for stormy_wombat-toolteadev →
FAQ
stormy_wombat-toolteadev is an npm package that has been identified as containing malicious code aimed at manipulating package metadata and inflating developer reputation scores.
The malicious code modifies your package.json file, potentially exposing your project to further vulnerabilities and affecting the integrity of your application.
If you have installed stormy_wombat-toolteadev, you should uninstall it immediately and check for any updates or patches for your dependencies.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application against vulnerabilities using the Vulert playground without any signup.
More information can be found in the vulnerability report on the official GitHub repository or through security advisories related to npm packages.
