Malicious Code Injection in private_beaver_replicate_automation Package
Summary
MAL-2025-107295: Malicious code in private_beaver_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 private_beaver_replicate_automation package is part of the npm ecosystem, primarily used for automating tasks related to data replication. However, it has been identified as part of a malicious campaign that exploits npm's package publishing system. This package is designed to generate and publish derivative packages with randomized names, which can lead to reputation inflation for the tea.xyz token reward campaign.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the private_beaver_replicate_automation package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then continuously republished to the npm registry. This behavior not only pollutes the npm ecosystem but also poses a risk of unintentional dependency on malicious packages by developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall private_beaver_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 private_beaver_replicate_automation package from your project by executing: npm uninstall private_beaver_replicate_automation. This will prevent any malicious code from executing in your environment until a secure version is available.
Conclusion
The private_beaver_replicate_automation package poses a significant risk due to its embedded malicious code. Developers are advised to uninstall the package and monitor their projects for vulnerabilities using tools like Vulert. Keeping dependencies updated and regularly checking for security advisories is crucial for maintaining a secure development environment.
See every vulnerability recorded for private_beaver_replicate_automation →
FAQ
It is an npm package used for automating data replication tasks, but it has been compromised with malicious code.
The malicious code modifies your package.json, removes private flags, and publishes harmful variants, potentially leading to security vulnerabilities.
You should uninstall the package immediately and check for any dependencies that may have been affected.
Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without signing up.
