Malicious Code Injection in combative_fish-tool: A Threat to npm Users
Summary
MAL-2025-100697: Malicious code in combative_fish-tool (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 combative_fish-tool package is part of the npm ecosystem, designed for various utility functions within JavaScript applications. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package, like others in the campaign, is engineered to manipulate the npm registry and inflate developer reputation scores through deceptive practices.
Vulnerability Detail
The vulnerability in combative_fish-tool originates from its association with the tea.xyz token reward campaign. This package contains scripts that automatically generate and publish derivative packages with randomized names, effectively polluting the npm registry. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, which can lead to security risks and reputational damage for developers using this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall combative_fish-toolIf 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 combative_fish-tool package altogether. If it is already in use, consider replacing it with a trusted alternative that provides similar functionality without the associated risks.
Conclusion
The combative_fish-tool package poses significant risks due to its malicious nature, which is part of a broader campaign to manipulate the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity and security of their applications.
See every vulnerability recorded for combative_fish-tool →
FAQ
combative_fish-tool is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through deceptive practices.
The vulnerability can lead to security risks, including the potential for malicious code execution and reputational damage due to the pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
You should remove the combative_fish-tool package from your project and look for a secure alternative.
Regularly audit your dependencies using tools like Vulert and stay updated on security advisories related to the packages you use.
