Malicious Code Injection in random_piranha_z3n: A Threat to npm Packages

random_piranha_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96181: Malicious code in random_piranha_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

random_piranha_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package, like others in the campaign, is designed to exploit the npm ecosystem by generating and publishing derivative packages with randomized names. The goal of these malicious packages is to inflate developer reputation scores for token rewards associated with the tea.xyz protocol.

Vulnerability Detail

The vulnerability in random_piranha_z3n stems from its inclusion in a campaign that utilizes autopublish scripts to create and publish numerous derivative packages. These scripts modify the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to pollution of the npm registry. The malicious behavior can result in developers unknowingly using compromised packages, potentially leading to security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall random_piranha_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 random_piranha_z3n package and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your package dependencies to identify and remove any potentially malicious packages.

Conclusion

The random_piranha_z3n package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant about the packages they use and to regularly audit their dependencies to maintain the integrity and security of their applications.

See every vulnerability recorded for random_piranha_z3n →

Share this vulnerability

FAQ

random_piranha_z3n is an npm package identified as part of a malicious campaign that generates and publishes derivative packages to manipulate developer reputation scores.

The vulnerability can lead to the inclusion of compromised packages in your application, which may introduce security risks and affect the integrity of your software.

If you have installed random_piranha_z3n, you should uninstall it immediately using 'npm uninstall random_piranha_z3n' and review your other dependencies for similar vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application against known vulnerabilities using the Vulert playground without any signup.

Currently, there are no specific patches for random_piranha_z3n. The best course of action is to remove the package and ensure your project dependencies are secure.

How To Fix

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

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