Malicious Code Injection in galacticgenius Package

galacticgenius Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171242: Malicious code in galacticgenius (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 galacticgenius package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through token reward systems, making them a significant threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the galacticgenius package arises from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to publish numerous variants of the package, thereby polluting the npm registry and potentially compromising the security of applications that depend on it. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been associated with various malicious npm packages.

How To Fix

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

npm uninstall galacticgenius

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 galacticgenius package and replace it with a reputable alternative that provides similar functionality. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The galacticgenius package poses a significant security risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action should be taken to remove this package from any projects.

See every vulnerability recorded for galacticgenius →

Share this vulnerability

FAQ

The galacticgenius package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the publication of derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the security of applications that depend on the galacticgenius package and its derivatives.

If you have installed the galacticgenius package, you should uninstall it immediately using 'npm uninstall galacticgenius' and review your project's dependencies for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software. You can also check your application for vulnerabilities using the Vulert playground without any signup.

Yes, you should look for reputable alternatives that provide similar functionality but do not have a history of malicious activity. Always check the package's reputation and reviews before use.

How To Fix

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

npm uninstall galacticgenius

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