What’s Vulnerable › Vulnerabilities

CVE-2025-59037: DuckDB NPM packages 1.3.3 and 1.29.2 briefly compromised with malware

• Severity: high (CVSS 8.6 v4.0)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.4% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2025-09-09 · updated 2026-06-17
• Weakness: CWE-506

Description

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.

Affected products

• duckdb-node: = 1.3.3, = 1.29.2

References

• https://github.com/duckdb/duckdb-node/releases/tag/v1.3.4
• https://github.com/duckdb/duckdb-node/security/advisories/GHSA-w62p-hx95-gf2c
• https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised

Get alerted when CVE-2025-59037 or the next vulnerability affects your stack