Malicious Code Injection in misty_squid_z3n Package
Summary
MAL-2025-98819: Malicious code in misty_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 misty_squid_z3n package 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 of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry and inflate developer reputation scores through the automatic generation of derivative packages.
Vulnerability Detail
The vulnerability in the misty_squid_z3n package stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant security risks, including the potential for developers to unknowingly use compromised packages, which can introduce further vulnerabilities into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall misty_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 misty_squid_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.
Conclusion
The misty_squid_z3n package poses a significant security risk due to its malicious behavior of modifying package metadata and republishing variants. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities to ensure the security of their applications.
See every vulnerability recorded for misty_squid_z3n →
FAQ
The misty_squid_z3n package is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
If your application uses the misty_squid_z3n package, it may be at risk of incorporating malicious code that can compromise your application's security.
You should uninstall the misty_squid_z3n package immediately and check your package-lock.json file for any references to it.
You can use Vulert to monitor your project for open-source vulnerabilities. It requires only your package-lock.json file to provide real-time alerts.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
