Malicious Code Injection in closed_angelfish_requirement Package
Summary
MAL-2025-93590: Malicious code in closed_angelfish_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 closed_angelfish_requirement package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. This package, like many others, is intended to facilitate the development process by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's package management system, leading to significant security risks.
Vulnerability Detail
The vulnerability originates from the closed_angelfish_requirement package, which is linked to a broader malicious campaign targeting npm. This package contains scripts designed to automatically generate and publish derivative packages with randomized names, effectively polluting the npm registry. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, which can lead to compromised applications and inflated developer reputation scores for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall closed_angelfish_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 closed_angelfish_requirement package from your project until a secure version is released. This can be done using the command: npm uninstall closed_angelfish_requirement. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The closed_angelfish_requirement package poses a significant security risk due to its malicious code injection capabilities. It is essential to take immediate action by updating or removing the package and utilizing monitoring tools like Vulert to safeguard your applications from potential threats.
See every vulnerability recorded for closed_angelfish_requirement →
FAQ
It is an npm package used for managing dependencies in JavaScript applications, but it has been identified as part of a malicious campaign.
The vulnerability can lead to the injection of malicious code, compromising the integrity of your application and potentially exposing sensitive data.
You should immediately update the package to the latest version or remove it from your project until a secure version is available.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
