Malicious Code Vulnerability in chronic_cuckoo_requirement Package
Summary
MAL-2025-93547: Malicious code in chronic_cuckoo_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 chronic_cuckoo_requirement package is part of the npm ecosystem, typically used for various functionalities in JavaScript applications. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing system. This package is associated with the tea.xyz token reward scheme, which floods the npm registry with derivative packages to inflate developer reputation scores.
Vulnerability Detail
The vulnerability originates from malicious code embedded within the chronic_cuckoo_requirement package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a compromised reputation for legitimate developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall chronic_cuckoo_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 chronic_cuckoo_requirement package from your project by running: npm uninstall chronic_cuckoo_requirement. This will prevent any malicious code from executing until a fix is applied.
Conclusion
The chronic_cuckoo_requirement package contains a serious vulnerability that can compromise the integrity of applications relying on it. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects.
See every vulnerability recorded for chronic_cuckoo_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the pollution of the npm registry and may introduce security risks into your application.
You should update the package to the latest patched version or remove it from your project until a fix is available.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
