Malicious Code Injection in current_termite_replicate_automation Package
Summary
MAL-2025-101166: Malicious code in current_termite_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 current_termite_replicate_automation package is part of the npm ecosystem, primarily used for automating tasks related to termite replication. It is designed to streamline processes for developers. However, this package has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security concerns.
Vulnerability Detail
The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which floods npm with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the integrity of the affected package but also pollutes the npm registry, potentially affecting other developers and applications relying on npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall current_termite_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 the following command to uninstall it: npm uninstall current_termite_replicate_automation. Additionally, consider using npm audit to identify and address other potential vulnerabilities in your project.
Conclusion
The current_termite_replicate_automation package has been identified as a vector for malicious code injection, posing significant risks to developers and their applications. Immediate action is required to mitigate these risks by removing the package and monitoring for any further vulnerabilities.
See every vulnerability recorded for current_termite_replicate_automation →
FAQ
It is an npm package designed for automating termite replication tasks, but it has been compromised with malicious code.
The malicious code can modify your package.json file, potentially leading to security risks and affecting the integrity of your application.
You should uninstall the package immediately and monitor your project for any unexpected behavior or changes.
Yes, you can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
