Malicious Code Injection in romantic_angelfish_replicate_automation Package
Summary
MAL-2025-108191: Malicious code in romantic_angelfish_replicate_automation (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 romantic_angelfish_replicate_automation package is part of the npm ecosystem, typically used for automation tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to inflate developer reputation scores through the generation and publication of numerous variants with altered metadata.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign associated with the tea.xyz token reward initiative. It contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This leads to the continuous republishing of these variants, which pollutes the npm registry and can compromise the integrity of the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall romantic_angelfish_replicate_automationIf 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 romantic_angelfish_replicate_automation package from your project by executing: npm uninstall romantic_angelfish_replicate_automation. This will prevent any potential exploitation until a secure version is available.
Conclusion
The romantic_angelfish_replicate_automation package has been identified as containing malicious code that can compromise the npm ecosystem. It is crucial for developers to take immediate action by uninstalling the package and monitoring for updates. Utilizing tools like Vulert can help in identifying and managing vulnerabilities effectively.
See every vulnerability recorded for romantic_angelfish_replicate_automation →
FAQ
It is an npm package used for automation tasks but has been identified as part of a malicious campaign.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing malicious code.
You should uninstall the package immediately and monitor for any updates or patches that may be released.
You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application against known vulnerabilities using the Vulert playground.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.
