CVE-2025-59037Known exploitationPublic exploitNetwork attack vector

Cryptocurrency transaction redirection via malicious browser hooks

Published Sep 9, 2025 · Updated Sep 10, 2025

Embedded malicious code in DuckDB npm packages 1.3.3 and 1.29.2 allows attackers to redirect cryptocurrency transactions. The injected JavaScript hooks window.ethereum, fetch, and XHR, replacing wallet addresses in requests and responses with attacker-controlled lookalikes. Exploitation requires an application to load an affected dependency while a user initiates cryptocurrency or Web3 activity; the source record reports no downloads before removal.

CVSS severity8.6
High
EPSS probability0.37%
Next 30 days · Sep 16, 2026
Known exploitationReported
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Embedded malicious code in DuckDB npm packages 1.3.3 and 1.29.2 allows attackers to redirect cryptocurrency transactions. The injected JavaScript hooks window.ethereum, fetch, and XHR, replacing wallet addresses in requests and responses with attacker-controlled lookalikes. Exploitation requires an application to load an affected dependency while a user initiates cryptocurrency or Web3 activity; the source record reports no downloads before removal.

The record

CVE
CVE-2025-59037
Published
Sep 9, 2025
Updated
Sep 10, 2025
Vendor
DuckDB
Product
DuckDB Node Bindings
Classifications
CWE-506, T1195.002
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Sep 8, 2025Exploitation reportedMalicious npm releases published after maintainer-account phishing
  2. Sep 9, 2025CVE publishedPublication date reported by the CVE source.
  3. Sep 10, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion== 1.29.2
  2. Affected versionversion== 1.3.3

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

DuckDB · DuckDB Node Bindingsversion== 1.29.2; version== 1.3.3

Published CVSS scores

8.6GitLab Advisory DatabaseCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
8.8GitLab Advisory DatabaseCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationReported
Public exploitPublished

Weakness, pattern, technique

CWE-506Embedded Malicious Code
T1195.002Compromise Software Supply Chain

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Reported exploitation

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo