Malicious Code Injection in public_cicada_requirement Package
Summary
MAL-2025-96100: Malicious code in public_cicada_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 public_cicada_requirement package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. This package has been identified as part of a malicious campaign that aims to exploit npm's package publishing system. It is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the public_cicada_requirement package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to continuously republish these variants, thereby manipulating the npm registry and potentially compromising the integrity of other packages. This can lead to security risks for developers who unknowingly depend on these tainted packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall public_cicada_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 public_cicada_requirement package from your project by executing the command: 'npm uninstall public_cicada_requirement'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The public_cicada_requirement package poses a significant risk due to its malicious code that alters package metadata and republishing behavior. It is essential to take immediate action by updating or removing the package to safeguard your project from potential threats.
See every vulnerability recorded for public_cicada_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
If your project depends on this package, it may be at risk of using modified versions that can compromise security and integrity.
You should uninstall the package immediately and monitor for any updates or patches that address this vulnerability.
Yes, Vulert can monitor your package-lock.json file to alert you in real-time for open-source vulnerabilities, including this one.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
