Selin Aydin runs OBOL's security desk, covering everything from the first drained wallet through to the post-mortem nobody wants to publish. She previously worked in smart-contract auditing, reviewing code for bugs before they became headlines, and now applies the same forensic patience to reconstructing incidents after the fact: where the exploit entered, what the audit missed, and who is quietly exposed next.
Security, custody and the failures that repeat
Her coverage tracks bridge failures, private-key compromises, oracle manipulation and the recurring pattern of protocols shipping unaudited upgrades under deadline pressure. She is equally interested in the unglamorous end of the problem, where most people actually lose money: a signature approved without reading it, a recovery phrase stored badly, a support agent who was never support.
She is blunt about the industry's habit of calling every incident sophisticated when the root cause is a known vulnerability class, and names the pattern rather than softening it for relationships.
At OBOL, Selin writes the custody and security guides, contributes the hardware wallet and self-custody ratings, and publishes incident breakdowns as facts become verifiable — resisting speculation while an exploit is still live and updating figures publicly when they change.