Malicious Code Vulnerability in accepted_zebra_z3n Package

accepted_zebra_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93098: Malicious code in accepted_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 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 accepted_zebra_z3n package is part of the npm ecosystem and appears to be 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 compromised to include malicious scripts that can alter project configurations and publish harmful variants.

Vulnerability Detail

The vulnerability in the accepted_zebra_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 that pollute the npm registry, potentially compromising the integrity of projects that depend on this package.

How To Fix

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

npm uninstall accepted_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 workaround, you can remove the accepted_zebra_z3n package from your project by executing 'npm uninstall accepted_zebra_z3n'. This will prevent any malicious scripts from executing until a secure version is available.

Conclusion

The accepted_zebra_z3n package has been identified as containing malicious code that can compromise project integrity. It is crucial to take immediate action by updating or removing the package to safeguard your application from potential threats.

See every vulnerability recorded for accepted_zebra_z3n →

Share this vulnerability

FAQ

The accepted_zebra_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.

The vulnerability can lead to unauthorized modifications in your project files and the potential pollution of the npm registry, affecting the integrity of your dependencies.

If you are using accepted_zebra_z3n, you should uninstall the package immediately and monitor for any updates or patches.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. Visit https://vulert.com for more information.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

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