440 hack event(s)
Description of the event: MORE Markets, a lending protocol deployed on Flow EVM, was exploited due to a bug in its lending contract liquidation logic. An attacker used flash loans to open and self-liquidate positions in the ankrFLOW/WFLOW market. A flaw cleared the collateral without clearing the corresponding WFLOW debt, allowing withdrawals from the WFLOW reserve. Losses were approximately $308,000; the protocol has been paused, with impact limited to users who supplied WFLOW to that market.
Amount of loss: $ 308000 Attack method: Smart Contract Vulnerability
Description of the event: On November 14–15, 2026, Bitcoin mining services provider Luxor experienced an unauthorized redirect of hashrate through its Commander fleet-management software. Attackers temporarily pointed machines from just over a dozen client accounts to another pool (e.g., OCEAN). The incident was limited in scope, with no data leaked. Luxor patched Commander within about two hours, restored settings, and pledged full compensation to affected clients for the redirected hashrate. The CEO described it as involving a sophisticated AI-enabled vector. Other Luxor services (Pool, LuxOS) were unaffected.
Amount of loss: $ 10,500 Attack method: Software Vulnerability
Description of the event: On November 14, 2026, HARD Lend, a decentralized lending application on Kava Chain, was exploited. The attacker used a lending-accounting vulnerability to inflate the value of BUSD collateral in a dormant market by roughly 243,000 times, then repeatedly borrowed and liquidated positions to drain approximately 53.9 million KAVA from the lending pool. The incident was confined to HARD Lend; Kava Chain’s underlying security was not compromised and no new tokens were minted. The exploit has been blocked, some funds frozen, and the team is accelerating the permanent shutdown of lending functionality.
Amount of loss: $ 3,760,000 Attack method: Smart Contract Vulnerability
Description of the event: On November 14, 2026, HyprEarn disclosed reports of unauthorized trading activity on a small number of Hyperliquid accounts that had previously authorized its API agent wallets. The team revoked all old agents on their side and instructed users to remove the approvals and re-enable trading with new ones. Agent wallets can only place trades and cannot withdraw or transfer funds. The root cause, number of affected accounts, and any financial losses remain undisclosed.
Amount of loss: - Attack method: Unknown
Description of the event: On November 12, 2026, Edel Finance announced that approximately $300,000 worth of $EDEL tokens were stolen and sold on the market. The team is working with authorities and exchanges to investigate and block the funds, with some tokens successfully blocked by exchanges. A more detailed post-mortem is forthcoming.
Amount of loss: $ 300,000 Attack method: Unknown
Description of the event: On the evening of November 10, 2026, an attacker exploited a flaw in the skew calculations of Rujira's Custom Concentrated Liquidity (CCL) strategy, manipulating trading activity in the BTC/USDC orderbook and imbalancing existing liquidity positions, resulting in approximately $200,000 in losses. Rujira halted the CosmWasm application layer and plans to remove the vulnerable skew parameter and fully reimburse affected users before resuming operations.
Amount of loss: $ 200,000 Attack method: Smart Contract Vulnerability
Description of the event: DeFi yield aggregator ACryptoS suffered a vault exploit due to a missing input validation check in the depositMulti function (array length not verified against token count). Attackers could deposit a tiny single-token amount to mint the vast majority of vault shares and withdraw a proportional share of both tokens. The attack hit 77 vaults across 5 chains (Arbitrum, BSC, Polygon, Base, Optimism), with total losses of approximately $665,000. Deposits have been disabled while withdrawals remain open; the project offered a 10% whitehat bounty for fund return and announced it is being deprecated due to lack of resources, urging users to withdraw ASAP.
Amount of loss: $ 665,429 Attack method: Smart Contract Vulnerability
Description of the event: BTCPay Server reported that hot wallets on multiple instances are being swept by unauthorized attackers. The project urgently advised all operators to shut down their instances immediately using ./btcpay-down.sh until the investigation is complete.
Amount of loss: $ 1,628,450 Attack method: Unauthorized Signing Access
Description of the event: On November 4, 2026, Crédit Mutuel Arkéa issued a statement confirming that the attacker gained access through the platform of an unnamed third-party service provider, then used the bank's own accounts to transfer funds to other financial institutions. The funds may have subsequently been converted into cryptocurrency through specialized platforms. The bank denied that the breach originated from its online banking subsidiary, Fortuneo, and stated that customer assets were not affected. Regarding the approximately $133 million in losses previously reported by ZachXBT, the bank did not confirm the exact figure but acknowledged the scale of the incident. Some funds have been frozen, while the final losses remain under assessment.
Amount of loss: $ 133000000 Attack method: Supply Chain Attack
Description of the event: On November 1, 2026, an attacker exploited a related actual-receipt verification failure in the fee processing of Sovryn’s XUSD/WRBTC AMM pool on Rootstock, receiving approximately 541,456 XUSD ($538,749). The protocol later implemented emergency fee controls, delisted the pool, and began reconciling LP losses.
Amount of loss: $ 538,749 Attack method: Smart Contract Vulnerability
Description of the event: The AI trading platform VergeX was attacked. Some users received withdrawal verification emails triggered by the attack. The official confirmed a total of 3,688.58 USDC was affected; risk controls triggered within one minute, all affected funds have been returned, and other users’ funds were unaffected. Services are being restored in stages.
Amount of loss: $ 3,688.58 Attack method: Unknown
Description of the event: On October 31, 2026, the Bitcoin dual-staking protocol b14g suffered a security incident in which approximately 97 million CORE tokens staked through the protocol were withdrawn without authorization and transferred to attacker-controlled addresses. The team paused the affected contracts and is coordinating with the Core team, security partners, and exchanges to trace, freeze, and recover the funds. BTC staked via the protocol remained time-locked on Bitcoin and was unaffected.
Amount of loss: $ 1,470,000 Attack method: Smart Contract Vulnerability
Description of the event: On October 31, 2026, attackers exploited a failure to verify actual token receipt in Sovryn’s lending and margin contracts on Rootstock. Through three transactions, they extracted a net outflow of approximately $914,000 in XUSD and WRBTC. The Perimeter 24-hour withdrawal delay successfully blocked an additional ~$66,134 XUSD.
Amount of loss: $ 914,000 Attack method: Smart Contract Vulnerability
Description of the event: Chainstack, a blockchain node and RPC infrastructure provider, was breached by an external attacker. The attacker entered via an exposed Grafana instance in a development environment (default admin credentials unchanged, no additional protection), leveraged an unauthenticated MCP tool server and other means to escalate privileges, reached parts of the production environment, and accessed a customer account database (including password hashes) as well as systems holding node credentials. The company detected and cut off access, urging customers to change passwords, rotate credentials, and regenerate API keys. Customer-facing services remained unaffected. The incident is linked to a broader AI-powered attack campaign using the ARTEX framework.
Amount of loss: 0 Attack method: Infrastructure Compromise
Description of the event: The Affluent DeFi protocol on the TON chain experienced an unbacked minting incident classified under token and share accounting, resulting in a loss of approximately $1,053,000 due to a smart contract vulnerability.
Amount of loss: $ 1,053,000 Attack method: Smart Contract Vulnerability
Description of the event: UNCX Network’s Smart Token Vesting V2 contracts were exploited across multiple chains (Ethereum, BNB Chain, Base, and Robinhood Chain). Attackers used a sequence of public vesting actions (release and cancel) that created discrepancies between pooled token balances and recorded shares, allowing attacker-controlled positions to withdraw more assets than entitled. Approximately 10 tokens and 11 transactions were involved. Early estimates put losses at about $1.49M; the project later confirmed roughly $807K–$808K in realized extracted value, with about $58K recovered by whitehats.
Amount of loss: $ 807,000 Attack method: Smart Contract Vulnerability
Description of the event: Crypto gambling platform Gamdom was attacked on October 13, 2026, due to an unauthorized server connection, resulting in approximately $4.2 million stolen from hot wallets. The incident affected multiple blockchains; the platform went offline for investigation and moved remaining hot wallet funds to cold storage.
Amount of loss: $ 4,208,000 Attack method: Hot Wallet Server Compromise
Description of the event: Papertrade, a synthetic perpetuals platform with up to 1000x leverage built on Hyperliquid’s HyperEVM, suffered a ~$1.28 million loss about 8 hours after its Oct. 10, 2026 launch. A wallet moved ETH prices on Hyperliquid (via large buys/sells) while holding highly leveraged positions on Papertrade that settled against the manipulated BBO midpoint, extracting profits from the platform’s shared USDC liquidity pool. Papertrade attributed it to overly permissive open-interest limits at launch and tightened them.
Amount of loss: $ 1,280,000 Attack method: Price Manipulation
Description of the event: Web3 financial platform Based discovered that an unauthorized third party had accessed an internal dashboard used to manage the Based Visa Card program and contained the incident shortly after detection. KYC data collected by the card issuer for some cardholders (including name, ID/passport number, date of birth, and address) may have been obtained. Card numbers, CVV, PIN, ID photos, liveness records, the Based Wallet, and card funds were not affected, and cards continue to work normally. Affected users were notified by email, authorities were informed, and users were warned about phishing and social-engineering risks.
Amount of loss: 0 Attack method: Unauthorized Access to Internal Systems
Description of the event: Microsoft’s official X account was accessed without authorization for about 30 minutes. Attackers changed the profile picture to Clippy, followed and reposted an impersonator account, and promoted an unauthorized Clippy meme coin to roughly 13 million followers; a later “apology” post was also unauthorized and deleted. Microsoft told The Verge and others that the account was secured, the posts removed, and that it never authorized any token tied to Clippy or $MSFT.
Amount of loss: 0 Attack method: The X account was hacked