Malicious Code Injection in splendid_viper_z3n Package - npm Vulnerability

splendid_viper_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109022: Malicious code in splendid_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The splendid_viper_z3n package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate npm's ecosystem by automatically generating and publishing derivative packages with randomized names. This behavior is primarily aimed at inflating developer reputation scores for token rewards, making it a significant concern for developers relying on npm for package management.

Vulnerability Detail

The vulnerability in the splendid_viper_z3n package originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages in their projects.

How To Fix

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

npm uninstall splendid_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 workaround, you can avoid using the splendid_viper_z3n package and replace it with an alternative package that provides similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in your software without requiring code access.

Conclusion

The splendid_viper_z3n package poses a significant risk due to its malicious behavior aimed at manipulating the npm ecosystem. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert. Staying informed and vigilant is crucial to maintaining the security of your projects.

See every vulnerability recorded for splendid_viper_z3n →

Share this vulnerability

FAQ

The splendid_viper_z3n package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.

Using the splendid_viper_z3n package can compromise your project's integrity by introducing malicious code and potentially affecting your application's security.

If you have installed the splendid_viper_z3n package, you should uninstall it immediately using the command npm uninstall splendid_viper_z3n.

You can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.

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.

How To Fix

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

npm uninstall splendid_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