Malicious Code Injection in Charlottelee Package: npm Vulnerability Overview

charlottelee Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171030: Malicious code in charlottelee (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 Charlottelee package is an npm library that has been implicated in a malicious campaign associated with the tea.xyz token reward initiative. This package is designed to facilitate various functionalities within the npm ecosystem but has been compromised to serve malicious purposes. The vulnerability stems from its ability to modify critical files and republish itself under different names, thus impacting the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the Charlottelee package originates from its inclusion in a broader malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the affected package but also pollutes the npm registry, potentially leading to security risks for developers who unknowingly use these malicious variants.

How To Fix

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

npm uninstall charlottelee

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 Charlottelee package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The Charlottelee package has been identified as a vector for malicious code injection, posing significant risks to developers and their projects. Immediate action is required to remove the package and safeguard your application from potential threats. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for charlottelee →

Share this vulnerability

FAQ

Charlottelee is an npm package that has been compromised to include malicious code as part of a token reward campaign.

The vulnerability can lead to unauthorized modifications in your package.json file and the potential introduction of malicious packages into your project.

You should uninstall the Charlottelee package immediately and monitor your project for any unusual behavior.

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

Regularly audit your dependencies, use tools like Vulert to monitor vulnerabilities, and stay updated with the latest security patches for your packages.

How To Fix

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

npm uninstall charlottelee

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