In crypto security, exploit threads move faster than facts: a bridge is “hacked for $X million” within minutes of the first abnormal transaction, often before anyone has traced where the funds actually went. This hub holds our checks on security incidents — exploits, bridge compromises, patch disclosures, bug-bounty claims — against the on-chain and published record.
A receipt is the transaction trace itself, a post-mortem published by the affected team, an auditor’s report, or a tracked vulnerability entry — something a reader can open and confirm independently. Early incident figures are frequently revised once a trace completes; where we cite a number, we link the record it came from rather than repeating a running total.
Not financial advice.
Nothing in this hub recommends a response to an incident or a security product. Full grading rules: methodology. Every published check: the verification index.
VerificationClaim class – unverifiedNovember 18, 2026
The claim class: a project points to its contract being verified on a block explorer, sometimes paired with a broader claim that the contract has been audited or is generally safe, as evidence that its code can be...
The FBI's Internet Crime Complaint Center reported $9.3 billion in losses across 149,686 complaints referencing cryptocurrency in 2024. The figure is in the report;...
Within days of the Bybit theft, the claim circulated that North Korea was responsible. The FBI's public service announcement I-022625-PSA says so, names the...
The claim class: a token team states that ownership of the contract has been renounced, implying no address retains owner-level privileges such as minting...
Most explorers let anyone check that a contract's published source code actually matches the bytecode running on-chain. This guide explains what the green Verified...
An audit badge gets quoted constantly; the actual report behind it is read far less often. This guide explains how to find the real...
Security: frequently asked questions
Does an audit mean a smart contract is safe?
No. An audit is a review of specific code at a specific time, within a stated scope. Read the report's scope, the commit it covers and which findings were fixed. Our guide to reading an audit report shows what to look for.
What does verified source code on a block explorer confirm?
It confirms that the published source compiles to the bytecode deployed at that address. It says nothing about whether the code is safe, and a proxy contract can point to different code later.
How can I check whether contract ownership was renounced?
Call the contract's owner function on a block explorer and check whether it returns the null address. Then look for proxies and other privileged roles, which renouncing ownership does not remove.
Who confirms who was behind a hack?
Attribution is a claim like any other. Look for official statements such as law-enforcement alerts or sanctions actions that name the actor, and treat unsourced attributions on social media as unconfirmed.