Malicious Code Injection in Aesthetic Zebra Z3N Package

aesthetic_zebra_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99231: Malicious code in aesthetic_zebra_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 Aesthetic Zebra Z3N package is part of the npm ecosystem, typically used for various aesthetic-related functionalities in web applications. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages, which can compromise the integrity of projects relying on it.

Vulnerability Detail

The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which employs autopublish scripts to generate and publish numerous derivative packages with randomized names. This malicious behavior modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly integrate these compromised packages into their projects.

How To Fix

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

npm uninstall aesthetic_zebra_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 measure, avoid using the Aesthetic Zebra Z3N package and consider alternative packages that provide similar functionality without the associated risks.

Conclusion

The Aesthetic Zebra Z3N package poses a significant security risk due to its association with malicious activities in the npm ecosystem. Developers are advised to remove this package from their projects and monitor for updates or alternatives to ensure the security of their applications.

See every vulnerability recorded for aesthetic_zebra_z3n →

Share this vulnerability

FAQ

It is an npm package that is part of a malicious campaign, designed to flood the npm registry with derivative packages.

Integrating this package can lead to security risks, including the potential for your project to be polluted with malicious code.

You should uninstall the package immediately using 'npm uninstall aesthetic_zebra_z3n' and look for alternatives.

Currently, there is no patched version available. It is recommended to remove the package until a safe version is released.

You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

How To Fix

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

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