Malicious Code Injection in evolutionary_llama_z3n Package - npm Vulnerability

evolutionary_llama_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102297: Malicious code in evolutionary_llama_z3n (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The evolutionary_llama_z3n 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 known to flood the npm registry with malicious packages. The primary function of this package is to provide developers with tools or libraries, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability originates from the malicious code embedded in the evolutionary_llama_z3n 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 exploitation by attackers. This can result in compromised developer reputations and the spread of further malicious packages.

How To Fix

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

npm uninstall evolutionary_llama_z3n

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 evolutionary_llama_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The evolutionary_llama_z3n package has been identified as a source of malicious code that can compromise your project. It is crucial to remove this package and monitor your dependencies regularly to ensure the security of your applications. Utilizing tools like Vulert can help in identifying vulnerabilities in real-time.

See every vulnerability recorded for evolutionary_llama_z3n →

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.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, you can identify if your application is affected by this vulnerability.

Using compromised packages can lead to security vulnerabilities, unauthorized access to your application, and damage to your reputation as a developer.

Regularly audit your dependencies using tools like Vulert and keep your packages updated to minimize the risk of vulnerabilities.

Immediately uninstall the evolutionary_llama_z3n package and check your project for any unauthorized changes. Consider using alternative packages.

How To Fix

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

npm uninstall evolutionary_llama_z3n

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