duckdb-node up to 1.3.3/1.29.2 malicious code

Summaryinfo

A vulnerability was found in duckdb-node up to 1.3.3/1.29.2 and classified as critical. This impacts an unknown function. The manipulation results in malicious code. This vulnerability is identified as CVE-2025-59037. The attack can be executed remotely. There is not any exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in duckdb-node up to 1.3.3/1.29.2. It has been classified as critical. Affected is an unknown code. The manipulation with an unknown input leads to a malicious code vulnerability. CWE is classifying the issue as CWE-506. The product contains code that appears to be malicious in nature. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at github.com. This vulnerability is traded as CVE-2025-59037 since 09/08/2025. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available.

Upgrading to version 1.3.4 or 1.30.0 eliminates this vulnerability.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Name

• duckdb-node

Version

• 1.3.0
• 1.3.1
• 1.3.2
• 1.3.3
• 1.29.0
• 1.29.1
• 1.29.2

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion