Malicious Code Injection in sick_earthworm_z3n Package
Summary
MAL-2025-90487: Malicious code in sick_earthworm_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_earthworm_z3n package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks.
Vulnerability Detail
The vulnerability in the sick_earthworm_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, which can lead to pollution of 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.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sick_earthworm_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, avoid using the sick_earthworm_z3n package and monitor your project for any dependencies that may have been affected by this malicious code. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The sick_earthworm_z3n package poses a significant security risk due to its involvement in a malicious campaign that modifies package metadata and publishes harmful derivatives. It is crucial for developers to remove this package from their projects and monitor for vulnerabilities using tools like Vulert.
See every vulnerability recorded for sick_earthworm_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.
You should uninstall the sick_earthworm_z3n package immediately and check for any dependencies that may have been affected.
Yes, you can use Vulert to monitor your package-lock.json for real-time alerts on open-source vulnerabilities without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
