Тёмный

The TORN Governance hack EXPLAINED 

The Red Guild
Подписаться 503
Просмотров 530
50% 1

A step-by-step explanation of the TORN Governance hack. We use diagrams, code and transaction tracing to explore the whole incident, and understand how it could have been prevented.
Rekt article: rekt.news/tornado-gov-rekt
Cast: book.getfoundry.sh/cast
Transaction tracer: openchain.xyz/trace
EIP for CREATE2: eips.ethereum.org/EIPS/eip-1014
Code: github.com/tinchoabbate/eth-sec-lab/tree/main/torn-governance
Follow The Red Guild!
- Our newsletter: blog.theredguild.org
- Twitter: theredguild

Опубликовано:

 

10 сен 2024

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 4   
@acaizman
@acaizman 10 месяцев назад
Sorry if this sounds stupid but I’m confuse. How does the attacker managed to call emergencyStop function if they are not the owner?
@gunjansurti
@gunjansurti 10 месяцев назад
Same question mate
@gunjansurti
@gunjansurti 10 месяцев назад
And only answers can be stupid and the questions
@ivandosev1139
@ivandosev1139 7 месяцев назад
It is called by the Deployer Contract not by the EOA account. EOA which is the attacker triggers only Deployer contract which is the owner of the Prop. factory hence can selfdestruct it
Далее
The Euler Finance hack EXPLAINED
30:56
Просмотров 1,5 тыс.
Junio en The Red Guild 2023 | RESUMEN
12:21
Quickstart: Using ASP.NET Core Identity
11:11
Have You Picked the Wrong AI Agent Framework?
13:10
Просмотров 65 тыс.
How Ian Hubert Hacked VFX (and you can too!)
22:26
Просмотров 141 тыс.
OpenBSD Desktops Are For Hackers Only
13:14
Просмотров 200 тыс.
Home Assistant Community Store version 2 (HACS)
7:31