bibibi.ccLoading…
Aave Founder says the attack targeted a third-party external adapter;Aave v3 contracts unaffected.
Aave Founder responds to security incident:Aave v3 contracts unaffected; third-party external adapter attacked
PANews October 2 reported that Aave founder Stani Kulechov responded to the Aave v3 Loop Safe attack, stating that the exploited component was a third-party external adapter built on Aave v3, and that the Aave v3 contracts themselves were not affected.
Source: https://www.panewslab.com/zh/articles/01a0fb53-98c9-739a-a8f8-a2b889fea282
PANews reported that Aave founder Stani Kulechov responded to the Aave v3 Loop Safe attack.
Stani Kulechov said that the exploited component was a third-party external adapter built on Aave v3.
Stani Kulechov said that the Aave v3 contracts themselves were not affected.
The following is analysis, separate from reported facts. Verify important claims independently.
This means that the reported target of the attack was a third-party external adapter built on Aave v3, rather than the Aave v3 contracts themselves.
If this claim is verified, the scope of the incident differs from a direct attack on the Aave v3 core contracts.
Beginners should distinguish between the underlying protocol contracts and third-party tools built on top of them; their security is not identical.
Loading event timeline…
This term is not in the glossary yet. Browse related concepts in the glossary.
View glossary →This term is not in the glossary yet. Browse related concepts in the glossary.
View glossary →This term is not in the glossary yet. Browse related concepts in the glossary.
View glossary →