Malicious Code Injection in elegant_monkey_requirement Package

elegant_monkey_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94221: Malicious code in elegant_monkey_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 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 elegant_monkey_requirement package is an npm library that is part of a broader campaign involving the tea.xyz token reward system. This package is designed to facilitate certain functionalities within the npm ecosystem but has been compromised to serve malicious purposes. The vulnerability stems from its association with scripts that automate the generation and publication of derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in the elegant_monkey_requirement package originates from its inclusion in a malicious campaign that modifies package.json files to remove private flags and change version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to inflate developer reputation scores. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these malicious packages in their projects.

How To Fix

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

npm uninstall elegant_monkey_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 avoid using the elegant_monkey_requirement package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The elegant_monkey_requirement package has been identified as containing malicious code that can compromise the integrity of the npm ecosystem. It is crucial for developers to be aware of this vulnerability and take necessary actions to update or remove the affected package from their projects. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities in real-time.

See every vulnerability recorded for elegant_monkey_requirement →

Share this vulnerability

FAQ

The elegant_monkey_requirement package is an npm library that is part of a token reward campaign, which has been compromised to include malicious code.

If your project uses the elegant_monkey_requirement package, it may inadvertently include malicious code that can compromise your application's integrity and security.

You should immediately update the package to the latest version or remove it from your project to prevent any potential security risks.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.

Regularly updating your packages, using trusted sources, and employing monitoring tools like Vulert can help mitigate the risk of vulnerabilities in your projects.

How To Fix

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

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