Malicious Code Injection in quiet_ocelot_replicate_automation Package
Summary
MAL-2025-107664: Malicious code in quiet_ocelot_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The quiet_ocelot_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 its own metadata and publish variants to inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability stems from the package's involvement in the tea.xyz token reward campaign, which utilizes malicious scripts to modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of these variants. This not only pollutes the npm registry but also compromises the security and reliability of dependent projects, potentially allowing for further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall quiet_ocelot_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 measure, you can remove the affected package from your project by executing the command: 'npm uninstall quiet_ocelot_replicate_automation'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The quiet_ocelot_replicate_automation package has been identified as a vector for malicious code injection, posing significant risks to users and the npm ecosystem. It is essential to take immediate action by updating or removing the package to safeguard your projects.
See every vulnerability recorded for quiet_ocelot_replicate_automation →
FAQ
It is an npm package used for automation tasks but has been compromised with malicious code.
It can lead to the pollution of the npm registry and compromise the security of your project by introducing malicious code.
You should immediately update or uninstall the package to mitigate the risks associated with this vulnerability.
You can refer to the official npm registry or security advisories for detailed information on the vulnerability.
Vulert uses your package-lock.json to monitor and alert you in real-time for open-source vulnerabilities without requiring code access or installation.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
