Exploits covers the technical failures and adversarial transactions that put smart contracts, DeFi markets, bridges, wallets and onchain governance systems at risk. The beat includes reentrancy, oracle manipulation, flash-loan-assisted attacks, signature and verification flaws, access-control failures and malicious governance proposals. These incidents matter beyond the protocol directly affected: a compromised price feed can trigger bad debt, a bridge flaw can threaten assets across networks, and a treasury raid can expose weaknesses in voting participation, quorum rules or execution delays. For holders of ETH, USDC, BTC, ADA and ecosystem tokens such as BONK and HBAR, the key questions are not only how much was taken, but which assumptions failed and whether connected markets remain exposed.
Zipp follows exploit reports from the first suspicious transaction through containment, post-mortems and recovery efforts. Day-to-day coverage examines transaction traces, attacker funding, oracle inputs, contract permissions, governance votes, validator or sequencer responses, bridge withdrawal guidance and changes to protocol operations. Recent reporting themes include low-turnout treasury attacks against DAOs, flash-loan exploits in lending systems, oracle and signature failures on Arbitrum and Hedera, verification problems affecting Taiko infrastructure, wallet compromises in the Cardano ecosystem and severe dislocations in Morpho-linked markets. We also track whether teams pause contracts or block production, move assets into security infrastructure such as Chainlink CCIP, negotiate with attackers, compensate users or leave unresolved liabilities. The aim is to separate the exploit mechanism from its market impact and show readers what evidence confirms a loss, what remains uncertain and which follow-on risks deserve attention.
Developers say the flaw was patched before any known exploit, but the market selloff lays bare how quickly trust collapses around a privacy coin when the integrity of its hidden supply is questioned.
Second major breach in three years, after the $100M Horizon bridge heist linked to North Korean hackers. The bigger question is whether a rollback restores trust or deepens the credibility hit.
A rollback on a major L1 would test whether on-chain accountability trumps immutability and could set a precedent for similar bridge and minting exploits.
XRP has the densest leverage pile of any major coin sitting on top of a fragile $1 support, into a binary CPI day where even bitcoin's options are pricing barely a 1.3% post-print swing.
About 26% of ONE's circulating supply minted from thin air is the structural blow; the rest of the market is coiled ahead of July U.S. CPI at 12:30 UTC that could reset the risk-asset tone.
The 4B figure is ~27x larger than Harmony's 2023 staking bug and lands on the base layer rather than a bridge, with the rollback trade-off now the structural question for the next base-layer…
The episode turns a planned L2 shutdown into a test of bridge reliability and user exit procedures across DeFi.
BIP-110's trigger fires this weekend; its replay protection waits until September. The dangerous case is a minority chain that refuses to die, because miner signalling sits at just 2.6%.
Polymarket's fix mirrors Kalshi's: time-weighted averages via Chainlink make last-second Binance pushes costly. Stanford-SMU paper found 93% of losses in manipulated windows fell on retail.
A full chain freeze routed to a support inbox, not an on-chain recovery path, is the kind of operational failure that tests whether decentralisation still means anything when a single team can stop…
The seed-randomness flaw had lurked in firmware since March 2021 and went unnoticed for years, exposing the practical ceiling of single-device self-custody for serious BTC holders.
Galaxy mapped the July 30 sweep to 1,196 wallets and 1,082 BTC drained in 41 minutes via a seed-generation bug that collapsed the keyspace to a few billion options.
Nearly 1,200 addresses and 1,000 BTC later, the incident has crossed from isolated phishing to a coordinated drain, putting self-custody users on notice about supply-chain risk in hardware wallets.
Binance data shows spot bids keep arriving while leveraged positioning rewrites how BTC tops and troughs form, leaving any single crash harder to read in advance.
Nearly 600 BTC were stolen from a flaw in Coldcard's firmware that let attackers reconstruct wallet seeds, reopening the case that institutional products like BlackRock's IBIT now make more sense for…
The protocol fix is live and verifiable, but ZEC still trades below the $500 area Ironwood was supposed to put back on the map, leaving the supply repair in technical hands and the price repair in…
DPRK alone siphoned nearly $600M. The headline number is bad, but the forward-looking warning on AI-driven exploits is the piece security teams and on-chain risk teams should be reading.
A formally verified pool that reuses a patched circuit is the bridge, not the destination: Zcash's ecosystem is rebuilding trust after the Orchard disclosure wiped out more than half of ZEC's price.
A 27% wick on a HIP-3-listed Korean stock perp exposed the liquidity fragility of permissionless listing: any staker can launch a market, but depth on entry is anything but guaranteed.
The 5,280 ETH is already in motion, but the lasting damage from a wallet exploit is rarely the theft itself, with secondary fallout that can stretch for months after the coins leave.
A smart contract exploit is the use of a coding flaw, faulty assumption or unsafe permission to produce an outcome the protocol did not intend. Not every exploit requires hacked private keys; some attackers interact with deployed contracts exactly as their code permits.
An attacker distorts or exploits the price data a protocol uses for lending, trading or collateral checks. If the protocol relies on a thin market, a single source or a poorly configured update mechanism, the false price can enable excessive borrowing, unfair liquidations or asset withdrawals.
Flash loans provide large amounts of temporary capital that must be borrowed and repaid within one transaction. They are legitimate tools, but attackers can use them to amplify oracle manipulation, governance power or accounting flaws without committing substantial capital beforehand.
Check the affected protocol’s official notices, relevant contract addresses and transaction records on a block explorer. Confirm whether independent security researchers identify the same mechanism, and distinguish the attacker’s gross transfers from the protocol’s final net loss.
CryptoSlate
TheBlock
CoinTelegraph
CoinDesk