Malicious Code Injection in instant_skunk_replicate_automation Package
Summary
MAL-2025-104253: Malicious code in instant_skunk_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 instant_skunk_replicate_automation package is part of the npm ecosystem, primarily used for automating tasks related to package replication. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to potential security risks for developers using this package.
Vulnerability Detail
This vulnerability stems from the package's involvement in a token reward campaign that floods the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to reputation inflation and registry pollution. This behavior can compromise the integrity of the npm ecosystem and expose developers to further security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall instant_skunk_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 measure, you can avoid using the instant_skunk_replicate_automation package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The instant_skunk_replicate_automation package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. Developers should take immediate action to remove this package and monitor their projects for any unauthorized changes.
See every vulnerability recorded for instant_skunk_replicate_automation →
FAQ
It is an npm package used for automating package replication tasks, but it has been identified as malicious.
The vulnerability can lead to unauthorized changes in your package.json file, potentially compromising your project's integrity and security.
You should remove the package immediately and monitor your project for any unauthorized changes.
Yes, tools like Vulert can monitor your package-lock.json file 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 without any signup.
