Vulnerability 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/[email protected]`, `@duckdb/[email protected]`, `[email protected]`, and `@duckdb/[email protected]` 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.
Related Weaknesses (CWE)
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
FAQ
What is CVE-2025-59037?
CVE-2025-59037 is a documented vulnerability. 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...
How severe is CVE-2025-59037?
CVSS scoring is not yet available for CVE-2025-59037. Check NVD for updates.
Is there a patch for CVE-2025-59037?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.