Malicious Code Injection in anxious_starfish_z3n Package
Summary
MAL-2025-99497: Malicious code in anxious_starfish_z3n (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 anxious_starfish_z3n package is part of the npm ecosystem and appears to be involved in the tea.xyz token reward campaign. This package is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability in the anxious_starfish_z3n package stems from its inclusion in a malicious campaign that utilizes autopublish scripts to create and publish numerous derivative packages with randomized names. This behavior not only pollutes the npm registry but also modifies the package.json file by removing private flags and altering version numbers. The malicious payload can lead to significant security risks, including the potential for unauthorized access and manipulation of the package's functionality.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall anxious_starfish_z3n
If 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 temporarily remove the package from your dependencies until a secure version is released. Use the following command to uninstall the package: npm uninstall anxious_starfish_z3n.
Conclusion
The anxious_starfish_z3n package has been identified as containing malicious code that poses significant security risks. It is crucial for developers to take immediate action by removing the package and monitoring for updates. Utilizing tools like Vulert can help in identifying vulnerabilities in real-time.
See every vulnerability recorded for anxious_starfish_z3n →
FAQ
The vulnerability involves malicious code that modifies package.json and publishes unauthorized derivative packages.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
It is advisable to uninstall the package immediately and monitor for any updates or patches.
Yes, leaving this vulnerability unaddressed can lead to unauthorized access and potential exploitation of your application.
It is uncertain at this time. Keep an eye on the package's repository for any announcements regarding patches.