Malicious Code Exploit in squid-notthedevs: A Threat to npm Users
Summary
MAL-2025-109056: Malicious code in squid-notthedevs (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-notthedevs' is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms. It is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'squid-notthedevs' originates from its association with the tea.xyz token reward campaign. The malicious code embedded in this package modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these polluted packages, potentially leading to security breaches and loss of trust in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall squid-notthedevsIf 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 remove the 'squid-notthedevs' package from your project by using the command: npm uninstall squid-notthedevs. This will prevent any malicious code from executing in your environment until a secure version is available.
Conclusion
The 'squid-notthedevs' package poses a significant threat due to its embedded malicious code, which can compromise the integrity of the npm ecosystem. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for squid-notthedevs →
FAQ
The malicious code is designed to modify package.json files, remove private flags, and generate random package names, which can lead to the pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground, you can check if your application is affected without any signup.
Using this package can lead to security breaches, loss of trust in your application, and potential exposure to further malicious packages.
Regularly auditing your dependencies and using tools like Vulert can help you stay informed about vulnerabilities and maintain a secure environment.
If an immediate update is not possible, consider removing the package from your project and monitoring for updates regularly.
