Malicious Code Injection in visiting_viper_z3n Package
Summary
MAL-2025-91975: Malicious code in visiting_viper_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 visiting_viper_z3n package is part of the npm ecosystem, often utilized for various JavaScript applications. However, it has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the tea.xyz token reward system. This package is designed to automatically generate and publish derivative packages with randomized names, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in the visiting_viper_z3n package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which can lead to the proliferation of unwanted and potentially harmful packages in the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing capabilities to manipulate developer reputation scores. The ramifications include a polluted npm registry and potential security risks for developers who unknowingly install these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall visiting_viper_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 visiting_viper_z3n package altogether until a secure version is released. Additionally, consider using npm audit to identify and address vulnerabilities in your project.
Conclusion
The visiting_viper_z3n package poses a significant risk due to its malicious code that alters package metadata and contributes to npm registry pollution. It is crucial for developers to update their dependencies and utilize tools like Vulert to monitor for vulnerabilities effectively.
See every vulnerability recorded for visiting_viper_z3n →
FAQ
The visiting_viper_z3n package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The malicious code modifies your package.json file, potentially leading to the installation of unwanted packages and pollution of the npm registry.
You should update the package to the latest version using npm update visiting_viper_z3n and monitor your project for any unusual behavior.
Yes, regularly audit your dependencies using tools like npm audit and consider using Vulert to monitor for vulnerabilities in real-time.
Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without any signup using the Vulert playground.
