Malicious Code Injection in opposite_anglerfish_requirement Package
Summary
MAL-2025-95759: Malicious code in opposite_anglerfish_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 opposite_anglerfish_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 broader malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages often include scripts designed to manipulate package metadata and inflate developer reputation scores through deceptive practices.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the opposite_anglerfish_requirement package, which is associated with the tea.xyz token reward campaign. It contains scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of these variants, ultimately polluting the npm registry and potentially compromising the integrity of other packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall opposite_anglerfish_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 opposite_anglerfish_requirement package from your project by executing: npm uninstall opposite_anglerfish_requirement. This will prevent any malicious scripts from executing until a secure version is available.
Conclusion
The opposite_anglerfish_requirement package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. Immediate action is required to update or remove the package to protect your application from potential exploitation.
See every vulnerability recorded for opposite_anglerfish_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The vulnerability can lead to the modification of your package.json file, potentially compromising your application's integrity and security.
You should immediately update or uninstall the package to mitigate the risk associated with this vulnerability.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without requiring any signup.
