Malicious Code Injection in alone_wildcat-biggestdev Package
Summary
MAL-2025-99369: Malicious code in alone_wildcat-biggestdev (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 'alone_wildcat-biggestdev' package 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 known to flood the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata to inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in the 'alone_wildcat-biggestdev' package stems from its inclusion in a malicious campaign that employs autopublish scripts to create and publish derivative packages with randomized names. These scripts modify the package.json file to remove private flags, alter version numbers, and continuously republish variants, leading to pollution of the npm registry. This can result in compromised developer reputations and potential security risks for applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall alone_wildcat-biggestdevIf 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 'alone_wildcat-biggestdev' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall alone_wildcat-biggestdev.
Conclusion
The 'alone_wildcat-biggestdev' package contains a serious vulnerability due to its involvement in a malicious campaign. It is crucial for developers to be aware of such vulnerabilities, take immediate action to remove affected packages, and utilize tools like Vulert to monitor their projects for security risks.
See every vulnerability recorded for alone_wildcat-biggestdev →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application if it relies on affected packages.
You should uninstall the 'alone_wildcat-biggestdev' package immediately and look for alternative packages.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file. You can check your application for vulnerabilities without signing up at the Vulert playground.
Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and review the security practices of the packages you use.
