0xasen
@asen_sec
Followers
3K
Following
3K
Media
56
Statuses
2K
Web3 security researcher. Minimizing trust, line by line.
Joined November 2022
Proud to have placed 2nd in the @code4rena Monad competition. 1,614 wardens, 164K SLOC of Rust and C++. Submitted the most valid findings in the contest. Shoutout to @monad for putting this one up. Huge respect to everyone who competed!
40
6
266
The most underrated thing about AI in security is speed, not accuracy. A 2 hour review instead of a 2 week review means more coverage, more iterations, faster feedback loops. That compounds.
0
0
8
Also observed the same. There are some bugs which fully autonomous AI are better at catching than humans. Similarly, there are some bugs which humans are better at catching at than fully autonomous AI. I think the best security outcomes will result from combining both approaches.
Here's what surprised me though: AI doesn't find fewer bugs. It finds different ones. Stuff I'd catch in 10 minutes, it misses. Stuff I'd need 3 hours to trace through, it flags in seconds.
4
3
59
It's changed how I spend my time. Less arithmetic, more thinking. Still figuring out where the ceiling is. How are you using it?
0
0
5
Here's what surprised me though: AI doesn't find fewer bugs. It finds different ones. Stuff I'd catch in 10 minutes, it misses. Stuff I'd need 3 hours to trace through, it flags in seconds.
3
0
18
What it misses: MEV. Anything that requires thinking "what would an attacker do if they saw this transaction in the mempool." Zero. Protocol-specific logic. Bugs that require understanding intent, not just code. Callback patterns. Unexpected state changes when control leaves
2
0
4
On one codebase it caught that a game's multiplier schedule guaranteed players positive expected value. The house always loses by design. Not a code bug. A game design flaw. AI found it by just doing the math.
1
0
6
What AI is good at: Accounting errors. Math bugs. State corruption. Anything where the answer is "does this arithmetic check out." I've found it to be relentless at this.
2
0
7
I've been running AI on real codebases for the past few months. Client work, contests, bounties. Not toy examples. Here's what I've seen it catch and what it completely misses.
5
3
54
If you're not using AI to build the things that automate your current workflow, someone else is building it for you. And they'll charge you for it.
0
0
15
it'll be obvious in hindsight that AI will be(already is) able to find complex bugs at top human level it's better to embrace it
1
0
9
Working hard every day to secure the web3 space 🫡
The greatest mission in crypto right now is to safeguard the space from hacks. Why? Because there's exactly one thing that's stopping billions and billions more from coming onchain, and it's hacks. Whoever solves that problem is going to make it big. Really big. It won't
0
0
4
Bounties are a game of luck with high rewards and $0 bets. You can either play more or increase your odds. Your coin is your time, energy, and health. Spend it well to level up the stats you need to increase chances. Reach perfect balance to meet the luckiest version of you.
6
9
117
Seeing posts on the TL from audit tools claiming: "We've found the Balancer bug" Which reminds me of something I've realized some time ago that changes slightly your mindset while bug hunting We're not actually hunting for "bugs". We're hunting exploits. A bug might not cause
2
2
21
Wishing a Happy Friday to brand new security researcher "yesofcourse" for scoring $10,000 via Immunefi on a High severity bug report. Enjoy your weekend. You've earned it. P.S. Don’t spend it all on energy drinks.
6
7
103
I just found a bug and got paid on @immunefi This was a long one but worth it at the end. Thank you Immunefi 🙏 #immunefitribe
immunefi.com
The trusted security layer of Web3. Protecting $180B+ in value and powering the next wave of onchain adoption with AI-driven, end-to-end protection for DeFi, stablecoins, RWAs, and institutional...
8
3
78
Less code, more proofs. Spend lines on tests and invariants - not on fancy abstractions.
0
0
7
Don’t wait to be “ready.” Read code, pick an invariant, try to break it. You learn faster from failing tests than from tutorials.
0
1
27