Malicious Code Injection in determined_snipe_z3n Package
Summary
MAL-2025-94007: Malicious code in determined_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 determined_snipe_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. It is often involved in token reward campaigns, specifically related to the tea.xyz protocol. This package, like others in its category, is designed to automate the generation and publication of derivative packages, which can lead to inflated developer reputation scores. However, it has been identified as containing malicious code that compromises its integrity and the security of projects that depend on it.
Vulnerability Detail
The vulnerability in the determined_snipe_z3n package originates from its association with a malicious campaign that floods the npm registry with derivative 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 the pollution of the npm registry. This behavior not only affects the integrity of the package itself but can also impact other projects that rely on it, potentially leading to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall determined_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 workaround, you can prevent the installation of the determined_snipe_z3n package by using the following command to uninstall it: npm uninstall determined_snipe_z3n. Additionally, ensure that your package-lock.json file is monitored for any unauthorized changes.
Conclusion
The determined_snipe_z3n package has been identified as containing malicious code that poses a significant risk to projects using it. Immediate action is required to remove this package and prevent potential security breaches. Monitoring tools like Vulert can assist in identifying vulnerabilities in your project.
See every vulnerability recorded for determined_snipe_z3n →
FAQ
It is an npm package involved in automated token reward campaigns, which has been identified as containing malicious code.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project, potentially introducing security risks.
You should uninstall the determined_snipe_z3n package immediately to mitigate any risks associated with its malicious code.
As of now, there is no patched version available. It is recommended to remove the package entirely.
You can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.
