Most recent entries from all

bdu:2025-12664

EUVD-2026-252399

fkie_cve-2025-59037

DuckDB is an analytical in-process SQL database management system. On 08 September 2025, the DuckDB distribution for Node.js on npm was compromised with malware (along with several other packages). An attacker published new versions of four of DuckDB's packages that included malicious code to interfere with cryptocoin transactions* According to the npm statistics, nobody has downloaded these packages before they were deprecated. The packages and versions `@duckdb/node-api@1.3.3`, `@duckdb/node-bindings@1.3.3`, `duckdb@1.3.3`, and `@duckdb/duckdb-wasm@1.29.2` were affected. DuckDB immediately deprecated the specific versions, engaged npm support to delete the affected verions, and re-released the node packages with higher version numbers (1.3.4/1.30.0). Users may upgrade to versions 1.3.4, 1.30.0, or a higher version to protect themselves. As a workaround, they may also downgrade to 1.3.2 or 1.29.1.

GHSA-w62p-hx95-gf2c — DuckDB NPM packages 1.3.3 and 1.29.2 briefly compromised with malware

Affected: npm: duckdb, npm: @duckdb/node-api, npm: @duckdb/node-bindings, npm: @duckdb/duckdb-wasm

The DuckDB distribution for [Node.js](http://node.js/) on [npm](https://www.npmjs.com/) was compromised with malware (along with [several other packages](https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised)). An attacker published new versions of four of duckdb’s packages that included **malicious code to interfere with cryptocoin transactions**. The following packages and versions are affected:

- `@duckdb/node-api@1.3.3` - `@duckdb/node-bindings@1.3.3` - `duckdb@1.3.3` - `@duckdb/duckdb-wasm@1.29.2`

> Note: The current release version of DuckDB is 1.3.2, with 1.4.0 expected to be released on Sept 10th, 2025 (tomorrow as of this writing). We do not plan to ever release a “legit” DuckDB 1.3.3. Users should double-check that they are not accidentally updating to those affected versions.

We have ourselves noticed this *within four hours* of it happening. Here’s our response:

- As an immediate response, we have **deprecated** the specific versions. - We have reached out to npm support to **delete the affected versions**. They were so kind to do so. - We have also **re-released** the node packages with higher version numbers (1.3.4/1.30.0) as a further safeguard so the latest version of the package points to a safe version

We apologize for this issue. We are reviewing our internal processes to ensure the safety of future releases.

### Postmortem ###

On September 8th (Monday), the DuckDB maintainers received the following message from "...@npmjs.help":…