Malicious Code Injection in pleased_pony_requirement Package

pleased_pony_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95918: Malicious code in pleased_pony_requirement (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The pleased_pony_requirement package is an npm module that is part of a larger ecosystem of packages associated with the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities within the npm registry but has been compromised to include malicious code. The primary attributes of this package include its ability to publish and manage npm packages, but its vulnerability has led to the introduction of harmful scripts that can manipulate package metadata.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the pleased_pony_requirement package. This code is designed to automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants to the npm registry, leading to pollution of the registry and potential misuse of developer reputation scores. The ramifications include compromised package integrity, potential data breaches, and a significant impact on the npm ecosystem.

How To Fix

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

npm uninstall pleased_pony_requirement

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 pleased_pony_requirement package from your project by executing the following command: npm uninstall pleased_pony_requirement. This will prevent any malicious code from executing while you await a patched version.

Conclusion

The pleased_pony_requirement package has been identified as containing malicious code that poses significant risks to developers and the npm ecosystem. It is crucial to take immediate action by updating or uninstalling the package to mitigate these risks. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for pleased_pony_requirement →

Share this vulnerability

FAQ

It is an npm package that has been compromised to include malicious code aimed at manipulating package metadata and inflating developer reputation scores.

The malicious code can modify your package.json file, remove private flags, and republish variants, leading to potential data breaches and pollution of the npm registry.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

As a temporary measure, you can uninstall the pleased_pony_requirement package to prevent any malicious activity until a patched version is available.

Regularly check for updates in your npm packages and consider using tools like Vulert to monitor vulnerabilities in real-time.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall pleased_pony_requirement

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