Malicious Code Injection in cheerful_primate_requirement Package

cheerful_primate_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93523: Malicious code in cheerful_primate_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The cheerful_primate_requirement package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to the proliferation of malicious packages on npm. The primary function of this package is to facilitate token rewards, but its malicious nature compromises its integrity and the security of applications that depend on it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the cheerful_primate_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, which leads to the continuous republishing of these variants. The origin of this vulnerability is traced back to the tea.xyz token reward campaign, which aims to inflate developer reputation scores through the creation of derivative packages. The ramifications include potential exposure of sensitive data, pollution of the npm registry, and a compromised development environment.

How To Fix

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

npm uninstall cheerful_primate_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 cheerful_primate_requirement package from your project by executing the following command: npm uninstall cheerful_primate_requirement. This will prevent any malicious code from executing while you seek a secure alternative.

Conclusion

The cheerful_primate_requirement package poses a significant security risk due to its malicious code that alters package configurations and repopulates the npm registry with harmful variants. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for cheerful_primate_requirement →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, which has been found to contain malicious code.

The malicious code modifies your package.json file, potentially exposing sensitive information and polluting the npm registry.

You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.

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

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 cheerful_primate_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