Malicious Code Injection in GalacticCrafter Package
Summary
MAL-2025-171240: Malicious code in galacticcrafter (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
GalacticCrafter is an npm package designed for creating and managing galactic-themed projects. It allows developers to easily generate assets and manage dependencies for their applications. However, it has recently been identified as part of a malicious campaign that exploits npm's package management system, leading to serious security concerns.
Vulnerability Detail
The vulnerability originates from a malicious code injection within the GalacticCrafter package, which is part of a broader scheme involving the tea.xyz token reward campaign. This campaign floods the npm registry with derivative packages that contain scripts designed to modify package.json files, removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants can lead to pollution of the npm registry and compromise developer reputation scores.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall galacticcrafterIf 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 GalacticCrafter package from your project by executing: npm uninstall galacticcrafter. This will prevent any malicious code from executing while you assess alternative packages or wait for a secure version.
Conclusion
The GalacticCrafter package has been identified as vulnerable due to malicious code that can compromise the integrity of npm packages. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects and maintain the integrity of the npm registry.
See every vulnerability recorded for galacticcrafter →
FAQ
The vulnerability involves malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
If immediate updates are not possible, consider uninstalling the package as a temporary measure to mitigate risks.
Yes, the impacts include potential pollution of the npm registry and compromised developer reputation scores due to the automatic generation of malicious packages.
Detailed information can be found in the vulnerability report published by Amazon Inspector, which outlines the specifics of the malicious code.
