Malicious Code Injection in radical_hummingbird_requirement Package
Summary
MAL-2025-96170: Malicious code in radical_hummingbird_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 radical_hummingbird_requirement package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. It is designed to facilitate the integration of various functionalities within a project. However, this package has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to severe security risks for developers and their applications.
Vulnerability Detail
The vulnerability in the radical_hummingbird_requirement package originates from its association with the tea.xyz token reward campaign. This campaign has led to the proliferation of malicious packages that contain scripts designed to automatically publish derivative packages with altered metadata. The malicious payload modifies the package.json file to remove private flags, changes version numbers, and generates random package names, ultimately polluting the npm registry and compromising the integrity of the ecosystem. Developers using this package may unknowingly expose their applications to further attacks or misuse.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall radical_hummingbird_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 measure, you can avoid using the radical_hummingbird_requirement package and seek alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before integrating them into your projects.
Conclusion
The radical_hummingbird_requirement package poses significant security risks due to its malicious code injection capabilities. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any compromised packages from their projects. Regular monitoring and updates are essential to maintain a secure development environment.
See every vulnerability recorded for radical_hummingbird_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 security and integrity of your application.
You should uninstall the radical_hummingbird_requirement package immediately and check your application for any signs of compromise.
Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
