Skip to main content

What Is the Risk of a Malleability Attack on an Exchange?

Before SegWit, an exchange could face issues if a withdrawal transaction was sent, and then a malleability attack changed its TXID before confirmation. The exchange's software, expecting the original TXID, might fail to track the payment, potentially leading to a second withdrawal (double-spend) if not properly handled.

In What Scenario Might an Attacker Try to Manipulate the Raw Transaction Data?
How Does the Concept of “Transaction Malleability” Relate to UTXOs and Transaction IDs?
What Is a “Witness” in the Context of SegWit Transactions?
What Layer 2 Solution Eliminates the Need for a Long Withdrawal Period?