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.
The Bitcoin payment software's update also closes a remote-command restriction bypass, prompting maintainers to urge a separate review of access credentials.
The correction separates token-destruction permissions from issuance, while also bringing accounting fixes for planned lending and pooled-asset features.
No users lost funds and dotUSD remained backed by USDT, but the breach exposed gaps in patch deployment and emergency response across Polkadot.
Equal reserves restore the backing ratio, but they do not restart Federation withdrawals or guarantee that SideSwap can pay every conversion immediately.
Blockstream supplied the final 550 BTC needed to close the reserve gap, while the Federation says governance and security changes are still in preparation.
Patching alone may leave stolen credentials and wallet secrets exposed, so BTCPay recommends fresh servers, new wallets and rotated access keys.
The flaw raises a trust and security concern for stablecoin issuance on the ledger, while the planned fix makes remediation the key next step.
The April fix blocks new malformed announcements, but upgrading alone does not remove a trigger already saved on disk, leaving operators with manual cleanup to do.
The change restores separation between token-destruction and issuance permissions, while XRP’s own supply remains unaffected.
Ubuntu's patch is still pending, leaving some operators reliant on temporary mitigations while the demonstrated exploit can reach root access without credentials.
The tests show emailed approval codes can fail as a human safeguard when an agent can access the same inbox, putting the security of autonomous payments under scrutiny.
The attacker used zero-value withdrawal requests, while exchange partners froze about 9M CORE and roughly 68M remained unmoved as of Oct. 31.
The pause disrupted cross-chain swaps for all users, while also delaying the movement of funds stolen from Binance.
The malicious delegation can sweep ETH and ERC-20 tokens, and the contract may also put assets sent to the wallet later at risk.
The attack remains theoretical, but exposed public keys and years-long upgrade timelines make Bitcoin's preparation window a central concern.
Default Teku mainnet nodes were not affected, and no exploitation has been reported, but some validator setups need software or Java updates.
The fix targets parser disagreements that could disconnect payment execution from withdrawal accounting, while lnd’s broader payment-secret checks remain under review.
The fix keeps validator deposits separate from builder funds, but client integration and a new Hoodi test date still stand between Glamsterdam and mainnet.
The real loss is about $3 million paid from reserves, but roughly $7 million in unauthorized balances means the bridge is insolvent on paper until Initia restores backing it has not yet explained.
Support has recovered to 31 of 35 validators, above the 29-vote threshold, but the patch must complete a fresh 14-day approval countdown.
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
CoinDesk
TheBlock
WatcherGuru
WuBlockchain