Malicious Code Injection in surrounding_llama_z3n Package

surrounding_llama_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96896: Malicious code in surrounding_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 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 surrounding_llama_z3n package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the surrounding_llama_z3n package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising the security of applications that depend on these packages. The malicious payload is designed to exploit the npm ecosystem by creating numerous derivative packages that can mislead developers and users.

How To Fix

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

npm uninstall surrounding_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 workaround, you can monitor your package dependencies using tools like Vulert, which allows you to check for vulnerabilities in your package-lock.json file. You can access the Vulert playground at https://vulert.com/scanner to see if your application is affected by this vulnerability without needing to sign up.

Conclusion

The surrounding_llama_z3n package poses a significant security risk due to its malicious code that modifies package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies.

See every vulnerability recorded for surrounding_llama_z3n →

Share this vulnerability

FAQ

The surrounding_llama_z3n package is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

This vulnerability can lead to the injection of malicious code and the pollution of the npm registry, potentially compromising the security and integrity of your application.

You should uninstall the surrounding_llama_z3n package immediately using 'npm uninstall surrounding_llama_z3n' and check your project for any other affected packages.

Yes, you can use tools like Vulert to monitor your package-lock.json file for vulnerabilities in real-time.

No, the surrounding_llama_z3n package is known to be malicious and should be removed entirely rather than patched.

How To Fix

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

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