Malicious Code Injection in hichambaguette Package: npm Vulnerability

hichambaguette Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171310: Malicious code in hichambaguette (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The hichambaguette package is part of the npm ecosystem, primarily used for various JavaScript applications. It has gained attention due to its involvement in the tea.xyz token reward campaign, which has led to the proliferation of malicious packages designed to manipulate npm's registry. This package, like others in the campaign, is engineered to inflate developer reputation scores through automated publishing of derivative packages.

Vulnerability Detail

The vulnerability in the hichambaguette package originates from its design to include malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, contributing to the pollution of the npm registry. The ramifications include potential exposure of sensitive data, unauthorized access to systems, and a compromised npm ecosystem, which can affect developers relying on legitimate packages.

How To Fix

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

npm uninstall hichambaguette

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 hichambaguette package from your project by executing: npm uninstall hichambaguette. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The hichambaguette package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remain vigilant, update their packages, and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for hichambaguette →

Share this vulnerability

FAQ

The hichambaguette package is an npm package that has been linked to a malicious campaign aimed at manipulating npm's registry.

The vulnerability can lead to unauthorized changes in your package.json file, potentially exposing sensitive information and compromising your application's integrity.

If you have installed hichambaguette, it is crucial to uninstall it immediately and monitor your project for any unusual activity.

You can use tools like 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 hichambaguette

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