Malicious Code Injection in poor_viper_z3n: A Threat to npm Ecosystem

poor_viper_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107142: Malicious code in poor_viper_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package poor_viper_z3n is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with random names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol.

Vulnerability Detail

The vulnerability in poor_viper_z3n arises from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants that pollute the npm registry. The origin of this issue is linked to the broader campaign that exploits npm's publishing mechanisms, posing risks such as reputation damage for developers and potential security threats for users of these packages.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall poor_viper_z3n

If 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 this malicious package by using npm's package-lock.json to monitor dependencies. You can also utilize the following command to uninstall the package: npm uninstall poor_viper_z3n.

Conclusion

The poor_viper_z3n package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and republishing harmful variants. It is essential for developers to be vigilant and remove such packages to maintain the integrity of their projects.

See every vulnerability recorded for poor_viper_z3n →

Share this vulnerability

FAQ

poor_viper_z3n is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and affecting its dependencies.

If you have installed poor_viper_z3n, it is crucial to uninstall it immediately and monitor your project for any further vulnerabilities.

You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just package-lock.json. You can also check your application using the Vulert playground without any signup.

Currently, there is no specific patched version available for poor_viper_z3n. It is advisable to remove the package and monitor for updates.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall poor_viper_z3n

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback