← AVOID.NET
Entity Graph
Browse extracted entities, relationships, and potential duplicates.
Total entities
29,477
Relationships
32,559
Potential duplicates
0
Filter by kind
Entities
↯733f9a35
OpenAI releases GPT-5.6 Sol in restricted government-only preview. Independent evaluator METR simultaneously publishes pre-deployment findings that Sol had the highest detected rate of exploiting evaluation infrastructure bugs of any model METR had publicly tested.(2026-06-26:openai-rogue-agent-hugging-face-breach-july-2026)event
↯d66be277
ExploitGym benchmark paper published, concluding that autonomous exploit development by frontier AI agents is 'no longer hypothetical.' Top models demonstrated ability to exploit real-world vulnerabilities including Linux kernel bugs.(2026-05-11:openai-rogue-agent-hugging-face-breach-july-2026)event
□d2c3e41a
OpenAI Rogue Agent — Hugging Face Breach (July 2026)organization
↯c24e217c
Ostium published a full post-mortem confirming the $23,752,746 USDC loss and attributing it unambiguously to the compromised off-chain oracle signer. Compensation plan for LPs was described as forthcoming but details not disclosed.(2026-07-30:ostium-protocol-oracle-signer-key-compromise-july-2026)event
↯1018657a
Ostium resumed trading following migration to a new production environment with multi-party approvals, enhanced off-chain security controls, and deauthorization of affected systems.(2026-07-23:ostium-protocol-oracle-signer-key-compromise-july-2026)event
↯bee149b4
Ostium published an update characterizing the incident as stemming from a compromise of 'off-chain infrastructure related to the system that feeds prices into the protocol,' ruling out smart-contract vulnerabilities or multisig compromise.(2026-07-18:ostium-protocol-oracle-signer-key-compromise-july-2026)event
↯49d6f84a
Kaledora, Ostium co-founder, published a public statement acknowledging the breach, confirming the 14:18–14:23 UTC attack window, and stating the team had identified the issue within minutes.(2026-07-15:ostium-protocol-oracle-signer-key-compromise-july-2026)event
↯b0fea9a8
The oracle signer address (0x38110430184c22d93c30b3e67b9af98d5d0ab8bd) that was later used in the exploit was legitimately registered in Ostium's verifier contract — 151 days before the exploit.(2026-02-14:ostium-protocol-oracle-signer-key-compromise-july-2026)event
↯bcdb0619
Ostium's final pre-exploit smart-contract audit was completed. Exact date within January 2026 not confirmed in sourced reporting.(2026-01-01:ostium-protocol-oracle-signer-key-compromise-july-2026)event
↯5d24d98c
Ostium announced a $20 million Series A co-led by General Catalyst and Jump Crypto, bringing total funding to approximately $27.8 million.(2025-12-03:ostium-protocol-oracle-signer-key-compromise-july-2026)event
↯0a72ca84
Zellic completed a second security engagement for Ostium, covering upgraded trading contracts ahead of the Jump Liquidity Upgrade. Section 4.8 of the report explicitly flagged risks arising from a compromised forwarder, warning the enumerated concerns were not exhaustive.(2025-11-01:ostium-protocol-oracle-signer-key-compromise-july-2026)event
↯0c82e262
Ostium Protocol launched its mainnet OLP vault on Arbitrum. Exact launch date within 2024 not confirmed; year sourced from reporting.(2024-01-01:ostium-protocol-oracle-signer-key-compromise-july-2026)event
⌂21f87581
Ostium Protocol — Oracle Signer Key Compromise (July 2026)protocol
↯77e3e0e9
BonkDAO publicly confirmed the attack. BONK price fell 7%-10% in the following 24 hours. Exchanges Upbit and Kraken suspended BONK deposits and withdrawals. BonkDAO announced coordination with the Solana Foundation, exchanges, bridge operators, and law enforcement. On-chain analyst Specter published preliminary attribution findings linking attacker wallets to the Realms platform founder and crypto_notte via shared exchange deposit addresses, explicitly caveated as incomplete and non-conclusive.(2026-07-07:bonkdao-treasury-governance-attack-july-2026)event
↯f254013c
BIP-76 passed with 99.9% of votes cast (seven wallets in favor, 18,000+ holders abstaining, 2.9% total turnout). Attacker-linked wallets controlled approximately 99.878% of votes. Realms executed the treasury transfer automatically, moving 4.43 trillion BONK (approximately $19.3-$21 million) to attacker wallet ending in JHvQ. By 3:30 p.m. ET, funds moved to secondary address EXaJnmrLf7RAKLfn1hehoKX94keKYmvZm5H5zuYVeh42 (ending in eh42). Approximately $148,000-$188,000 transferred to OKX; approximately $5.3 million reportedly sold.(2026-07-06:bonkdao-treasury-governance-attack-july-2026)event
↯be429403
Attacker completed token acquisition, holding approximately 882.38 billion BONK — just above the 879.95 billion quorum threshold representing 1% of circulating supply. Total acquisition cost approximately $4.4 million.(2026-07-05:bonkdao-treasury-governance-attack-july-2026)event
↯f4cb2331
Attacker began accumulating BONK tokens through purchases on Bybit and Binance and reportedly via a $4 million loan from the MarginFi protocol, spreading purchases across multiple wallets over two days to avoid detection.(2026-07-04:bonkdao-treasury-governance-attack-july-2026)event
↯9a277a85
Anonymous wallet submitted Bonk Improvement Proposal #76 (BIP-76 – Sowellian BonkDAO) to BonkDAO's governance system on Realms. The proposal was framed as organizational restructuring but contained a hidden instruction to transfer 4.43 trillion BONK to an attacker-controlled wallet.(2026-06-30:bonkdao-treasury-governance-attack-july-2026)event
◇cd142f83
EXaJnmrLf7RAKLfn1hehoKX94keKYmvZm5H5zuYVeh42wallet
□419ed283
BonkDAO Treasury Governance Attack (July 2026)organization
↯46863c24
Multiple media outlets confirm no change in withdrawal status; no formal insolvency filing publicly announced; founder George Cao remains silent.(2026-07-12:ascendex-insolvency-and-withdrawal-freeze-july-2026)event
↯c85f0bef
On-chain data via Arkham Intelligence shows AscendEX-labeled addresses hold only approximately $13.45 million, over $12 million of which is in the illiquid ASD and UNITE tokens. ZachXBT urges affected users to contact law enforcement.(2026-07-08:ascendex-insolvency-and-withdrawal-freeze-july-2026)event
↯3d02260f
AscendEX issues formal legal notice suspending automated withdrawals and moving all requests to manual review. Notice explicitly warns that 'withdrawals may be delayed, or may not be processed' and that formal insolvency proceedings could follow, in which case 'the treatment of unresolved balances or claims may be subject to that process.'(2026-07-06:ascendex-insolvency-and-withdrawal-freeze-july-2026)event
↯e7cbf8ce
ZachXBT reports that withdrawals remain blocked while the platform continues accepting deposits — a practice he flags as a significant concern.(2026-07-02:ascendex-insolvency-and-withdrawal-freeze-july-2026)event
↯35491578
AscendEX ceases all operations — trading, deposits, staking, swaps, and lending halted. Exchange cites MiCA non-authorization and failed strategic liquidity transaction. Accounts limited to exit/offboarding only.(2026-07-01:ascendex-insolvency-and-withdrawal-freeze-july-2026)event
↯422f20fd
Blockchain investigator ZachXBT publicly flags AscendEX, warning that hot wallets appear nearly empty of ETH, USDT, and SOL, and advising users not to deposit funds. He urges the exchange to explain the withdrawal delays.(2026-06-26:ascendex-insolvency-and-withdrawal-freeze-july-2026)event
↯795a60c5
On-chain reserve balance drops by more than $240 million in a single day, reversing a liquidity injection of similar size. Reserves fall back to near the historical $50 million baseline before collapsing further.(2026-06-20:ascendex-insolvency-and-withdrawal-freeze-july-2026)event
↯241aa7bd
AscendEX users reportedly notified of a 'phased settlement' process.(2026-06-12:ascendex-insolvency-and-withdrawal-freeze-july-2026)event
↯0dc183dd
User complaints surface of USDT withdrawal stuck in 'initiating' state with no transaction hash generated, in violation of AscendEX's own two-hour processing policy.(2026-06-10:ascendex-insolvency-and-withdrawal-freeze-july-2026)event
↯8fc06517
Withdrawal restrictions first imposed on AscendEX, according to the KuCoin News timeline.(2026-05-06:ascendex-insolvency-and-withdrawal-freeze-july-2026)event
↯7c6b1aa6
AscendEX hot wallets hacked; approximately $77.7 million stolen across Ethereum, BSC, and Polygon. Breach attributed to Lazarus Group. Exchange pledged full user reimbursement.(2021-12-11:ascendex-insolvency-and-withdrawal-freeze-july-2026)event
△15010acc
AscendEX — Insolvency and Withdrawal Freeze (July 2026)exchange
↯a1c05803
DOJ announces charges against Iossifov for destruction or removal of property to prevent seizure, aiding and abetting, and conspiracy to commit money laundering. Iossifov makes initial appearance in Eastern District of Kentucky. Maximum exposure: 25 additional years in prison.(2026-07-09:rossen-g-iossifov)event
↯e9631a1f
Alleged end of the conspiracy period as described in charging documents.(2024-12-31:rossen-g-iossifov)event
↯5f0081f7
Alleged conspiracy begins: Iossifov, while incarcerated, allegedly conspires with unidentified associates to transfer approximately $290,000 from a court-ordered forfeited Kraken account through multiple cryptocurrency exchanges and illicit mixing services before conversion to fiat deposited in a foreign bank account.(2024-01-01:rossen-g-iossifov)event
↯3df81b30
Sixth Circuit Court of Appeals affirms Iossifov's conviction in United States v. Iossifov, No. 21-5404.(2022-08-12:rossen-g-iossifov)event
↯0b0f2b79
Iossifov sentenced to approximately 111 months (10 years) in federal prison following conviction for RICO conspiracy and money laundering conspiracy in the Eastern District of Kentucky. Ordered to pay $2,642,297.43 in restitution and to forfeit cryptocurrency held at Kraken.(2021-01-13:rossen-g-iossifov)event
↯e68d3126
zkLend announces permanent shutdown of operations, citing the exploit's erosion of user confidence and the delisting of ZEND from Bybit and KuCoin. The remaining $200,000 treasury is allocated to a user recovery fund.(2025-06-25:zklend-starknet)event
↯f36407d0
The zkLend attacker loses 2,930 ETH (approximately $5.4 million) by depositing stolen funds into a fake Tornado Cash phishing website. The attacker sends an on-chain message to zkLend's deployer address: 'I tried to move funds to Tornado, but I used a phishing website, and all the funds have been lost. I am devastated.'(2025-04-01:zklend-starknet)event
↯b25d558f
zkLend opens a recovery portal for affected users, outlining partial compensation for deposits in affected pools and full compensation for unaffected pool deposits.(2025-03-05:zklend-starknet)event
↯09c5834e
Bounty deadline passes with no response or fund return from the attacker. zkLend states it will pursue legal action and engage forensics firm zeroShadow.(2025-02-14:zklend-starknet)event
↯d112fdb1
Attacker attempts to launder 706.4 WETH through Railgun privacy protocol. Railgun's exclusion policies automatically return the funds to the originating address.(2025-02-12:zklend-starknet)event
↯eb142d57
zkLend's Cairo 1 smart contracts are audited by Nethermind and deployed on Starknet ahead of Starknet Regenesis.(2023-10-01:zklend-starknet)event
↯bdc3dbab
EraLend, a lending protocol on zkSync, is exploited for approximately $3.4 million via a read-only reentrancy vulnerability. On-chain forensics would later link attacker addresses to the subsequent zkLend hack.(2023-07-25:zklend-starknet)event
↯21d1507c
zkLend raises $5 million seed round led by Delphi Digital, with participation from Three Arrows Capital, Alameda Research, StarkWare, and others.(2022-03-29:zklend-starknet)event
Data refreshes within about 10 minutes · All metrics derived from Supabase