Malicious Code Exploit in proud_ox_replicate_automation Package
Summary
MAL-2025-107388: Malicious code in proud_ox_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 proud_ox_replicate_automation package is part of the npm ecosystem, primarily utilized for automation tasks. It has gained attention due to its association with the tea.xyz token reward campaign, which has been linked to various malicious activities. This package is designed to automate processes but has been compromised to serve malicious purposes, affecting its integrity and the security of applications that depend on it.
Vulnerability Detail
The vulnerability in the proud_ox_replicate_automation package stems from malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards, leading to the continuous republishing of derivative packages that pollute the npm registry. The origin of this vulnerability is traced back to a campaign that exploits npm's publishing mechanisms, posing significant risks to developers and users by compromising the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall proud_ox_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 proud_ox_replicate_automation package from your project until a secure version is released. This can be done using the command: npm uninstall proud_ox_replicate_automation. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The proud_ox_replicate_automation package has been identified as containing malicious code that poses significant risks to developers and applications. It is essential to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.
See every vulnerability recorded for proud_ox_replicate_automation →
FAQ
It is an npm package used for automation tasks, but it has been compromised with malicious code.
The vulnerability can lead to the modification of your package.json file, potentially compromising your application's integrity and security.
You should immediately update or uninstall the package to mitigate the risks associated with this vulnerability.
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 for vulnerabilities in your application without needing to sign up.
