2 years ago I did a PoC to run #rust 🦀 in the #pixel modem
Today it shipped in millions of devices!
They grow up to fast! 🥲
security.googleblog.com/2026/04/brin...
#rust #security #smartphone #baseband
Thanks to @elykdeer.bsky.social and the @binary.ninja team for having me on the AI vs AI Binary Ninja stream. Great discussion on agentic RE, tooling, and feedback loops.
www.youtube.com/watch?v=TBqB...
I passed my defense! After a small celebration, it's time to get back to work.
Too many supply chain attacks in one year...
I think the recent iOS exploit kit leaks are a hint of what's to come. I'm less worried about 0-days (since LLMs benefit attackers and defenders roughly symmetrically) and more worried about ubiquitous exploits for n-days.
That is awesome news!!
This Fall, I’m joining the University of Georgia as an Assistant Professor!
I want to push on the fundamentals of software reverse engineering, from decompilation to how humans actually understand code.
I’m looking for PhD students, collaborators, and sponsors. More below.
Congratulations Zion!
"Theory building and evaluation can guide the design and analysis of surveys, and surveys can also be applied to test theories."
My keynote at RE//Verse went great!
(it will be released online later if you missed it!)
Dr. Gladys West, the pioneering mathematician whose work laid the foundation for modern GPS technology, has died. She was 95.
Today's cool visualization of the day is brought to you by arxiv.org/pdf/2512.14045
The world needs more Sankey diagrams.
For types etc to see what the decompiler had for those, that does require not just dwarf eval.
An undefined function that would have referenced an undefined global struct can’t be evaluated.
I think it’s fair to say some structures especially those unidentified in stripped binary by decomp, and whole functions left as undefined data can’t be mapped or meaningless to map in those cases. I think for a majority of the technique you would be able to still do that eval, and you can use xref
I’m not sure I follow, stripping a binary would leave you with a debug binary and a new stripped binary, and you can tie debug symbols to new one, alternatively using the external debug symbols does the same thing?
This DecompileBench paper is pretty slick, especially how they test for semantic equivalence: arxiv.org/pdf/2505.11340
Unfortunately, there's a pretty big limitation that isn't addressed anywhere that I can see. Can you tell what it is?
Episode 23: War Stories with Brendan Dolan-Gavitt (XBOW)!
@tib3rius.bsky.social & @swiftsecur.bsky.social are joined by @moyix.net who shares some AI and human war stories with us!
Links below!
🎙️ #ASE2025 Keynote Speaker Series (2 of 3)
Dr. Cristina Cifuentes, Vice President @ Oracle Software Assurance
“Oracle Parfait – Detecting Application Vulnerabilities at Scale – Past, Present and Future”
🎙️ ASE 2025 Keynote Speaker Series (3 of 3)
Prof. Taesoo Kim (Georgia Tech)
“Hyperscale Bug Finding and Fixing: DARPA AIxCC”
conf.researchr.org/track/ase-20...
🎙️ #ASE2025 Keynote Speaker Series (1 of 3)
What do symbolic model checking, path profiling, and quantum simulation have in common? 🤔
Find out from Prof. Reps (University of Wisconsin-Madison) in his ASE2025 Keynote “We Will Publish No Algorithm Before Its Time”!
conf.researchr.org/track/ase-20...
You've seen the trends in AIxCC: LLMs can hack source, find vulns, and patch them. But what about on binaries without source? Do decompilers close the gap, or is there more to grow?
Come see my talk at DistrctCon where I merge and dissect these two fields: AI Hacking + Decomp.
Must-read for fuzzing folks (read: tooling/algorithms/academia) by Addison Crump
addisoncrump.info/research/wha...
We at @emproofsecurity.bsky.social open-sourced a free firmware reverse engineering workshop for self-study.
Topics: ELF analysis, cracking, malware triage, embedded-Linux, bare-metal, crypto-key extraction, anti-analysis. Docker setup and solutions included.
github.com/emproof-com/...
Screenshot of the blog post intro: Permissive vs Copyleft Open Source Published on Jul 9, 2025. The premise of copyleft licenses is attractive: Create more open source! With permissive licenses, someone can take the code and make proprietary modifications to it and sell it to other people without releasing the modifications. We want people to publish their improvements, right? With copyleft, we can force people to publish their improvements to copyleft code. Businesses will want to use our code because creating it was so much work in the first place. We need copyleft if we want more contributors, more open source, more code re-use, more freedom. Right? Wrong. In this post, I break down all the ways copyleft licenses fail to achieve their stated goals, and explain why permissive licenses succeed where copyleft fails.
I wrote a comprehensive post dispelling many incorrect assumptions about Copyleft vs Permissive open source licenses.
If you author/contribute to open source code, it's worth reading and understanding these nuances!
shazow.net/posts/permis...
New blog post on implementing patchelf-like functionalities using LIEF's Rust bindings:
lief.re/blog/2025-07...
Cool blog of how @aendra.com built @xblock.aendra.dev her automoderation tuned screenshot classifier AI model and pipeline, including all the manual work behind it.
www.aendra.com/xblock-summe...
It was great to see the community come together again at our 4th #FUZZING workshop in Trondheim this year! We drew a big crowd. Enjoyed the super lively discussions.
Thanks to the organizers:
* @rohan.padhye.org
* @yannicnoller.bsky.social
* @ruijiemeng.bsky.social and
* László Szekeres (Google)
