Malicious Code Injection in shared_viper_z3n Package - npm Vulnerability
Summary
MAL-2025-96556: Malicious code in shared_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 shared_viper_z3n package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that inflate developer reputation scores. This package, like others in the campaign, is designed to automate the generation and publication of derivative packages, often leading to security risks and registry pollution.
Vulnerability Detail
The vulnerability in the shared_viper_z3n package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to publish numerous variants of the package, thereby compromising the integrity of the npm registry. The malicious payload can lead to unauthorized access and manipulation of projects that depend on this package, posing significant risks to developers and their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall shared_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 shared_viper_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.
Conclusion
The shared_viper_z3n package poses a significant security risk due to its malicious code that alters project dependencies. It is crucial to remove this package from your projects and monitor for any vulnerabilities using tools like Vulert. Staying informed and proactive can help safeguard your applications from such threats.
See every vulnerability recorded for shared_viper_z3n →
FAQ
The shared_viper_z3n package is an npm package associated with the tea.xyz token reward campaign, which is known for flooding the npm registry with malicious packages.
The vulnerability can lead to unauthorized modifications of your project's dependencies, potentially compromising its security and integrity.
You should uninstall the shared_viper_z3n package immediately using 'npm uninstall shared_viper_z3n' and check for any other affected packages.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
