Malicious Code Injection in upset_snipe_replicate_automation Package
Summary
MAL-2025-110217: Malicious code in upset_snipe_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 upset_snipe_replicate_automation package is part of the npm ecosystem, primarily used for automating certain tasks related to the snipe functionality. 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 has been flooding 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, leading to the continuous republishing of these variants. This behavior can inflate developer reputation scores fraudulently and pollute the npm registry, posing risks to developers and users relying on the integrity of npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall upset_snipe_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 upset_snipe_replicate_automation package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert, which alerts you in real-time for open-source vulnerabilities.
Conclusion
The upset_snipe_replicate_automation package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and users. Immediate action is required to remove the package and monitor for similar vulnerabilities in the future.
See every vulnerability recorded for upset_snipe_replicate_automation →
FAQ
It is an npm package designed for automating tasks related to snipe functionality, but it has been compromised with malicious code.
The malicious code modifies your package.json, removes private flags, and publishes variants that can pollute the npm registry, potentially affecting your project's integrity.
Yes, you can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
You should uninstall the package immediately using npm uninstall upset_snipe_replicate_automation and look for alternative solutions.
Regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.
