Malicious Code Injection in salty_wolverine-toolteadev: A Threat to npm Users
Summary
MAL-2025-108345: Malicious code in salty_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
salty_wolverine-toolteadev is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the development of tools and applications within the tea protocol ecosystem. However, it has been identified as containing malicious code that compromises its integrity and the security of its users.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the salty_wolverine-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 the npm registry, which can lead to reputation inflation for developers involved in the tea protocol token rewards. This not only pollutes the npm registry but also poses a significant risk to users who may unknowingly install compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall salty_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 salty_wolverine-toolteadev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.
Conclusion
The salty_wolverine-toolteadev package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised packages. It is crucial for developers to uninstall this package and monitor their dependencies to maintain the integrity of their applications.
See every vulnerability recorded for salty_wolverine-toolteadev →
FAQ
The primary issue is the presence of malicious code that modifies package.json and republishes variants to the npm registry, compromising the security of users.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without any signup.
You should uninstall the salty_wolverine-toolteadev package immediately using the command npm uninstall salty_wolverine-toolteadev.
Yes, you should look for alternative npm packages that provide similar functionality without the associated risks. Always verify the integrity of packages before installation.
Regularly audit your npm packages using tools like npm audit, and consider using Vulert to monitor your dependencies for vulnerabilities.
