Malicious Code Vulnerability in holy_starfish_0xrequest Package
Summary
MAL-2025-103758: Malicious code in holy_starfish_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 holy_starfish_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. This package, like others in the campaign, is designed to manipulate npm's publishing system for fraudulent purposes.
Vulnerability Detail
The vulnerability in holy_starfish_0xrequest stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a compromised development environment, inflated reputation scores for malicious actors, and potential security risks for applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall holy_starfish_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 temporary workaround, you can remove the holy_starfish_0xrequest package from your project by executing: npm uninstall holy_starfish_0xrequest. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The holy_starfish_0xrequest package contains a significant vulnerability due to its malicious code designed to manipulate npm's publishing system. It is crucial to take immediate action by updating or removing the package to safeguard your applications from potential threats.
See every vulnerability recorded for holy_starfish_0xrequest →
FAQ
The malicious code modifies package.json to remove private flags and alters version numbers, allowing for unauthorized republishing of the package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.
Using this package can lead to a compromised development environment, inflated reputation scores for malicious actors, and potential security risks for your applications.
Regularly audit your dependencies and utilize tools like Vulert to monitor for vulnerabilities in your open-source packages.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.
