Malicious Code Vulnerability in exclusive_peafowl-notthedev Package

exclusive_peafowl-notthedev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102352: Malicious code in exclusive_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 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 exclusive_peafowl-notthedev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards for developers by publishing derivative packages. However, it has been identified as containing malicious code that compromises its integrity and the security of applications that depend on it.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the exclusive_peafowl-notthedev package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of these variants. This behavior not only inflates developer reputation scores but also pollutes the npm registry, potentially affecting other packages and applications relying on npm.

How To Fix

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

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

Conclusion

The exclusive_peafowl-notthedev package contains a serious vulnerability due to embedded malicious code that alters package metadata and can lead to broader security issues. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing monitoring.

See every vulnerability recorded for exclusive_peafowl-notthedev →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to publish derivative packages.

The malicious code modifies your package.json, potentially leading to security vulnerabilities and pollution of the npm registry.

You should immediately update or uninstall the package to prevent any security risks.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.

How To Fix

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

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