Malicious Code Injection in chameleon_lavender-31: A Threat to npm Packages

chameleon_lavender-31 Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97644: Malicious code in chameleon_lavender-31 (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

chameleon_lavender-31 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards through various scripts that automate the generation and publication of derivative packages. However, it has been identified as containing malicious code that compromises its integrity and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in chameleon_lavender-31 originates from its association with the tea.xyz token reward campaign, which floods the npm registry with numerous derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, potentially leading to security risks for developers who unknowingly use these compromised packages.

How To Fix

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

npm uninstall chameleon_lavender-31

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 chameleon_lavender-31 package until a patched version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The chameleon_lavender-31 package has been identified as containing malicious code that poses a significant risk to developers using npm. It is crucial to take immediate action by updating the package or finding alternatives to ensure the security of your applications.

See every vulnerability recorded for chameleon_lavender-31 →

Share this vulnerability

FAQ

chameleon_lavender-31 is an npm package involved in the tea.xyz token reward campaign, which automates the generation of derivative packages.

The vulnerability allows for the modification of package.json files, removal of private flags, and the generation of numerous derivative packages that can pollute the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground, you can check if your application is affected without any signup.

If you are using chameleon_lavender-31, you should update to the latest version or consider removing the package until a patch is available.

Detailed information about this vulnerability can be found in the vulnerability report, and you can also check resources like Vulert for real-time alerts.

How To Fix

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

npm uninstall chameleon_lavender-31

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