Malicious Code Injection in considerable_piranha_z3n Package

considerable_piranha_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100878: Malicious code in considerable_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The considerable_piranha_z3n package is part of the npm ecosystem, often associated with token reward campaigns. It is designed to facilitate the automatic generation and publication of derivative packages. However, this package has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with unwanted variants.

Vulnerability Detail

The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards, leading to potential security risks such as registry pollution and unauthorized access to sensitive data.

How To Fix

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

npm uninstall considerable_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 considerable_piranha_z3n package and instead utilize alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package dependencies using tools like npm audit.

Conclusion

The considerable_piranha_z3n package poses significant security risks due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package and monitor for updates to safeguard your application.

See every vulnerability recorded for considerable_piranha_z3n →

Share this vulnerability

FAQ

It is an npm package associated with token reward campaigns, designed to automate the generation and publication of derivative packages.

The vulnerability can lead to registry pollution, unauthorized access to sensitive data, and potential security breaches.

You should remove the considerable_piranha_z3n package from your project and monitor for any updates or patches.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring a signup.

You can use tools like npm audit and Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.

How To Fix

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

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