cystack
DeFi Security: Situation and Solution — Examples of DeFi Attacks Included
Published
Users worldwide can join DeFi protocols, following smart contracts rather than complicated legal obligations or paying high transaction fees. As a plus, they can control their money and review transactions transparently.
Here we give examples of three DeFi attacks that remind you to keep your guard up.

Poly made abundant communication and even published a despairing letter, starting with the salutation "Dear Hacker" and inviting the hacker to be its chief security advisor. Luckily, the hacker returned the stolen funds after three days as they only desired to teach Poly a lesson.
Although the network remains in its position in the blockchain market, its DeFi security is under question.
The two Blockchain systems: Ethereum and Solana, were not the targets. Their underlying blockchain architectures are secure. Thus, hackers attacked the overlaying network Wormhole by minting new tokens on the side of Solana and draining the balance in Ethereum.
DeFi security lessons learned - Developers must enhance the security in DeFi blockchain bridges to avoid any possible attacks.
Accordingly, Beanstalk Farm uses the voting power (determined by the token held) to accept loans. Thus, the attackers exploited the governance mechanism by conducting an urgent execution to steal reserve funds away from the liquidity pools.
Attackers often penetrate the liquidity pools of DeFi systems through an oracle manipulation's flash loan. Then, they sell the assets at a significantly lower price to attract perpetrators. Once the perpetrators repurchase the support, the attackers will excite the pool at a higher price.
Hackers attempt to drain out the balance of smart contracts as "if execution is paused in the middle of its running, entered again, and run completely without errors." In other words, they turn the smart contracts into an ATM and take out money.
The hackers attract investments in their new DeFi projects yet delete their traces before the systems are built.
As scammers, hackers can control the DeFi protocol and even do away with liquidity. Technically simple and tremendously profitable!
- Update yourself on the latest knowledge of cryptocurrency and also DeFi technologies.
- Use decentralized and manipulation-resistant oracles to get full-market coverage and stay informed by fair price feeds.
- Improve smart contracts with special functions or whitelist particular external contracts to prevent interactions with unknown smart contracts.
- Carefully research the DeFi projects before you put money in, such as their traces, track records, experiences, etc.
- Ensure that your interactions are only through official channels.
Never put your DeFi security down!
Besides the golden rules above, you should remember that there is hardly a comprehensive list to cover all potential vulnerabilities. The more blockchain and DeFi grow, the more sophisticated attempts hackers create to exploit the systems and steal your money.
HASHEX
Comments
2The incident examples are easier to compare by the violated security property than by the amount lost. That gives a development team a clearer starting point for tests. A failed authorization check and a broken accounting rule need different regressions. I would use those properties as labels beside the historical incident names.
Mitigation also needs an execution owner. A documented pause mechanism is only useful during an incident if the authorized team can actually invoke it. The rehearsal should include the signer's actual steps from receiving the alert to submitting the transaction.
Leave a comment
Share a question or observation about this article.