Malicious Code Injection in key_snipe_z3n Package
Summary
MAL-2025-95170: Malicious code in key_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 key_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 targeting npm users, specifically linked to the tea.xyz token reward initiative. The package is designed to manipulate npm registry entries, affecting the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in the key_snipe_z3n package originates from its inclusion in 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. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, potentially leading to security risks for users who inadvertently install these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall key_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 avoid using the key_snipe_z3n package and monitor your project's dependencies for any malicious activity. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The key_snipe_z3n package poses a significant risk due to its malicious behavior, which can compromise the integrity of the npm registry and affect applications using it. It is crucial to remove this package and monitor your dependencies for vulnerabilities.
See every vulnerability recorded for key_snipe_z3n →
FAQ
key_snipe_z3n is an npm package that has been identified as part of a malicious campaign aimed at manipulating npm registry entries.
The vulnerability can lead to the installation of malicious packages that may compromise your application's integrity and security.
You should remove the key_snipe_z3n package from your project and monitor your dependencies for any further vulnerabilities.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
