Malicious Code Injection in bewildered_llama_requirement Package

bewildered_llama_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93374: Malicious code in bewildered_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 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 'bewildered_llama_requirement' package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, this package has been identified as part of a malicious campaign linked to the tea.xyz token reward system, which aims to inflate developer reputation scores through deceptive practices.

Vulnerability Detail

The vulnerability arises from malicious code embedded within the 'bewildered_llama_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 intent is to continuously republish these variants, polluting the npm registry and potentially compromising the integrity of projects that depend on this package. The origin of this vulnerability is traced back to a campaign that floods npm with such malicious packages, specifically targeting developers seeking token rewards.

How To Fix

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

npm uninstall bewildered_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 'bewildered_llama_requirement' package from your project by executing: npm uninstall bewildered_llama_requirement. This will prevent any malicious code from executing while you seek a secure alternative.

Conclusion

The 'bewildered_llama_requirement' package poses a significant risk due to its embedded malicious code aimed at manipulating npm registry entries. It is essential to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help in monitoring and identifying such vulnerabilities in the future.

See every vulnerability recorded for bewildered_llama_requirement →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

The vulnerability can lead to unauthorized modifications in your project's package.json, potentially compromising its integrity and security.

You should uninstall the package immediately and check for any other dependencies that may be affected.

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

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.

How To Fix

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

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