Malicious Code Injection in galaxyobserver Package

galaxyobserver Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171250: Malicious code in galaxyobserver (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 galaxyobserver package is part of the npm ecosystem, typically used for various JavaScript applications. It is designed to facilitate certain functionalities within these applications. However, it has been identified as part of a malicious campaign that exploits npm's package publishing system, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability originates from the galaxyobserver package being associated with a token reward campaign that floods npm with malicious packages. These packages contain scripts that automatically modify the package.json file, removing private flags, altering version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry, compromising the integrity of the ecosystem and potentially exposing users to further security risks.

How To Fix

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

npm uninstall galaxyobserver

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 remove the galaxyobserver package from your project by executing the following command: npm uninstall galaxyobserver. This will prevent any malicious code from executing while you assess the situation.

Conclusion

The galaxyobserver package has been identified as a vector for malicious code injection, posing significant risks to developers and users. It is crucial to take immediate action by updating or removing the package to safeguard your applications. Utilizing tools like Vulert can enhance your security posture by providing real-time monitoring for vulnerabilities.

See every vulnerability recorded for galaxyobserver →

Share this vulnerability

FAQ

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

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can determine if your application is affected by this vulnerability.

Using the galaxyobserver package can lead to the exposure of your application to malicious code, which can compromise security and integrity.

Regularly updating your dependencies and using tools like Vulert can help monitor for vulnerabilities and ensure your packages are secure.

You can find detailed information about this vulnerability on the official GitHub repository and through security advisories related to npm packages.

How To Fix

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

npm uninstall galaxyobserver

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