Malicious Code Injection in galaxygazer: A Threat to npm Users

galaxygazer Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171247: Malicious code in galaxygazer (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

galaxygazer is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities within the ecosystem, but it has been compromised. The vulnerability stems from the package's involvement in a scheme that floods the npm registry with malicious derivatives, potentially harming developers and users alike.

Vulnerability Detail

The vulnerability in galaxygazer originates from its association with a malicious campaign that employs autopublish scripts to generate and publish derivative packages with randomized names. This behavior not only inflates developer reputation scores for token rewards but also modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, polluting the npm registry. The ramifications include potential security risks for users who unknowingly install these compromised packages, leading to further exploitation.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall galaxygazer

If 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 galaxygazer package by using the following command: npm uninstall galaxygazer. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.

Conclusion

The galaxygazer package has been identified as having a significant vulnerability due to its involvement in a malicious campaign. Users are advised to take immediate action by updating or removing the package to protect their projects. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for galaxygazer →

Share this vulnerability

FAQ

galaxygazer is an npm package associated with the tea.xyz token reward campaign, designed to facilitate certain functionalities but has been compromised.

The vulnerability can lead to the installation of malicious packages that modify your project files and potentially expose your application to security risks.

If you have installed galaxygazer, it is crucial to update or uninstall the package immediately to mitigate any risks.

You can use Vulert, which requires only your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall galaxygazer

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback