SharkTeam has conducted a technical analysis of this incident and summarized the security prevention means, hoping that the subsequent projects can take warning and build a security line for the blockchain industry.Attacker 1: 0x7e39e3b3ff7adef2613d5cc49558eab74b9a4202 (abbreviated as 0x7e39)Attack Contract 1: 0xd996073019c74b2fb94ead236e32032405bc027c (abbreviated as 0xd996)Attacker 2: 0x7fe83f45e0f53651b3ed9650d2a2c67d8855e385Attack Contract 2: 0x4148310fe4544e82f176570c6c7b649290a90e17Target contract under attack: 0x1cc79f3f47bfc060b6f761fcd1afc6d399a968b6The attack consists of 16 transactions, taking the first attack transaction as an example:0x00c503b595946bccaea3d58025b5f9b3726177bbdc9674e634244135282116c7The attack flow is as follows:1.Read all collateral and obligations in the target contract at address 0x56a201b872b50bbdee0021ed4d1bb36359d291ed (abbreviated as 0x56a2).