Malicious Code Injection in medieval_piranha_0xrequest Package

medieval_piranha_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105765: Malicious code in medieval_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 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 medieval_piranha_0xrequest package is part of the npm ecosystem, designed for developers to create and manage applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities. This package is linked to the tea.xyz token reward scheme, which incentivizes the creation of numerous derivative packages to inflate developer reputation scores.

Vulnerability Detail

The vulnerability in the medieval_piranha_0xrequest package originates from its association with a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This behavior can lead to security risks, including the potential for unauthorized access to sensitive information and the compromise of developer environments.

How To Fix

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

npm uninstall medieval_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, you can restrict the use of the medieval_piranha_0xrequest package in your project by implementing strict package management practices and using tools like Vulert to monitor your dependencies. You can check for vulnerabilities in your application using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The medieval_piranha_0xrequest package poses a significant security risk due to its malicious code that modifies package configurations and repopulates the npm registry with harmful variants. It is essential to remove this package and monitor your dependencies to maintain a secure development environment.

See every vulnerability recorded for medieval_piranha_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.

The vulnerability can lead to unauthorized modifications in your package.json file, potentially exposing your application to security risks and cluttering the npm registry.

You should uninstall the medieval_piranha_0xrequest package immediately using the command npm uninstall medieval_piranha_0xrequest.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file.

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

How To Fix

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

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