For your digest
duckdb, @duckdb/node-api: DuckDB NPM packages 1.3.3 and 1.29.2 briefly compromised with malware
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- duckdb (npm): from 1.3.3, before 1.3.4
- @duckdb/node-api (npm): from 1.3.3, before 1.3.4-alpha.27
- @duckdb/node-bindings (npm): from 1.3.3, before 1.3.4-alpha.27
- @duckdb/duckdb-wasm (npm): from 1.29.2, before 1.30.0
The fix
duckdb (npm) fixed in 1.3.4
npmnpm install duckdb@1.3.4pnpmpnpm add duckdb@1.3.4yarnyarn add duckdb@1.3.4bunbun add duckdb@1.3.4Check what is installednpm ls duckdbPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency duckdb to 1.3.4 or the nearest later release, to fix CVE-2025-59037. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@duckdb/node-api (npm) fixed in 1.3.4-alpha.27
npmnpm install "@duckdb/node-api@1.3.4-alpha.27"pnpmpnpm add "@duckdb/node-api@1.3.4-alpha.27"yarnyarn add "@duckdb/node-api@1.3.4-alpha.27"bunbun add "@duckdb/node-api@1.3.4-alpha.27"Check what is installednpm ls @duckdb/node-apiPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @duckdb/node-api to 1.3.4-alpha.27 or the nearest later release, to fix CVE-2025-59037. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@duckdb/node-bindings (npm) fixed in 1.3.4-alpha.27
npmnpm install "@duckdb/node-bindings@1.3.4-alpha.27"pnpmpnpm add "@duckdb/node-bindings@1.3.4-alpha.27"yarnyarn add "@duckdb/node-bindings@1.3.4-alpha.27"bunbun add "@duckdb/node-bindings@1.3.4-alpha.27"Check what is installednpm ls @duckdb/node-bindingsPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @duckdb/node-bindings to 1.3.4-alpha.27 or the nearest later release, to fix CVE-2025-59037. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.@duckdb/duckdb-wasm (npm) fixed in 1.30.0
npmnpm install "@duckdb/duckdb-wasm@1.30.0"pnpmpnpm add "@duckdb/duckdb-wasm@1.30.0"yarnyarn add "@duckdb/duckdb-wasm@1.30.0"bunbun add "@duckdb/duckdb-wasm@1.30.0"Check what is installednpm ls @duckdb/duckdb-wasmPaste into Cursor, Lovable or Claude CodeUpgrade the npm dependency @duckdb/duckdb-wasm to 1.30.0 or the nearest later release, to fix CVE-2025-59037. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".