XRP Ledger Fix Delayed to Nov. 4 After Validator Support Dips
Support has recovered to 31 of 35 validators, above the 29-vote threshold, but the patch must complete a fresh 14-day approval countdown.
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.
Support has recovered to 31 of 35 validators, above the 29-vote threshold, but the patch must complete a fresh 14-day approval countdown.
Confirmed attacks after an early leak put unpatched websites at risk, making prompt patching and caution around unfamiliar sites especially important.
SEC Question 77 was already probing whether AI agents should be permitted to sign crypto transactions; the OpenAI disclosure handed regulators a concrete case study on autonomous authorization drift.
The appointment links NEAR's private onchain markets push with a Solana infrastructure executive, as NEAR Intents faces scrutiny after a $3.8M exploit.
The selloff is widening across equities and crypto as leverage unwinds, with $813M liquidated and traders hedging Bitcoin downside ahead of U.S. CPI.
Developers skipped the usual two-week governance vote to kill a flaw that could have let attackers mint unlimited spendable XRP, trading process for speed.
Version 3.4.1 gives the ecosystem a clear reference point for the fix while XRP's supply rules remain unchanged.
The episode exposes the risk of pairing 1,000x leverage with an external price feed and a shared pool that takes the other side of trades.
The flaw had existed since 2015, but exploiting it required hundreds of contrived offers and a transaction designed to consume them all at once.
The fix covers two theft paths, including a reconnect attack that could make a forwarding node pay a recipient without recovering the incoming funds.
The claims expose a potential oracle-design weakness: short-term changes in Hyperliquid quotes could affect executions on Papertrade.
No XRP was created or lost, but the incident exposed a decade-old weakness in XRPL's supply controls and forced developers to bypass normal validator approval.
The flaw could have bypassed the ledger’s fixed-supply safeguards, but RippleX found no evidence of exploitation and shipped a patch in xrpld 3.4.1.
The drain hinged on 79AU token permissions, showing that locking LP receipts does not revoke a privileged address's ability to move tokens from a pool.
The warning challenges the assumption that quantum computers will be the first technology to threaten elliptic-curve cryptography, but no practical attack has been demonstrated.
The framework arrives as a Base vault incident highlights risks beyond the underlying lending protocol, including vault security, curator decisions and withdrawal liquidity.
Agent-driven blockchain use could reduce reliance on traditional frontends, but shifts security risks toward prompt injection and whether AI understands each onchain action.
Existing Stylus apps and Solidity contracts remain operational, but developers cannot make newly activated Stylus code executable until the restriction is lifted.
Aave v3’s core contracts were unaffected, but the attack exposed how a third-party integration can put collateral in users’ wallets at risk.
Q3's $6.34B in spot Bitcoin ETF inflows alongside a 43% price gain is a structural demand story, not a sentiment spike, and the Fear & Greed reading of 72 still leaves room before this looks crowded.
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.