Malicious Code Injection in acute_halibut_requirement Package
Summary
MAL-2025-93121: Malicious code in acute_halibut_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 acute_halibut_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 publishing system. Its key attributes include automatic versioning and package name generation, which are manipulated to inflate developer reputation scores through the tea.xyz token reward initiative.
Vulnerability Detail
The vulnerability originates from the acute_halibut_requirement package, which contains malicious scripts designed to modify the package.json file. This includes removing private flags, altering version numbers, and generating random package names to continuously republish variants on the npm registry. The ramifications of this vulnerability include potential pollution of the npm registry, unauthorized access to sensitive information, and damage to developer reputations.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall acute_halibut_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 prevent the installation of the acute_halibut_requirement package by using the following command: npm uninstall acute_halibut_requirement. Additionally, ensure that your package-lock.json file is monitored for any unauthorized changes.
Conclusion
The acute_halibut_requirement package poses a significant risk due to its malicious code designed to exploit npm's publishing system. It is crucial to take immediate action by updating or removing the package and monitoring your dependencies for any vulnerabilities.
See every vulnerability recorded for acute_halibut_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 unauthorized modifications of your package.json file, potentially compromising your application's integrity.
You should uninstall the acute_halibut_requirement package immediately and monitor your package-lock.json for any unauthorized changes.
Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
