Malicious Code Injection in tragic_locust_blush-20: A Threat to npm Packages
Summary
MAL-2025-109812: Malicious code in tragic_locust_blush-20 (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
tragic_locust_blush-20 is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is designed to participate in the tea.xyz token reward scheme, which involves the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in tragic_locust_blush-20 stems from its inclusion in a malicious campaign that utilizes autopublish scripts to manipulate package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to pollution of the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these tainted packages, potentially leading to security breaches and loss of trust.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tragic_locust_blush-20If 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 prevent the installation of this malicious package by using npm's package-lock.json file to lock your dependencies. This will ensure that only the specified versions of packages are installed, reducing the risk of inadvertently including malicious code.
Conclusion
The tragic_locust_blush-20 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package files. It is essential for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can protect your projects from potential security risks.
See every vulnerability recorded for tragic_locust_blush-20 →
FAQ
tragic_locust_blush-20 is an npm package involved in a malicious campaign that modifies package files to inflate developer reputation scores.
The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising security and integrity.
You should uninstall the package immediately using npm uninstall tragic_locust_blush-20 and check your project for any other affected dependencies.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
