Malicious Code Injection in continental_echidna_z3n: A Threat to npm Packages
Summary
MAL-2025-100927: Malicious code in continental_echidna_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 package 'continental_echidna_z3n' 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 generating and publishing numerous derivative packages with randomized names. These actions are intended to inflate developer reputation scores for token rewards associated with the tea protocol.
Vulnerability Detail
The vulnerability in 'continental_echidna_z3n' originates from its involvement in a token reward campaign that floods the npm registry with malicious packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This results in the continuous republishing of these variants, which pollutes the npm registry and can lead to reputational damage for developers and security risks for users who inadvertently install these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall continental_echidna_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 measure, avoid using the 'continental_echidna_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 check for vulnerabilities in your package-lock.json file. For example, you can visit the Vulert playground at https://vulert.com/scanner to analyze your application without needing to sign up.
Conclusion
The 'continental_echidna_z3n' package poses a significant risk due to its malicious code designed to exploit the npm registry. It is crucial for developers to remove this package from their projects and monitor for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for continental_echidna_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
The vulnerability can lead to the installation of malicious code, which may compromise your project's security and reputation.
You should uninstall the package immediately using 'npm uninstall continental_echidna_z3n' and check for any other affected dependencies.
You can use tools like Vulert, which allows you to monitor and alert for open-source vulnerabilities in real-time using your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring an account.
