Malicious Code Injection in georgejackson Package: npm Vulnerability Summary
Summary
MAL-2025-171259: Malicious code in georgejackson (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 georgejackson package is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to manage dependencies efficiently. However, this package has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms, leading to potential security risks for developers and their applications.
Vulnerability Detail
The vulnerability originates from the georgejackson package being associated with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry and inflate developer reputation scores fraudulently, posing significant risks to the integrity of the software supply chain.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall georgejacksonIf 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 georgejackson package and any packages that depend on it. Ensure that your project does not include any references to this package in your package.json file.
Conclusion
The georgejackson package poses a significant security risk due to its association with a malicious campaign that manipulates npm's publishing process. It is crucial for developers to remove this package from their projects and regularly audit their dependencies to maintain the integrity of their applications.
See every vulnerability recorded for georgejackson →
FAQ
The georgejackson package is an npm package that has been identified as part of a malicious campaign targeting the npm registry.
This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application and its dependencies.
You should uninstall the georgejackson package immediately and audit your project for any other vulnerabilities.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your 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 requiring any signup.
