Malicious Code Injection in petite_lizard_z3n: A Threat to npm Ecosystem

petite_lizard_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107055: Malicious code in petite_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 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 package petite_lizard_z3n is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, posing a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in petite_lizard_z3n stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This not only affects the reputation of legitimate developers but also creates a chaotic environment in the package management system, making it difficult for users to find trustworthy packages.

How To Fix

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

npm uninstall petite_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 petite_lizard_z3n package and monitor your project for any unauthorized changes to the package.json file. Implementing strict access controls and using tools like Vulert can help in identifying vulnerabilities in your dependencies.

Conclusion

The petite_lizard_z3n package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant about the packages they use and to regularly audit their dependencies to safeguard their projects from such vulnerabilities.

See every vulnerability recorded for petite_lizard_z3n →

Share this vulnerability

FAQ

petite_lizard_z3n is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.

The vulnerability can lead to unauthorized changes in your project's package.json file, potentially compromising the integrity of your application and making it difficult to manage dependencies.

You should uninstall the package immediately using 'npm uninstall petite_lizard_z3n' and review your project for any other potentially malicious packages.

Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and ensure that you only install packages from trusted sources.

Vulert is a tool that monitors your package-lock.json file for open-source vulnerabilities in real-time. You can use the Vulert playground to check if your application is affected by this vulnerability without any signup.

How To Fix

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

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