Malicious Code Injection in Redundant Chameleon 0xRequest Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107795: Malicious code in redundant_chameleon_0xrequest (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 'redundant_chameleon_0xrequest' package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the publishing of derivative packages with randomized names, which can inflate developer reputation scores for token rewards. However, this functionality has led to significant security concerns, as the package contains malicious scripts that manipulate its own metadata.

Vulnerability Detail

The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the package but also leads to pollution of the npm registry, making it difficult for developers to trust legitimate packages. The scripts involved are typically named auto.js, autopublish.js, autopublish2.js, and autopublish3.js, and they continuously republish variants of the package, exacerbating the issue.

How To Fix

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

npm uninstall redundant_chameleon_0xrequest

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 this package by removing it from your dependencies. You can do this by executing the following command in your project directory: npm uninstall redundant_chameleon_0xrequest. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The 'redundant_chameleon_0xrequest' package poses a significant security risk due to its malicious code that alters package metadata and republish variants. It is crucial for developers to remove this package from their projects and consider using safer alternatives. Monitoring tools like Vulert can aid in identifying such vulnerabilities in real-time.

See every vulnerability recorded for redundant_chameleon_0xrequest →

Share this vulnerability

FAQ

The package contains malicious code that alters its own metadata and republish variants, leading to npm registry pollution.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, Vulert can help you identify affected packages.

You should uninstall the package immediately using the command: npm uninstall redundant_chameleon_0xrequest.

Yes, consider looking for other npm packages that offer similar functionality without the security risks associated with redundant_chameleon_0xrequest.

Utilize tools like Vulert, which provides real-time monitoring for vulnerabilities in your open-source dependencies without requiring code access or installation.

How To Fix

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

npm uninstall redundant_chameleon_0xrequest

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