Malicious Code Vulnerability in primitive_lizard_z3n Package

primitive_lizard_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96023: Malicious code in primitive_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 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 primitive_lizard_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the npm registry.

Vulnerability Detail

The vulnerability in the primitive_lizard_z3n package originates from its malicious payload, which 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 variants, polluting the npm registry and potentially affecting other developers and users relying on legitimate packages. The malicious scripts are designed to automate the process of creating and publishing these harmful packages, making it difficult to track and manage the impact.

How To Fix

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

npm uninstall primitive_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 primitive_lizard_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.

Conclusion

The primitive_lizard_z3n package contains a serious vulnerability due to its malicious code, which can lead to significant issues within the npm ecosystem. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity of their projects.

See every vulnerability recorded for primitive_lizard_z3n →

Share this vulnerability

FAQ

The primitive_lizard_z3n package is an npm package linked to the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially affecting other packages and developers. It may also compromise the integrity of your project if you rely on this package.

You should remove the primitive_lizard_z3n package from your project and monitor for any updates or patches that may be released.

Yes, Vulert allows you to monitor and alert for open-source vulnerabilities in your software using just the package-lock.json file. You can also use the Vulert playground to check if your application is affected by this vulnerability.

Regularly audit your dependencies, keep your packages updated, and use tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

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