Malicious Code Injection in glorious_echidna_requirement Package
Summary
MAL-2025-94706: Malicious code in glorious_echidna_requirement (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 glorious_echidna_requirement package is part of the npm ecosystem, typically used for managing dependencies in JavaScript projects. This package has been identified as part of a malicious campaign that targets developers by flooding the npm registry with derivative packages. The intention behind this campaign is to manipulate developer reputation scores for token rewards, leading to potential misuse and abuse of the npm ecosystem.
Vulnerability Detail
The vulnerability in the glorious_echidna_requirement package arises from its inclusion in a malicious campaign that modifies the package.json file. This modification removes private flags and alters version numbers, allowing the package to generate and publish numerous derivative packages with randomized names. The malicious payload can lead to pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing their projects to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall glorious_echidna_requirementIf 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, consider removing the glorious_echidna_requirement package from your project if it is not essential. You can do this by executing the command: npm uninstall glorious_echidna_requirement. Additionally, monitor your package-lock.json file for any unexpected changes or additions.
Conclusion
The glorious_echidna_requirement package is implicated in a malicious campaign that modifies package metadata to inflate developer reputation scores. It is crucial for developers to be aware of this vulnerability and take appropriate actions to secure their projects by updating or removing the affected package.
See every vulnerability recorded for glorious_echidna_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.
The vulnerability can lead to the pollution of the npm registry, making it harder to find legitimate packages and potentially exposing your project to further vulnerabilities.
You should update the package to a patched version or remove it from your project if it is not essential.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground.
You can refer to the official GitHub repository for the glorious_echidna_requirement package or check security advisories related to npm packages.
