Malicious Code Vulnerability in grotesque_skink_replicate_automation Package
Summary
MAL-2025-103405: Malicious code in grotesque_skink_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 grotesque_skink_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 the replication and publication of npm packages, often with randomized names. Its primary function is to inflate developer reputation scores for token rewards, but this functionality has been exploited for malicious purposes.
Vulnerability Detail
The vulnerability originates from the package's design, which includes autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants. This behavior pollutes the npm registry and can compromise the integrity of applications relying on this package. The malicious payload can potentially lead to unauthorized access or manipulation of the software environment.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall grotesque_skink_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 grotesque_skink_replicate_automation package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The grotesque_skink_replicate_automation package poses a significant risk due to its malicious code that alters package configurations and republishing behavior. It is crucial for developers to remove this package and monitor their applications for vulnerabilities to maintain security.
See every vulnerability recorded for grotesque_skink_replicate_automation →
FAQ
It is an npm package designed to automate the replication and publication of packages, often used in token reward campaigns.
The vulnerability can lead to unauthorized modifications in your application's dependencies, potentially compromising its security and integrity.
You should remove the package from your project and monitor for any updates or patches that may address the vulnerability.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
