Which versions of update-db are malicious?

The following npm versions of update-db are flagged malicious: 99.1.0, 99.1.1. Treat any of these as compromised.

How do I remediate update-db if I installed it?

Remove update-db from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed update-db — how do I know if it already compromised me?

If update-db was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find update-db across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for update-db (2 malicious versions).

Malicious package

update-dbnpm

Advisory published May 1, 2026Updated May 12, 2026

update-db is a confirmed malicious npm package (MAL-2026-3315) that executes malicious code on install (malicious versions 99.1.0, 99.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in update-db (npm)

MAL-2026-3315

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall update-db

What this malware does

The package update-db was found to contain malicious code.

The OpenSSF Package Analysis project identified 'update-db' @ 99.1.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

99.1.099.1.1

Indicators of compromise (SHA-256)

188c4543894354956bdb0ef341ed98247a992c1ab7a8873fa6ac1c7533e9b1c0

6e88fcc9e357cdf912ec18cb28b728eb10d4f9369e5e4f16e321e8ce62fd86f2

9b606e43d802d06fa7b5d14f020e7727886462320dd05dca09c16887b15d5a37

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for update-db (2 malicious versions).
If you installed it — respond
Remove update-db from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If update-db was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. update-db on npm has been identified as a malicious package (versions 99.1.0, 99.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks update-db-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database