CVE-2025-59037
Published: 09 September 2025
Summary
CVE-2025-59037 is a high-severity Embedded Malicious Code (CWE-506) vulnerability in Aikido (inferred from references). Its CVSS base score is 8.6 (High).
Operationally, ranked at the 26.6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-33981
Vulnerability details
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…
more
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.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Restricting software to licensed versions and controlling P2P prevents introduction of software containing embedded malicious code from unauthorized sources.
The control prevents users from installing software that contains embedded malicious code.
Regular inventory reviews and updates make it harder to conceal or exploit embedded malicious code by requiring all components to be documented and accounted for.
Reverting to a known state removes any malicious code embedded by an attacker.
The approval and review process for maintenance tools can prevent introduction or continued use of tools containing embedded malicious code.
Supply chain strategy requires vetting and controls during acquisition to prevent or detect insertion of malicious code by vendors or integrators.
Background screening for development or deployment roles makes intentional insertion of malicious code by insiders materially harder to accomplish.
The capability explicitly searches for embedded malicious code and backdoors as indicators of compromise.