How DeFi differs
Decentralized applications can reduce reliance on an intermediary, but introduce contract, governance and infrastructure risks. There is no universal chargeback or deposit-insurance protection. Some services have support or limited coverage, but completed on-chain transactions generally cannot be reversed through a bank-style dispute.
Ronin Bridge: about $620 million
Attackers obtained the five validator signatures needed to authorize withdrawals in the nine-validator system. The March 2022 incident exposed the bridge’s dependence on a small set of signing keys.
Wormhole: about $320 million
A signature-verification flaw allowed an attacker to mint unbacked wrapped ETH. Jump Crypto subsequently replenished the bridge with 120,000 ETH; this response is not a guarantee that another bridge would reimburse users.
Euler Finance: about $197 million
An exploitable lending function and flash loans enabled the March 2023 attack. After negotiations, Euler announced in April that all recoverable funds had been returned. That outcome was unusual and should not be expected after an exploit.
Past exploits show that contract and signing risks can cause substantial losses. Evaluate the specific protocol and your ability to understand permissions rather than treating every decentralized application as equally safe.
Five risk categories
These five categories illustrate common risks. They are not an exhaustive list, and several can combine in one incident.
Drainer
A signature that grants dangerous permission
A convincing copy of an application may request a signature or token approval rather than an obvious payment. Depending on the permission, an attacker can transfer approved tokens or NFTs. One approval does not automatically grant access to every asset in the wallet.
Rug Pull
The team removes the liquidity
Anonymous developers, concentrated token ownership, weak review and extraordinary return promises deserve scrutiny. Chainalysis attributed over $2.8 billion to rug pulls in 2021, including a large centralized-exchange case; that total was not exclusively DeFi liquidity withdrawals.
Contract flaw
Bugs in deployed contract code
Reentrancy, missing authorization checks and arithmetic mistakes can expose funds. An immutable contract cannot simply be patched in place; migration or other mitigations may be needed. An upgradeable contract introduces its own governance and administrator risks.
Bridge
Two networks and an additional trust model
A bridge relies on security across networks and on its own verification or signing system. Past bridge exploits show why users must examine those additional assumptions rather than treating bridged assets as identical to native assets.
Oracle
A manipulated price
A protocol relying on a manipulable market price can value collateral incorrectly. A flash loan can amplify an attack, but the vulnerable price or accounting mechanism is the underlying problem.
Token permissions: an ongoing exposure
Some token-based swaps or protocol deposits ask you to grant a token approval, allowing a specified spender to move defined tokens. The requested amount can be limited or unlimited; inspect the scope instead of assuming every interaction works the same way.
A standard allowance may remain after your session ends. A malicious or later-compromised spender can use an applicable allowance without another confirmation. Other signature and permission systems can have different rules.
Open the official Revoke.cash site
Look up your public address to inspect approvals. Connecting a wallet alone does not authorize spending, but check every subsequent request before signing.
CautionType revoke.cash yourself or use a verified bookmark. Fake approval-management sites can request the very permissions you intend to remove.
Prioritize risky permissions
Review unfamiliar spenders, unlimited allowances and applications you no longer use. Check the selected network as well as the assets covered by each permission.
Revoke unnecessary permissions
Revoking a standard approval requires a network transaction and gas. Prioritize suspicious permissions and valuable assets. Revocation does not recover stolen funds or repair a compromised recovery phrase.
Make reviews a habit
Review permissions after using DeFi and periodically thereafter. Many standard allowances remain until used, changed or revoked; other permission schemes can have different expiry rules.
Review a protocol before using it
An audit means reviewers examined a defined scope and documented findings. Check whether serious issues were resolved and whether the review still covers the deployed version. It does not establish that every failure mode was found.
Findings
Were serious findings resolved?
Read critical and high-severity findings and how they were resolved. An audit with unresolved critical issues is a warning, not a safety certificate.
Scope
What was actually reviewed?
Check the exact contracts, code revision and exclusions covered by the report. A review of one component does not establish the safety of an entire application.
Version
Does it cover the current version?
Compare the audited revision with the deployed code and subsequent changes. Age alone is not a reliable cutoff: a recent report can still omit a major update.
Independent review
Look for independent scrutiny
Multiple independent reviews and an active bug-bounty program can improve scrutiny. They still cannot guarantee that all vulnerabilities have been found.
Ten practical checks
Use a compatible hardware wallet
A hardware wallet protects signing keys and requires device confirmation. It cannot protect funds if you approve a malicious transaction or permission. Read the device display and avoid blind signing.
Use a separate wallet for DeFi
Keep experimental application activity separate from long-term holdings. Limiting the assets and permissions in that wallet can reduce the amount exposed.
Limit the initial exposure
Start with an amount you can afford to lose. A successful small transaction or several quiet weeks does not establish that a new protocol is safe.
Review and revoke permissions
Review approvals after sessions and revoke unnecessary permissions. Combine this with careful signing; revocation alone is not a complete security plan.
Use verified bookmarks
Avoid opening wallet applications from search ads, unsolicited messages or Discord links. Verify the domain independently and bookmark it.
Read the signing request
Check the spender, asset and amount before approving. A swap may legitimately need an allowance, but an unexpected or excessive permission is a reason to stop and investigate.
Inspect a supported transaction preview
Use a reputable wallet’s transaction preview or simulation where available. It can show a transaction’s estimated balance changes, but a standard simulation is not guaranteed to match what happens on-chain.
Examine the protocol’s track record
Review operating history, administrator powers, liquidity and independent audits. A large value locked or a familiar name does not rule out an exploit; unusually high yields need additional scrutiny.
Understand the bridge’s trust assumptions
Compare the network’s official bridge with alternatives, including verification, administrator powers and withdrawal constraints. Splitting a transfer can limit an operational mistake but does not remove a bridge vulnerability.
Question extraordinary yields
Treat triple-digit annual yields as a warning of substantial risk. Determine where the return comes from and whether incentives, leverage or later participants are funding it.
A hardware wallet adds device confirmation, but cannot make a malicious permission safe. Check what its display actually explains and avoid blind signing. Compare supported devices in the Wallet comparison, and setup guidance in the Hardware-wallet setup guide.
