DuckDB NPM packages 1.3.3 and 1.29.2 briefly compromised with malware
duckdb-node
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| duckdb npm |
|
|
| @duckdb/node-api npm |
|
|
| @duckdb/node-bindings npm |
duckdb-node
| Product | Affected | Fixed in |
|---|---|---|
| duckdb npm |
|
|
| @duckdb/node-api npm |
|
|
| @duckdb/node-bindings npm |
≥ 1.3.3 · < 1.3.4-alpha.27
|
| @duckdb/duckdb-wasm npm |
|
|
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.
From the CVE record · GitHub_M
Four DuckDB npm package versions were published with malicious code that could interfere with cryptocoin transactions. The risk applies when an affected package version is installed and used; the input does not specify authentication or user-interaction requirements.
Check installations of duckdb, @duckdb/node-api, or @duckdb/node-bindings at version 1.3.3, and @duckdb/duckdb-wasm at version 1.29.2.