Malicious Code Injection in charliemarshall: A Threat to npm Packages

charliemarshall Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171023: Malicious code in charliemarshall (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

charliemarshall is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate various functionalities within the npm ecosystem, but it has been compromised, leading to significant security concerns. The vulnerability stems from malicious scripts that manipulate the package's metadata and behavior, posing risks to developers and users alike.

Vulnerability Detail

The vulnerability in charliemarshall originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, potentially leading to further exploitation and misuse of the affected packages.

How To Fix

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

npm uninstall charliemarshall

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 charliemarshall package from your project until a secure version is released. You can do this by executing: npm uninstall charliemarshall. This will help prevent any potential exploitation while you await a fix.

Conclusion

The charliemarshall package has been compromised, leading to a significant vulnerability that affects npm users. It is essential to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help monitor and alert you to any vulnerabilities in your dependencies.

See every vulnerability recorded for charliemarshall →

Share this vulnerability

FAQ

charliemarshall is an npm package that was part of the tea.xyz token reward campaign, designed to facilitate various functionalities within the npm ecosystem.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing your project to further risks and pollution of the npm registry.

If you are using charliemarshall, it is recommended to update to the latest version or remove the package until a secure version is available.

You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json.

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

How To Fix

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

npm uninstall charliemarshall

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