Malicious Code Injection in lesser_peafowl-notthedev Package

lesser_peafowl-notthedev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105091: Malicious code in lesser_peafowl-notthedev (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 lesser_peafowl-notthedev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is suspected to be involved in a token reward campaign that has led to the proliferation of malicious packages on npm. Its primary function is to facilitate the development and distribution of JavaScript applications, but it has been compromised to serve malicious purposes.

Vulnerability Detail

The vulnerability in the lesser_peafowl-notthedev package originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, potentially leading to security risks for users who unknowingly install these compromised packages.

How To Fix

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

npm uninstall lesser_peafowl-notthedev

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

Conclusion

The lesser_peafowl-notthedev package has been identified as containing malicious code that can compromise the integrity of applications using it. Users are advised to update or remove the package to protect their projects from potential threats. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for lesser_peafowl-notthedev →

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 publication of compromised packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, you can determine if your application is affected by this vulnerability.

Using compromised packages can lead to security vulnerabilities, data breaches, and unauthorized access to your application, potentially compromising user data and application integrity.

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

If you cannot update the package right away, consider removing it from your project as a temporary measure to mitigate the risk of malicious code execution.

How To Fix

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

npm uninstall lesser_peafowl-notthedev

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