Malicious Code Injection in Inevitable Harrier Replicate Automation Package
Summary
MAL-2025-104179: Malicious code in inevitable_harrier_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 'inevitable_harrier_replicate_automation' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to automate tasks related to package publishing, but it has been compromised to include malicious scripts that manipulate package metadata and inflate developer reputation scores.
Vulnerability Detail
This vulnerability stems from the package's involvement in a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. This can result in security risks for developers who unknowingly use these compromised packages, as they may inadvertently include malicious code in their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall inevitable_harrier_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 'inevitable_harrier_replicate_automation' package from your project by executing the command: 'npm uninstall inevitable_harrier_replicate_automation'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The 'inevitable_harrier_replicate_automation' package has been identified as containing malicious code that can compromise your project. It is crucial to take immediate action by updating or removing the package to safeguard your application from potential threats.
See every vulnerability recorded for inevitable_harrier_replicate_automation →
FAQ
The malicious code modifies package metadata and publishes numerous derivative packages to inflate developer reputation scores.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.
Using compromised packages can lead to security vulnerabilities, including unauthorized access to your codebase and potential data breaches.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risk.
