SEC-T 2026

Sofia Bobadilla

Sofia Bobadilla is a 3rd year PhD student at KTH Royal Institute of Technology. Her research focuses on automated exploit generation and vulnerability repair for smart contracts, building systems that find and fix bugs before attackers do. Her work has been adopted as reference guidelines for AI-assisted security research in the Ethereum ecosystem, and she is a member of KTH's Software Supply Chain Security group CHAINS. In 2024 she won the ETHPrague hackathon with a code fix verification tool.


Session

09-09
13:15
45min
Yippee-Ki-Yay, Blockchain: Exploiting Decentralized Systems One Die Hard at a Time
Sofia Bobadilla

Blockchain systems have redefined what it means for an attack to be permanent. Smart contracts are immutable by design; once deployed, their logic cannot be patched. Every vulnerability is forever, every stolen asset is gone, and the code is public for anyone to study and exploit.

Despite governing hundreds of billions of dollars, these systems keep failing in ways that any security practitioner will recognize: logic bugs that trust the wrong sequence of operations, access control that collapses under social engineering, and infrastructure implants so well-engineered they remain invisible for weeks.

In this talk, we examine three landmark exploits through the lens of the Die Hard films. This is not a gimmick; each film captures something structurally true about the corresponding attack. Gruber exploiting Nakatomi's own vault logic. Terrorists who seized the control tower, not the planes. Simon Gruber keeping everyone chasing riddles while the real crew drills into the Federal Reserve. The analogy makes unfamiliar attack surfaces immediately intuitive for any security practitioner, regardless of blockchain background.

We cover the 2016 DAO hack ($60M), the Parity and Ronin multisig failures ($905M combined), and the 2025 CPIMP attack, a clandestine supply-chain implant across seven blockchains, invisible to every monitoring tool, defused in a 36-hour coordinated war room. Three failure classes: trust in your code, trust in your keyholders, trust in your infrastructure.

Main hall