Malicious Code Injection in charlie-teadev Package: A Threat to npm Users
Summary
MAL-2025-100343: Malicious code in charlie-teadev (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The charlie-teadev package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only undermines the integrity of the npm registry but also poses a significant risk to developers who may unknowingly use these compromised packages.
Vulnerability Detail
The vulnerability in the charlie-teadev package originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially leading to the installation of compromised packages by unsuspecting developers. The ramifications include the risk of executing malicious code, loss of data integrity, and damage to developer reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall charlie-teadevIf 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, avoid using the charlie-teadev package and consider using alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before installation.
Conclusion
The charlie-teadev package poses a significant threat to npm users due to its malicious behavior, which can compromise project integrity and developer reputation. It is crucial to remove this package and monitor for vulnerabilities using tools like Vulert to ensure the security of your applications.
See every vulnerability recorded for charlie-teadev →
FAQ
The charlie-teadev package is part of a malicious campaign that floods npm with packages designed to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the installation of compromised packages, execution of malicious code, and potential data loss or corruption.
You should uninstall the charlie-teadev package immediately using 'npm uninstall charlie-teadev' and check for any other affected packages.
Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
