Malicious Code Injection in wrong_snipe_z3n Package - npm Vulnerability
Summary
MAL-2025-111042: Malicious code in wrong_snipe_z3n (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 wrong_snipe_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that targets developers by flooding the npm registry with derivative packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the wrong_snipe_z3n package originates from its involvement in the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the security of applications relying on these packages. The malicious payload can potentially allow unauthorized access to sensitive data or lead to further exploitation of affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wrong_snipe_z3nIf 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 prevent the installation of the wrong_snipe_z3n package by using npm's package-lock.json file to lock your dependencies. Ensure that your project does not include this package by checking your package.json and removing any references to it.
Conclusion
The wrong_snipe_z3n package poses a significant security risk due to its malicious code that modifies package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies.
See every vulnerability recorded for wrong_snipe_z3n →
FAQ
The wrong_snipe_z3n package is an npm package that has been identified as part of a malicious campaign to manipulate package metadata and inflate developer reputation scores.
The vulnerability can lead to unauthorized modifications of your package metadata, potentially compromising the security and integrity of your application.
If you have installed the wrong_snipe_z3n package, you should uninstall it immediately using 'npm uninstall wrong_snipe_z3n' and review your dependencies for any other malicious packages.
You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
