Malicious Code in sporting_gorilla_replicate_automation: A Threat to npm Ecosystem
Summary
MAL-2025-109032: Malicious code in sporting_gorilla_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 'sporting_gorilla_replicate_automation' package is part of a broader campaign that exploits the npm ecosystem by flooding it with malicious packages. These packages are designed to manipulate developer reputation scores through automated publishing of derivative packages. The vulnerability stems from the package's ability to modify critical files, such as package.json, leading to potential security risks and pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'sporting_gorilla_replicate_automation' originates from its association with the tea.xyz token reward campaign, which employs autopublish scripts to create and publish numerous derivative packages with randomized names. This malicious behavior includes altering package.json to remove private flags, changing version numbers, and continuously republishing variants, which can lead to significant pollution of the npm registry and compromise the integrity of the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sporting_gorilla_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 avoid using the 'sporting_gorilla_replicate_automation' package and monitor your dependencies for any signs of malicious activity. Regularly audit your npm packages using the command: npm audit.
Conclusion
The 'sporting_gorilla_replicate_automation' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential to remove this package and monitor your dependencies to maintain the security and integrity of your applications. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities effectively.
See every vulnerability recorded for sporting_gorilla_replicate_automation →
FAQ
The package contains malicious code that modifies package.json and publishes derivative packages, which can pollute the npm registry.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without any signup.
You should remove the package from your project and monitor for any updates or patches that may address the vulnerability.
Regularly audit your dependencies and use tools like Vulert to monitor for open-source vulnerabilities in real-time.
Failing to address this vulnerability can lead to compromised application integrity, security risks, and potential exploitation by malicious actors.
