Malicious Code Injection in squid_indigo-78: A Threat to npm Ecosystem
Summary
MAL-2025-98370: Malicious code in squid_indigo-78 (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 'squid_indigo-78' is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to potential security risks for developers and users alike.
Vulnerability Detail
The vulnerability in 'squid_indigo-78' originates from its association with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages contain scripts designed to automatically generate and publish derivative packages with randomized names, effectively polluting the npm registry. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, which can lead to reputation inflation for malicious actors and compromise the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall squid_indigo-78If 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 'squid_indigo-78' and any other packages associated with the tea.xyz campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.
Conclusion
The 'squid_indigo-78' vulnerability highlights the ongoing risks associated with open-source package management. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can help safeguard your applications from malicious threats.
See every vulnerability recorded for squid_indigo-78 →
FAQ
The impact includes potential exposure to malicious code that can compromise your application and inflate the reputation of malicious actors within the npm ecosystem.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
If you have installed squid_indigo-78, it is recommended to uninstall it immediately and audit your project for any other potentially malicious packages.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages.
The tea.xyz token reward campaign is significant because it has led to the proliferation of malicious packages in the npm registry, posing risks to developers and users by compromising package integrity.
