In 2025, DeFi protocols lost $3.4 billion to exploits. The Bybit hack alone accounted for $1.5 billion. Early 2026 isn't looking better — $86 million stolen in January, another $24 million in February. The attacks are getting more sophisticated, but most of them succeed because of preventable mistakes.
After auditing dozens of DeFi protocols, we've compiled the security checklist we wish every team used before deployment. This isn't theoretical — every item on this list maps to a real attack that cost real money. For the step-by-step audit process itself, see How to Audit a Smart Contract Before Launch.
$3.4B
Crypto Stolen in 2025
$1.5B
Bybit Hack Alone
19%
Of Hacked Protocols Used Multisig
2.4%
Used Cold Storage
Smart Contract Security
The code is the foundation. If your contracts are vulnerable, nothing else matters.
| Area | What to Check |
|---|---|
| Multiple Audits | Get at least two independent audits. Different auditors have different strengths and blind spots. |
| Static Analysis | Run Slither, Aderyn, and Mythril. Fix all findings or document why they're false positives. |
| Fuzz Testing | Use Echidna, Medusa, or Foundry fuzzing (see our free tools guide). Define critical invariants and let the fuzzer try to break them. |
| 100% Test Coverage | Unit tests, integration tests, and negative path tests. If a function isn't tested, assume it's broken. |
| Formal Verification | For critical math (token pricing, reward distribution, liquidation logic), use Certora or SMTChecker. See our Formal Verification practical guide. |
| OWASP SC Top 10 Review | Walk through every item in the OWASP Smart Contract Top 10 2026 against your codebase. |
| Re-Audit After Changes | Any code change after an audit — even a "minor" one — needs re-review. We've seen critical bugs introduced in one-line fixes. |
Access Control and Key Management
In 2025, access control vulnerabilities caused $953 million in losses — making it the #1 category in the OWASP Smart Contract Top 10. And yet, only 19% of hacked protocols used multisig wallets.
| Area | What to Check |
|---|---|
| Multisig for Admin Functions | Every privileged function (pause, upgrade, parameter changes) must require multiple signers. Use Safe (formerly Gnosis Safe) with 3-of-5 or higher. |
| Timelocks on Governance | Governance actions should have a minimum 24–48 hour delay. This gives the community time to react to malicious proposals. |
| Hardware Security Modules | Store signing keys in HSMs, not software wallets. A compromised laptop should not be able to drain your treasury. |
| Cold Storage for Treasury | Keep 90%+ of protocol funds in cold storage. Only operational funds should be in hot wallets. |
| Role Separation | Separate deployer, admin, pauser, and upgrader roles. No single address should have all privileges. |
| Key Rotation Plan | Document your process for rotating keys if a team member leaves or a key is compromised. |
🛑The Multisig Gap
Only 19% of hacked protocols used multisig wallets. Only 2.4% used cold storage for funds. These are basic operational security measures that cost nothing to implement. If your protocol's admin key is a single EOA on someone's MetaMask, you are one phishing email away from losing everything.
Oracle and Price Feed Security
Oracle manipulation is the third most common DeFi attack vector, as we detailed in Common DeFi Vulnerabilities We See in Every Audit. If your protocol uses external price data, this section is critical.
| Area | What to Check |
|---|---|
| Decentralized Oracles | Use Chainlink, Pyth, or other decentralized oracle networks. Never use on-chain spot prices from a single DEX pool. |
| TWAP Implementation | If using on-chain prices, implement Time-Weighted Average Prices (TWAP) over a meaningful window (15–30 minutes minimum). |
| Price Deviation Checks | Reject price updates that deviate more than X% from the last known price. Set X based on your asset's expected volatility. |
| Circuit Breakers | Auto-pause protocol functions when price feeds show extreme volatility or staleness. |
| Oracle Redundancy | Use multiple independent price sources. If one oracle fails or is manipulated, the others provide a sanity check. |
| Stale Price Protection | Check the oracle's lastUpdated timestamp. Reject prices older than your acceptable staleness threshold. |
Flash borrow $50M in ETH
Attacker borrows a massive amount from Aave or dYdX — no collateral needed
Dump into target protocol's price oracle pool
The massive sell tanks the spot price on the DEX pool the protocol reads
Trigger liquidations at manipulated price
Protocol liquidates positions based on the artificially depressed price
Buy liquidated assets at discount
Attacker scoops up assets at a fraction of their real value
Repay flash loan + profit
Return the borrowed ETH. The damage is done. Total attack time: one block.
Flash Loan Protection
Flash loans amplify every other vulnerability. A bug that would cost an attacker $10,000 of their own capital to exploit becomes free with a flash loan. For the full mechanics, see Anatomy of a Flash Loan Attack: Step-by-Step Breakdown.
| Area | What to Check |
|---|---|
| Same-Block Restrictions | For sensitive operations (governance votes, price-dependent actions), require that the caller's balance existed in a previous block. |
| Borrowing Caps | Limit the maximum amount that can be borrowed or deposited in a single transaction. |
| Withdrawal Delays | For large withdrawals, implement a delay or multi-step process. |
| Snapshot Voting | If using token-weighted governance, snapshot balances at a past block — not the current one. See DAO Governance Security. |
Protocol Design Security
These are the architectural decisions that prevent entire categories of attacks.
| Area | What to Check |
|---|---|
| Checks-Effects-Interactions | Always update state before making external calls. This prevents reentrancy by design, not by modifier. |
| Minimal Proxy Exposure | If using upgradeable proxies, initialize implementations immediately after deployment. Uninitialized implementations are hijack targets. |
| Pausability | Include an emergency pause function callable by a multisig. When (not if) something goes wrong, you need a kill switch. |
| Rate Limiting | Limit the rate of high-value operations (minting, withdrawing, parameter changes) to slow down exploits. |
| Composability Risk Assessment | Document every external protocol your contract interacts with. Understand what happens if that protocol is paused, upgraded, or exploited. See The Hidden Risks of DeFi Composability. |
| Upgrade Safety | Use OpenZeppelin's upgrade safety checks. Verify storage layout compatibility. See Smart Contract Upgradability: Security Trade-offs. |
Pre-Launch Operational Security
| Area | What to Check |
|---|---|
| AI-Powered Audit | Start with an AI-powered audit to catch the same vulnerability classes that top-500 auditors find — at a fraction of the cost. RedVolt's Web3 auditor uses 7 specialized AI agents to deliver comprehensive findings with automated PoC exploits, starting at $5,000. It's the fastest way to cover the OWASP Smart Contract Top 10 before engaging additional reviewers. |
| Bug Bounty Program | Launch on Immunefi before or at deployment. Set bounties proportional to TVL (10% of funds at risk for critical bugs). |
| Real-Time Monitoring | Deploy Forta bots and OpenZeppelin Defender Sentinels to detect suspicious transactions immediately. |
| Incident Response Plan | Document who can pause, how to communicate with users, and your war room process. Practice it. |
| Insurance | Consider Nexus Mutual or InsurAce coverage. Costs 2–10% annually but provides a safety net for your users. |
| Verified Source Code | Verify all contracts on Etherscan/Sourcify immediately after deployment. Users and researchers should be able to review your code. |
| Deployment Verification | After deploying, verify that the deployed bytecode matches the audited source code exactly. Tools like Sourcify make this trivial. |
Post-Launch Continuous Security
Security doesn't end at deployment. The attack surface changes as TVL grows, new integrations are added, and the threat landscape evolves.
Monitor
Real-time transaction monitoring with automated alerts for anomalies, large withdrawals, and governance actions.
Respond
Incident response within minutes. Auto-pause capabilities for critical thresholds. War room process for triage and mitigation.
Re-Audit
Every protocol upgrade, parameter change, or new integration triggers a security review. No exceptions.
Evolve
Update your threat model quarterly. New attack vectors emerge constantly — your security posture must keep pace.
The 2025–2026 Attack Landscape
Understanding recent attacks helps you prioritize your defenses:
| Area | What to Check |
|---|---|
| Bybit ($1.5B, Feb 2025) | Access control compromise. A single signing key was the single point of failure for $1.5 billion in assets. |
| Cetus ($223M, May 2025) | Smart contract logic bug in the concentrated liquidity implementation. |
| Blend Protocol ($10.8M, Feb 2026) | Business logic vulnerability in the lending protocol's collateral calculation. |
| CrossCurve ($2.9M, Feb 2026) | Cross-protocol interaction exploit targeting the bridge between Curve pools. |
⚠️The Pattern
The biggest losses come from the simplest failures: single-signer admin keys, missing input validation, untested edge cases. The most sophisticated exploit of 2025 (Bybit) succeeded because of inadequate key management — not a novel zero-day vulnerability. Fix the basics before worrying about exotic attack vectors.
Download the Checklist
Here's the condensed version. Print it. Pin it to your wall. Go through it before every deployment:
Pre-Audit:
- Static analysis clean (Slither, Aderyn, Mythril)
- 100% test coverage including negative paths
- Fuzz testing with defined invariants
- Documentation complete (architecture, requirements, risks)
Smart Contracts:
- OWASP SC Top 10 review complete
- Checks-effects-interactions pattern everywhere
- No single-point-of-failure admin keys
- Proxy/upgrade safety verified
- At least 2 independent audits
Operations:
- Multisig (3-of-5+) for all admin functions
- Timelocks on governance (24h+ delay)
- Emergency pause function tested
- Incident response plan documented and practiced
Post-Launch:
- Bug bounty live on Immunefi
- Real-time monitoring active (Forta/Defender)
- Source code verified on-chain
- Re-audit process defined for all changes
For broader context on DeFi threat landscape, see The State of Web3 Security in 2026 and Cross-Chain Bridge Vulnerabilities: Lessons from $2B in Exploits. For cost planning, see our Smart Contract Audit Cost in 2026 pricing guide.
Need help checking items off this list? RedVolt's AI-powered auditor catches known vulnerability patterns in hours, and our expert review team handles the business logic and protocol design analysis. Start with an AI scan or request a full security engagement.