Malicious Code Injection in visual_lizard_z3n Package - npm Vulnerability

visual_lizard_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-91976: Malicious code in visual_lizard_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The visual_lizard_z3n package is part of the npm ecosystem, primarily used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that exploits npm's package publishing system. This package is associated with the tea.xyz token reward initiative, which has led to the proliferation of numerous derivative packages aimed at inflating developer reputation scores.

Vulnerability Detail

The vulnerability in the visual_lizard_z3n package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall visual_lizard_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 visual_lizard_z3n package until a secure version is released. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access or installation. You can check for vulnerabilities in your application using the Vulert playground at https://vulert.com/scanner.

Conclusion

The visual_lizard_z3n package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for visual_lizard_z3n →

Share this vulnerability

FAQ

The visual_lizard_z3n package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.

The vulnerability can lead to the introduction of malicious code in your application, potentially compromising its security and integrity.

If you are using visual_lizard_z3n, you should update to a patched version if available or remove the package from your project to mitigate risks.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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