Malicious Code Vulnerability in appalling_chameleon_z3n Package

appalling_chameleon_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93246: Malicious code in appalling_chameleon_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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The appalling_chameleon_z3n package is part of the npm ecosystem, which is used for managing JavaScript packages. It is associated with the tea.xyz token reward campaign, which has been known to flood npm with various packages. This package, like others in the campaign, is designed to manipulate npm's publishing system, potentially harming developers and users by inflating reputation scores through malicious practices.

Vulnerability Detail

The vulnerability in the appalling_chameleon_z3n package originates from its association with a malicious campaign that employs scripts to automatically generate and publish derivative packages. These scripts modify the package.json file to remove private flags, alter version numbers, and create random package names, ultimately leading to the pollution of the npm registry. This can result in compromised developer reputations and the proliferation of potentially harmful packages.

How To Fix

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

npm uninstall appalling_chameleon_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 workaround, you can temporarily avoid using the appalling_chameleon_z3n package by removing it from your dependencies and replacing it with a trusted alternative. Ensure to audit your package-lock.json file for any other potentially vulnerable packages.

Conclusion

The appalling_chameleon_z3n package contains a significant vulnerability that can lead to malicious activities within the npm ecosystem. It is crucial for developers to be aware of this issue, remove the affected package, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for appalling_chameleon_z3n →

Share this vulnerability

FAQ

It is an npm package associated with a token reward campaign that has been identified as malicious.

The vulnerability can lead to the pollution of the npm registry and compromise your project's integrity by introducing malicious code.

You should remove the appalling_chameleon_z3n package from your project and monitor for any updates or patches.

You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

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

How To Fix

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

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