Malicious Code Injection in spicy_starfish-apptea: npm Package Vulnerability
Summary
MAL-2025-109012: Malicious code in spicy_starfish-apptea (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 spicy_starfish-apptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with potentially harmful packages. This package is designed to facilitate the distribution of derivative packages that can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that modifies essential files, posing a significant risk to users.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which alters the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to reputation damage for developers and potential security risks for applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall spicy_starfish-appteaIf 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 spicy_starfish-apptea package from your project by running: npm uninstall spicy_starfish-apptea. This will prevent the malicious code from executing while you seek a secure alternative.
Conclusion
The spicy_starfish-apptea package has been identified as containing malicious code that poses significant risks to developers and their applications. It is essential to take immediate action by updating or uninstalling the package to safeguard your project. Utilizing tools like Vulert can further enhance your security posture by monitoring for vulnerabilities in real-time.
See every vulnerability recorded for spicy_starfish-apptea →
FAQ
The primary risk is the modification of package.json, which can lead to unauthorized access and the proliferation of malicious packages in the npm registry.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If immediate updates are not possible, consider uninstalling the package as a temporary measure to mitigate risks.
Check the npm registry for any patched versions of spicy_starfish-apptea. If available, updating to the latest version is recommended.
Vulert monitors and alerts for open-source vulnerabilities in your software using just package-lock.json, providing real-time insights into potential risks.
