Morning Edition · Monday, September 28, 2026Published at 1:43 AM EDT · New York
A forged Circle transfer message, an unprotected registry reinitialization and a privileged burn paired with a premature pool sync push the tracked incident count to 871.

The DeFiHackLabs repository added three reproductions overnight and updated its incident count from 870 to 871. All three have one thing in common. None required breaking a cryptographic primitive. The Allbridge case reproduces a phantom de…
Track on-chain flows, protocol shifts, stablecoins, and regulation.
The Global Intelligence Brief stays free.
Part of a tracked trend
Losses Move to Components That Worked as Designed
A growing share of DeFi losses will come not from buggy contract code but from components behaving exactly as specified — oracle forwarders, validator signature sets, governance votes and other trusted off-contract inputs — so audits and bug bounties scoped to on-chain code keep missing the failure surface, and protocols will be repeatedly forced to extend review, scope and monitoring to their privileged operational infrastructure.
Start a discussion in Townsquare.
More from this edition
Comments
0No comments yet.