REhints (@REhints) profile picture

sharing reverse engineering knowledge

Joined May 2013
Photo by REhints (@REhints)Photo by REhints (@REhints)Photo by REhints (@REhints)Photo by REhints (@REhints)Photo by REhints (@REhints)Photo by REhints (@REhints)Photo by REhints (@REhints)Photo by REhints (@REhints)Photo by REhints (@REhints)
idasql 0.0.20 released with IDA 9.5 release. My favorite features are the instance discovery and communication, the database rescue feature, and UI actions surface.
idasql 0.0.20 is out, with IDA 9.5 support. Your agent now works with every IDA you have open. It finds them, starts the server it needs, and tells you what it changed. IDA 9.2-9.5 · Windows, Linux, macOS · x64 and ARM64 github.com/allthingsida/idas…
1
2
6
619
Announcing a major milestone achieved by my team @GoogleDeepMind: we have proven key security properties of the machine code underlying the Signal messaging protocol. This is the first time the actual production code of a widely deployed protocol has been formally verified – by any method, with or without AI – and at this depth. More than a research breakthrough, it’s a prime example of how frontier AI can be a force multiplier to counter the speed and scale of modern cyber threats. Formal verification offers a higher standard of security; however, it’s extremely complex and time consuming, which is why in many cases it’s considered to be impractical. Similar efforts could take teams decades of combined effort. We did it in a month’s time. Using AlphaProof Code, Google DeepMind's new agentic framework for formal verification that runs on LLMs including Gemini Carbon, we verified the Signal protocol down to the actual code running on devices.  This milestone lays the groundwork for a future in which vital systems, from medical device firmware to power grid software, ship with mathematical proof that their protections work. Reaching that future will take continued research from our community. In that spirit, we're open-sourcing our formal specifications and verification artifacts so others can build on this work. On a personal note, this moment is of deep significance to me. I started my own research journey more than two decades ago as an intern working on checking the consistency of complex software systems. Seeing this grand challenge made practical with modern AI is extraordinary. I'm extremely proud of my team members: Swarat Chaudhuri, Andrew Ferraiuolo, Anton Kovsharov, Tej Chajed, Sam Schlesinger,  Karn Seth, Jonathan Katz, and Charles Sutton for taking on this grand challenge and delivering, and grateful to the Signal team for their partnership. deepmind.google/blog/formal-…
223
694
233
5,723
581,829
REhints retweeted
30 years ago today, Phrack 49 published Aleph One’s “Smashing the Stack for Fun and Profit”. A legendary paper that inspired generations of hackers and helped shape modern exploit development. Still an essential reading. phrack.org/issues/49/smashin… Phrack 73 is coming soon!
28
386
35
1,500
57,730
Many people have a shallow understanding of what Rust actually guarantees. The borrow checker is great for ensuring memory safety *within an application*, the guarantees for multi-process interaction (and even interaction with shared libraries etc.) aren't the same thing.
People are asking how you corrupt memory in a sandbox written in Rust. 🦀🔥 The spark came from an unsafe block: mmap(MAP_FIXED) failed after unmapping a guest-RAM page. KVM kept pointing there; Firecracker reused it. Guest writes became VMM writes. 🏴‍☠️
13
15
176
8,026
REhints retweeted
Good news! We've wrapped our initial "Lights Out" research into out-of-band management devices and BMCs. The final advisories are live and OOBscan now includes detections for all issues. The bad news: many of these issues still have no patch: github.com/runZeroInc/oobsca…
7
49
3
106
11,173
REhints retweeted
Slides from the talk @mlippautz and I gave at the recent @offensive_con in Tokyo: saelo.github.io/presentation… Blog post for the Fuzzing vs. AI part: projectzero.google/2026/10/f…
3
59
3
226
19,611
REhints retweeted
Code-execution flaw in UEFI firmware affects most servers on planet Earth: arstechnica.com/security/202… Great work by Alex Matrosov (Anthropic) and Dan Holmes-Mitra (Google)!
4
23
2
60
7,938
I have just noticed that my Scudo internals paper (released while at L3Harris Trenchant) can't be (easily?) found anymore due to website changes... here is a link to a pdf copy for those that need it: github.com/rrbranco/ScudoAll…
3
12
79
4,159
REhints retweeted
this blog shows some of the worst bugs claude found, including a zero-click rce on the linux networking stack that roots a server over the network with no creds or interaction, and tens of full rce chains in chrome (recording below is the one in the blog): anthropic.com/research/disco…
9
52
10
505
103,255
LLMs are great at finding bugs, but so are fuzzers. @5aelo compared the vulnerabilities found in V8 by BigSleep, an agentic system, with those found by the Fuzzilli fuzzer. projectzero.google/2026/10/f…
13
109
7
446
42,830
REhints retweeted
Submit to the CFP! We close in 5 daysssssss
Our CFP is still open! Submit your talks on -bizarre reverse engineering projects -tool releases -exploits and vulnerabilities -Non-technical and policy talks on cyberz districtcon.org/cfp
1
5
7
1,174
REhints retweeted
📢 IDA 9.5 is here: more platforms, more agentic power. → 3 new decompilers: Android Dalvik, Infineon TriCore and Qualcomm Hexagon → IDA MCP and Assist for AI-driven reverse engineering → Recursive decompilation across call graphs → IDA Home now includes 11 cloud decompilers instead of 2, at the same price → And much, much more It’s one of our biggest releases yet. Active license holders can download it now from the Download Center. hex-rays.com/blog/ida-9.5-re…
12
56
4
401
20,418
AI-assisted research is killing embargoes. Coordinated disclosure will never be the same. The industry used to have the luxury of testing or sitting on a fix for months. Not anymore. When everyone's using the same tools and the same intelligence to find vulnerabilities, you're not the only one finding that bug. Product security and PSIRT need a serious rethink: less gatekeeping, more proactive evaluation of security posture, and shipping fixes continuously at scale. The biggest impact will be in firmware and hardware, where disclosure timelines have historically stretched past 12 months. That mindset is a leftover from outdated processes and slow testing and bring-up environments.
7
20
2
71
6,671
My presentation at Hexacon is done ! Time for public disclosure. Pictured below: remote unauthenticated code execution over-the-air (including the shell) on Proximus BBOX 3V+
6
57
4
267
16,489
REhints retweeted
Yes my passcode is really 555555
Replying to @calif_io
4/ APT stands for Apple Persistent Threat
14
12
1
182
19,021
Exciting work from @willzhou97 (Fellow, now full time!) and @bucketofkets on the Frontier Red Team. One of the cool parts of the job is seeing a future world early. We think this one is ~pretty underpriced. "We should aim to harden our systems to make it difficult for such replicators to spread, but also prepare to deal with a world where they are here to stay."
Anthropic's Frontier Red Team believes small AI models may now be months away from being capable of self replicating without access to a datacenter. Quoting from the blog: 'The capabilities that make AI models generally powerful coding agents also generalize to cyber tasks, including autonomous replication. Like coding agents in 2024, we’re seeing signs of life for AI worms. We don’t yet have a full rogue replicator, but agents are becoming increasingly capable of completing the individual steps in the replication chain (and passing on their adaptations to future copies of themselves). At the same time, increasing amounts of inference compute are now available both inside and outside of datacenters (see Appendix D). It’s uncertain exactly what form autonomous AI replication will take. It could be a slow, distributed “digital slime mold,” living on relatively insecure compute. It could also be a powerful cyber model that breaches datacenters at a high pace, or a model that scams people for compute credits. As a prediction that goes beyond our experiments, we expect a future awash with agents running on all types of hardware, including some that aren’t under human control. While it’s true that IoT devices have been vulnerable for a long time, lightweight agents may be much more willing than human attackers to put in the effort to compromise large fractions of the world’s IoT compute. The rise of slow replicators would also be a bellwether for more aggressive, faster ones that can breach more hardened machines or be effective API key thieves. We should aim to harden our systems to make it difficult for such replicators to spread, but also prepare to deal with a world where they are here to stay.'
23
28
7
238
28,506
Very excited to share details on the bugs used in our full chain Chrome exploit! We used three bugs (V8 corruption, V8 sandbox escape, and renderer sandbox escape via Crashpad). The third bug is my favorite!
Replying to @Xbow
7/ Read more on the blog: xbow.com/labs/research/zero-…
15
55
2
256
16,834
📚 Slide decks from OB1 2025 & 2026 are live! Catch up on talks you missed, revisit top sessions, or dive into the technical breakdowns. Most slides are up on GitHub: 👉🏻 github.com/star-sg/OBO Huge thanks to all our speakers, sponsors, activity partners, and attendees!
24
1
80
4,958
Agenda for OffensiveCon Tokyo 2026 is live! Explore the talks and plan your schedule now: offensivecon.jp/agenda/2026.… #OffensiveCon #Tokyo
22
6
39
9,809