Malicious Code Vulnerability in steady_echidna_requirement Package
Summary
MAL-2025-96766: Malicious code in steady_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The steady_echidna_requirement package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is particularly vulnerable due to its association with scripts that manipulate package metadata and publish unauthorized versions, affecting the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the steady_echidna_requirement package being linked to a malicious campaign that modifies package.json files. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only compromises the security of the affected projects but also pollutes the npm registry, making it difficult for developers to trust the packages they use.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall steady_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, you can remove the steady_echidna_requirement package from your project until a secure version is available. This can be done using the command: npm uninstall steady_echidna_requirement. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The steady_echidna_requirement package has been identified as a vector for malicious code that compromises the integrity of the npm registry. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.
See every vulnerability recorded for steady_echidna_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate package metadata and publish unauthorized versions.
The vulnerability can lead to the introduction of malicious code, compromising the security and integrity of your project and potentially affecting other dependencies.
You should uninstall the package immediately and monitor for any updates or patches that may address the vulnerability.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
If not addressed, this vulnerability can lead to significant security risks, including data breaches and loss of trust in the npm ecosystem.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
