Malicious Code Injection in intimate_angelfish_0xrequest Package
Summary
MAL-2025-104362: Malicious code in intimate_angelfish_0xrequest (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 intimate_angelfish_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, which are often used to inflate developer reputation scores for rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of applications that depend on it.
Vulnerability Detail
The vulnerability in the intimate_angelfish_0xrequest package stems from the presence of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The origin of this issue is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the creation of these malicious packages. The ramifications include potential security risks for applications using this package, as well as the degradation of the npm registry's reliability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall intimate_angelfish_0xrequestIf 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 workaround, you can avoid using the intimate_angelfish_0xrequest package altogether. If your application relies on it, consider finding an alternative package that provides similar functionality without the associated risks.
Conclusion
The intimate_angelfish_0xrequest package has been identified as containing malicious code that poses significant security risks. It is crucial for developers to remove this package from their projects and seek alternatives to ensure the integrity and security of their applications. Regular monitoring for vulnerabilities using tools like Vulert can help maintain secure software practices.
See every vulnerability recorded for intimate_angelfish_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The package modifies package.json files, removes private flags, changes version numbers, and generates random package names, leading to pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. Visit Vulert Scanner to check your application without any signup.
You should uninstall the intimate_angelfish_0xrequest package immediately and look for alternative packages that do not pose security risks.
Currently, there is no patched version available for the intimate_angelfish_0xrequest package. It is recommended to uninstall it and monitor for any updates.
