Malicious Code Detected in galaxy-sequelize-nebula-gravity Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21133: Malicious code in galaxy-sequelize-nebula-gravity (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The galaxy-sequelize-nebula-gravity package is an npm library designed to facilitate interactions with Sequelize, a popular ORM for Node.js. This package aims to simplify database operations and enhance productivity for developers working with relational databases. However, it has been found to contain malicious code, posing significant risks to users who integrate it into their applications.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the galaxy-sequelize-nebula-gravity package. This code can potentially compromise the security of applications that utilize this package, leading to unauthorized access, data breaches, or other harmful effects. The malicious nature of the code was identified through security assessments, highlighting the importance of scrutinizing third-party packages before integration.

How To Fix

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

npm uninstall galaxy-sequelize-nebula-gravity

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, consider using alternative packages that provide similar functionality without the associated risks. Always ensure to review the security status of any new package before integration.

Conclusion

The discovery of malicious code in the galaxy-sequelize-nebula-gravity package underscores the importance of vigilance when using third-party libraries. Users are advised to remove the package and explore safer alternatives while keeping an eye on security updates.

See every vulnerability recorded for galaxy-sequelize-nebula-gravity →

Share this vulnerability

FAQ

It is an npm library designed to work with Sequelize, providing tools for easier database interactions.

The malicious code was identified through security assessments conducted by Amazon Inspector.

Using this package can lead to unauthorized access to your application, data breaches, and other security vulnerabilities.

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.

Immediately uninstall the package and consider using alternative solutions. Monitor your application for any unusual activity.

How To Fix

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

npm uninstall galaxy-sequelize-nebula-gravity

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