Malicious Code Injection in charliemiller Package - npm Vulnerability
Summary
MAL-2025-171024: Malicious code in charliemiller (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 charliemiller package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is likely involved in the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of charliemiller is not well-defined due to its malicious nature, but it is associated with generating and publishing derivative packages that can inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in the charliemiller package originates from its involvement in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of the software supply chain. The malicious payload can potentially allow unauthorized access to sensitive information or lead to the installation of other malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall charliemillerIf 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 prevent the installation of the charliemiller package by using npm's package-lock.json file to lock down your dependencies. Ensure that you do not include charliemiller in your dependencies or devDependencies sections.
Conclusion
The charliemiller package poses a significant security risk due to its malicious behavior of modifying package files and republishing variants. It is essential to remove this package from your project and monitor your dependencies for any potential vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software supply chain.
See every vulnerability recorded for charliemiller →
FAQ
The charliemiller package is an npm package that has been identified as malicious, involved in a campaign to inflate developer reputation scores through the publication of derivative packages.
The vulnerability can lead to the installation of malicious code, which may compromise your application's security and integrity by allowing unauthorized access or data leakage.
You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can help identify if your application is affected by this vulnerability.
If you have installed charliemiller, you should immediately uninstall it using the command 'npm uninstall charliemiller' and ensure your dependencies are secure.
To prevent similar vulnerabilities, regularly audit your dependencies using tools like Vulert and keep your packages updated to their latest versions.
