Malicious Code Injection in filthy_owl_replicate_automation Package
Summary
MAL-2025-102700: Malicious code in filthy_owl_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 filthy_owl_replicate_automation package is part of the npm ecosystem, primarily 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 manipulate developer reputation scores through automated publishing scripts, which can lead to significant issues within the npm ecosystem.
Vulnerability Detail
The vulnerability stems from the package's involvement in the tea.xyz token reward campaign, which utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This malicious behavior modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry and potential security risks for developers relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall filthy_owl_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 avoid using the filthy_owl_replicate_automation package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall filthy_owl_replicate_automation.
Conclusion
The filthy_owl_replicate_automation package poses a significant risk due to its malicious behavior aimed at manipulating npm registry integrity. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain security.
See every vulnerability recorded for filthy_owl_replicate_automation →
FAQ
It is an npm package involved in automation tasks but has been identified as malicious due to its role in a token reward 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 your project for any unusual behavior.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
