🎉 #Gate xStocks Trading Share# Posting Event Is Ongoing!
📝 Share your trading experience on Gate Square to unlock $1,000 rewards!
🎁 5 top Square creators * $100 Futures Voucher
🎉 Share your post on X – Top 10 posts by views * extra $50
How to Participate:
1️⃣ Follow Gate_Square
2️⃣ Make an original post (at least 20 words) with #Gate xStocks Trading Share#
3️⃣ If you share on Twitter, submit post link here: https://www.gate.com/questionnaire/6854
Note: You may submit the form multiple times. More posts, higher chances to win!
📅 End at: July 9, 16:00 UTC
Show off your trading on Gate Squ
Review of the Eight Major Security Incidents in DeFi in 2022: Losses Exceed $4.3 Billion
2022 DeFi Security Incident Review
Author: a certain security expert
Recently, a seasoned security expert shared a lesson on DeFi security for community members. He reviewed the significant security incidents that the Web3 industry has encountered over the past year, discussed the causes and preventive measures of these incidents, summarized common security vulnerabilities in smart contracts, and provided some security recommendations. This article organizes his shared content as follows for the reference of DeFi enthusiasts.
According to statistics, over 300 blockchain security incidents occurred in 2022, with a total amount involved reaching 4.3 billion USD.
The following is a detailed analysis of 8 typical cases, most of which have losses exceeding 100 million dollars.
Ronin Bridge
Event Review:
This attack is a typical APT( advanced persistent threat). The hacker group first controlled a computer within the target organization through methods such as social engineering to serve as a springboard for further infiltration, ultimately achieving their attack objectives.
The incident exposed the weak security awareness of the company's employees and issues within the internal security system.
Wormhole
Event Review:
Wormhole mainly encounters issues at the code level, using some deprecated functions. It is recommended that developers use the latest version to avoid similar problems.
Nomad Bridge
Event Review:
This is a typical case. There are issues with the initialization settings, leading to valid transactions being executed multiple times. After discovering this, MEV bots and others broadcast attack transactions in large quantities, resulting in a money-grabbing incident.
The open-source nature of the smart contract ecosystem makes it easier for hackers to analyze and discover vulnerabilities. Once a project has a vulnerability, it is basically declared a failure.
Beanstalk
Event Review:
Attack Process:
This case exposes the potential risks of a purely decentralized governance mechanism. It is recommended that the project implements security measures such as proposal review mechanisms, voting thresholds, and time locks.
Wintermute
Event Review:
On September 21, 2022, Wintermute confirmed that it had been hacked. They had used the Profanity tool to create vanity wallet addresses to optimize transaction fees. Although they accelerated the phasing out of old keys after learning of the vulnerability in Profanity, an internal error resulted in the failure to completely revoke the signature permissions of the affected addresses, leading to the theft of funds.
When using open-source tools, security risks should be fully assessed. Tools related to key management require even more caution.
Harmony Bridge
Event Review:
If it is indeed the work of North Korean hacker groups, the attack method may be similar to the Ronin Bridge incident. In recent years, North Korean hacker groups have been very active in targeting the cryptocurrency industry.
Ankr
Event Review:
Subsequent investigations revealed that the incident was caused by a malicious act of a former employee. The exposed issues include:
Mango
Event Review:
This can be seen both as a security incident and as an arbitrage behavior. The main issue lies in the business model vulnerabilities, where the prices of small-cap coins are easily manipulated, leading to difficulties in position management on the platform.
Project teams should fully consider various extreme scenarios for testing. Users participating in the project should also comprehensively assess risks and not focus solely on returns.