Malicious Code Injection in identical_piranha_0xrequest Package

identical_piranha_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103934: Malicious code in identical_piranha_0xrequest (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The identical_piranha_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate automated publishing of derivative packages, which can inflate developer reputation scores. However, it has been compromised to include malicious scripts that alter package metadata and publish harmful variants.

Vulnerability Detail

The vulnerability originates from the malicious code embedded in the identical_piranha_0xrequest package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers who unknowingly use these packages.

How To Fix

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

npm uninstall identical_piranha_0xrequest

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, avoid using the identical_piranha_0xrequest package and consider alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.

Conclusion

The identical_piranha_0xrequest package has been identified as containing malicious code that poses significant risks to developers and the npm ecosystem. It is crucial to remove this package and monitor your projects for vulnerabilities to maintain security.

See every vulnerability recorded for identical_piranha_0xrequest →

Share this vulnerability

FAQ

The malicious code can lead to the exposure of sensitive information and the pollution of the npm registry with harmful packages.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

If you have installed the identical_piranha_0xrequest package, uninstall it immediately and consider using a secure alternative.

Yes, you should look for well-reviewed and maintained packages that offer similar functionality without the associated risks.

Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities in your software.

How To Fix

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

npm uninstall identical_piranha_0xrequest

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