Malicious Code Exploit in Comprehensive Llama Requirement Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93692: Malicious code in comprehensive_llama_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 Comprehensive Llama Requirement package is an npm library that is part of the tea.xyz token reward campaign. It is designed to facilitate the management of dependencies in JavaScript applications. However, this package 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 the package being part of a malicious campaign that floods the npm registry with derivative packages. It includes scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior can lead to the pollution of the npm registry and can potentially compromise the security of applications using this package, as it may allow unauthorized access or manipulation of the code.

How To Fix

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

npm uninstall comprehensive_llama_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 Comprehensive Llama Requirement package from your project by executing the following command: npm uninstall comprehensive_llama_requirement. This will prevent any malicious code from executing in your application until a secure version is available.

Conclusion

The Comprehensive Llama Requirement package has been identified as containing malicious code that poses a significant risk to applications using it. It is crucial to update or remove the package to mitigate these risks and ensure the security of your software.

See every vulnerability recorded for comprehensive_llama_requirement →

Share this vulnerability

FAQ

It is an npm library used for managing dependencies in JavaScript applications, but it has been compromised with malicious code.

The malicious code can modify your package.json file, potentially leading to unauthorized access and manipulation of your application.

You should check the npm registry for any updated versions of the Comprehensive Llama Requirement package that address this vulnerability.

As a workaround, you can uninstall the package to prevent any malicious code from executing in your application.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can also check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

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

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