Malicious Code Injection in galaxywatcher Package: npm Vulnerability Overview

galaxywatcher Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171252: Malicious code in galaxywatcher (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

The galaxywatcher package is part of the npm ecosystem, typically used for various functionalities within JavaScript applications. However, it has been identified as part of a malicious campaign that exploits npm's package publishing system. This vulnerability allows attackers to manipulate package metadata and publish harmful derivatives, potentially affecting developers and users relying on this package.

Vulnerability Detail

The vulnerability stems from the galaxywatcher package being involved in a token reward campaign that floods the npm registry with malicious packages. These packages contain scripts designed to modify the package.json file, removing private flags and altering version numbers. The scripts generate random package names and continuously republish variants, leading to pollution of the npm registry and potential security risks for users who unknowingly install these packages.

How To Fix

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

npm uninstall galaxywatcher

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 avoid using the galaxywatcher package until a secure version is released. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.

Conclusion

The galaxywatcher package has been identified as a vector for malicious code injection, posing significant risks to applications that utilize it. It is crucial for developers to update or remove this package and to monitor their dependencies for vulnerabilities to maintain application security.

See every vulnerability recorded for galaxywatcher →

Share this vulnerability

FAQ

The galaxywatcher package is an npm package used in JavaScript applications, but it has been compromised and is now associated with malicious activities.

If your application uses the galaxywatcher package, it may inadvertently install malicious code that can compromise your application's integrity and security.

You should immediately update the package to a patched version or remove it from your project to mitigate any potential risks.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software 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 requiring any signup.

How To Fix

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

npm uninstall galaxywatcher

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