rev.ng
@_revng
Followers
5K
Following
23
Media
199
Statuses
529
Building the next generation decompiler. Binary analysis is a dish best served static.
Joined October 2018
π BIG ANNOUNCEMENT! π The full rev.βng decompiler pipeline is now fully open source! Also, we'll soon start to invite people to participate in the UI closed beta. Check out our latest blog post: https://t.co/9YchJS4RIG
1
95
347
We're now based on QEMU 8, we need some more work to further upgrade to QEMU 10.
0
0
1
β« After many many years, we upgrade our QEMU fork! Goodby libptc, welcome libtcg! Here you can find a summary of the improvements this brings: https://t.co/PlHdGrBzvG Moreover, we can now support Hexagon, RISC-V and Loongarch.
github.com
This commit drops libptc in favor of its new form libtcg. It brings several improvements, among which: * The QEMU version we work on has been upgraded. * CPUStateAccessAnalysis has been reimpleme...
2
1
18
π Weβre excited to host the 9th Nix Milano Unconference at our HQ! Seats are limited, so hurry up and register! π
Saturday, December 13, 2025 at 9.30 AM π Via Carlo Farini 57A, Milan π
meetup.com
**Ciao! π** Excited to kick off another great meetup! Join us at **rev.ng Labsβ office** in **Milan** (10-minute walk from **Garibaldi station**) on **Saturday, December
0
1
6
For your enjoyment, the video of the talk has been published: https://t.co/LtUNFX6QZa π€¦ββοΈ No warning, no nothing. Published as a regular talk π€·ββοΈ
0
1
8
π’ 2nd part of our Black Hat Arsenal talk is out! Python scripting! πππ
1
0
1
You can find it on YouTube as well: https://t.co/dCCzhr7OFL Also, soon we'll publish part 2 about Python π scripting!
0
0
2
π΄ We just published our Black Hat Arsenal talk (part 1)! It's a brief tutorial on: 1. using https://t.co/BpzWlLVmIo from the CLI; 2. playing around with the decompiled code in VSCode; 3. finding bugs with clang static analyzer! π¦Ύ
1
2
9
Our results wouldn't have been possible without the support of our sponsors, who helped us get the whole team together to Vegas: π₯ #7Layers - #DRIVESEC π₯ @_revng - @KeylessTech - @WuerthPhoenix - @CNIT_TLC π #STACKBITS
1
1
1
π’ Aaand here is Anton's talk about QEMU+RISC-V at KVM Forum 2025! Automatic Frontend Generation for RISC-V Extensions Video: https://t.co/B2ulGhMhLd (21:37) Code: https://t.co/T5ESVmSFIi π¦Ύ
0
3
6
π Tomorrow and Friday we'll be at #KVMForum at Politecnico di Milano! π’ Catch Anton's talk on Friday, 9:15 (Aula De Donato): Automatic Frontend Generation for RISC-V Extensions. π
pretalx.com
QEMU is an extremely useful tool during testing and development of new architectures, yet adding support for new targets is error prone and incurs a significant entry cost in terms of learning QEMU...
1
0
4
Needless to say, the people reviewing talk submissions at DEF CON bear some responsibility in all of this, but I don't think I'm in the position to judge without full context.
1
1
61
What puzzles me is: if this is all made up, why not go the extra mile and state you can emit deobfuscated code?
1
0
24
Conclusion? I don't know. Either he has something, ran out of time, panicked, created the whole project with an LLM or he had a bet with his friends like "wanna bet I can get *two* talks accepted with pure AI slop?". In the latter case, he won.
1
2
29
Presentation and demos are quite similar: https://t.co/tb6Xkec3Ia
https://t.co/D5AWB3ZLfN The code is not released:
github.com
A modular, extensible security automation and intelligent analysis framework. It orchestrates multi-phase software and binary analysis: discovery, detection, fuzzing, ML-assisted pattern evolution,...
1
0
14
Now, the guy had *another* talk at DEF CON, which I didn't manage to attend. Captivating title: Jailbreaking the Hivemind Finding and Exploiting Kernel Vulnerabilities in the eBPF Subsystem
1
0
15
Actually understanding what the obfuscated code was doing was, in his terms, "analysts enrichment". I call that "actual reversing".
1
1
22
Overall, I was unhappy for the quality of the talk and due to the fact that he wasn't actually emitting deobfuscated code (as we do), but just identifying opcodes. At the offline Q&A he mentioned that he "had some ideas" on how to do that with Ghidra.
1
0
22
After a few questions, I left. The feeling was: the work was quite flaky but, removing the fog, he seemed to have some way to identify dispatchers and was using random forest to pattern match what an opcode was doing based on some ground truth he had from past analyses.
1
1
18