Malicious Code Injection in lazy_panther_0xrequest Package

lazy_panther_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105035: Malicious code in lazy_panther_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 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

The lazy_panther_0xrequest package is part of the npm ecosystem, typically used for various web development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability in the lazy_panther_0xrequest package stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. It generates random package names and continuously republishes variants, polluting the npm registry. This can lead to security risks, including unauthorized access to sensitive information and potential exploitation of affected applications.

How To Fix

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

npm uninstall lazy_panther_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 avoid using the lazy_panther_0xrequest package and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The lazy_panther_0xrequest package poses a significant security risk due to its malicious code that alters package configurations and floods the npm registry. It is crucial to remove this package and monitor your projects for vulnerabilities to ensure the security of your applications.

See every vulnerability recorded for lazy_panther_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

The vulnerability can lead to unauthorized modifications in your package.json file, potentially exposing your application to security risks.

You should uninstall the lazy_panther_0xrequest package immediately and check for any alternative packages that are safe to use.

Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.

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

How To Fix

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

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