Malicious Code Injection in sick_squid_z3n Package - npm Vulnerability
Summary
MAL-2025-98929: Malicious code in sick_squid_z3n (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 sick_squid_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The primary function of such packages is to inflate developer reputation scores through automated publishing scripts, which can lead to a polluted registry and potential security risks for users.
Vulnerability Detail
The vulnerability stems from the inclusion of malicious code within the sick_squid_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then continuously republished to the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to further exploitation or data breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sick_squid_z3nIf 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 sick_squid_z3n package and any packages that depend on it. Additionally, consider using tools like Vulert to monitor your package-lock.json file for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The sick_squid_z3n package poses a significant risk due to its malicious code that compromises the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities. Staying informed and proactive can help mitigate the risks associated with such malicious packages.
See every vulnerability recorded for sick_squid_z3n →
FAQ
The sick_squid_z3n package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The malicious code modifies your package.json file, removes private flags, and republishes variants, which can lead to a polluted npm registry and potential security risks.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
You should uninstall the sick_squid_z3n package immediately using the command npm uninstall sick_squid_z3n and look for secure alternatives.
Regularly update your packages to their latest versions and use tools like Vulert to monitor your dependencies for vulnerabilities.
