Malicious Code Injection in charlottethompson Package: A Threat to npm Users
Summary
MAL-2025-171031: Malicious code in charlottethompson (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 charlottethompson package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code components. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing system, leading to potential security risks for developers and their projects.
Vulnerability Detail
The vulnerability originates from the charlottethompson package being linked to a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to automatically modify the package.json file, removing private flags and changing version numbers. The malicious payload generates random package names and continuously republishes variants, which can lead to reputation inflation and pollution of the npm registry. This poses a significant risk as it can compromise the integrity of the npm ecosystem and potentially introduce harmful code into applications that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall charlottethompsonIf 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 charlottethompson package and search for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The charlottethompson package poses a significant risk due to its malicious code designed to exploit the npm registry. It is crucial for developers to remove this package from their projects and utilize monitoring tools like Vulert to stay informed about potential vulnerabilities. By taking these steps, developers can help protect their applications from security threats.
See every vulnerability recorded for charlottethompson →
FAQ
The charlottethompson package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
This vulnerability can compromise the integrity of your project by introducing malicious code, which may lead to security breaches or reputation damage.
If you have installed the charlottethompson package, you should uninstall it immediately using the command: npm uninstall charlottethompson.
Yes, tools like Vulert can monitor your project for open-source vulnerabilities in real-time using just the package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
