Critical Malicious Code Vulnerability in Sequelization Package

sequelization Updated 02 Mar 2026

Summary

02/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1112: Malicious code in sequelization (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

Sequelization is an npm package designed for database interaction and management, providing developers with a streamlined interface for executing SQL queries and handling data. However, this package has been compromised, leading to severe security risks for any system utilizing it. The vulnerability allows malicious actors to gain unauthorized access to sensitive information stored on affected systems.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the Sequelization package. This code can fully compromise any computer on which the package is installed, potentially allowing attackers to access secrets and keys stored on the system. The origin of this malicious code has been traced back to a known malware source, making it imperative for users to take immediate action to secure their systems.

How To Fix

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

npm uninstall sequelization

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 workaround, users should ensure that they do not run any applications that depend on the Sequelization package until it has been removed and the system has been secured. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The Sequelization package has been compromised with malicious code, posing significant risks to users. Immediate action is required to remove the package and secure any sensitive information. Users should monitor their systems and consider alternative solutions for database management.

See every vulnerability recorded for sequelization →

Share this vulnerability

FAQ

Immediately remove the Sequelization package and rotate any secrets or keys stored on the affected system.

You can use Vulert's playground at Vulert Scanner to monitor and alert for open-source vulnerabilities in your application without needing to sign up.

Currently, there is no patched version available. Users are advised to remove the package entirely.

Failure to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and full system compromise.

It is recommended to find an alternative package that provides similar functionality without the associated security risks.

How To Fix

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

npm uninstall sequelization

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