Malicious Code Injection in pretty_leopon_0xrequest Package

pretty_leopon_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107239: Malicious code in pretty_leopon_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 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 pretty_leopon_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities within the npm registry but has been compromised, leading to significant security concerns. Its primary attributes include automatic publishing capabilities, which have been exploited to generate malicious variants that can affect developers' reputations and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the pretty_leopon_0xrequest package stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file, removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk of reputation damage to developers and potential exploitation of their applications.

How To Fix

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

npm uninstall pretty_leopon_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 remove the pretty_leopon_0xrequest package from your project by executing the following command: npm uninstall pretty_leopon_0xrequest. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The pretty_leopon_0xrequest package has been identified as containing malicious code that can compromise the security of applications using it. It is crucial for developers to take immediate action by updating or removing the package to protect their projects from potential threats.

See every vulnerability recorded for pretty_leopon_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been compromised and is associated with a malicious campaign aimed at inflating developer reputation scores.

The vulnerability can lead to the injection of malicious code, which may compromise your application's integrity and security.

You should immediately update the package to the latest version or remove it from your project to mitigate risks.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

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