A reentrancy attack is an exploit against a smart contract in which an attacker's contract calls back into the victim while the victim's first call is still running. The typical flaw is a withdrawal function that sends funds before reducing the caller's recorded balance. When the payment arrives, the attacking contract runs code that calls the withdrawal function again, and again, each time passing the balance check because the record has not yet changed.
The best-known case is The DAO in June 2016, when an attacker used reentrancy to move about 3.6 million ether. The response, a hard fork that returned the funds, split the network and left the original chain as Ethereum Classic. Standard defences are the checks-effects-interactions pattern, which updates state before any external call, and reentrancy guards that lock a function while it runs. Variants that re-enter through a different function or contract remain a common finding in a smart contract audit.
Ref 1070001401