Malicious Code Injection in statutory_ox_replicate_automation Package
Summary
MAL-2025-109097: Malicious code in statutory_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 statutory_ox_replicate_automation package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to automate the generation and publication of derivative packages, thereby inflating developer reputation scores for token rewards in the tea.xyz protocol. The package's functionality is compromised, making it a vector for malicious activities.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. It contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to further security risks. The malicious payload can also affect the integrity of applications that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall statutory_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 prevent the installation of this package by using npm's package-lock.json file to lock your dependencies. Additionally, consider using the following command to uninstall the package: npm uninstall statutory_ox_replicate_automation.
Conclusion
The statutory_ox_replicate_automation package poses a significant risk due to its malicious code designed to exploit the npm ecosystem. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the package, and utilize tools like Vulert to monitor their dependencies for future vulnerabilities.
See every vulnerability recorded for statutory_ox_replicate_automation →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of applications that depend on this package.
You should uninstall the statutory_ox_replicate_automation package immediately and check for any updates or patches.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without any signup.
