Polyduekes retweeted
“No one is looking at compiled binaries” is a lie that we tell ourselves to justify our behavior with AI. No one stopped looking at compiler output.
Low level programmers have readelf, objdump, nm, strip, ldd, elftool, binsider, capa, shiva, and numerous others for examining and debugging the output of compilers.
Java programmers have javap (disassembler), jar, jmd / jdeps, CFR, Fernflower, JD-GUI, and many more.
.NET programmers have ildasm, dotnet-dump, dotnet-gcdump, ILSpy, dotPeek, dnSpy, and many others.
And no discussion is complete without mentioning @mattgodbolt’s excellent Compiler Explorer. Give it high level source code, your compiler settings, and see what assembly code is produced.
Why do we have all these tools if no one looks at the compiled code?
The answer is simple: people still look at compiled code.
The confusion is because we’ve used compilers for more than three decades now. We have a high trust that a given implementation of a loop will create the same, predictable output each time. We don’t both debugging the assembly because it can’t tell us anything we don’t know.
That is, until it does something horribly unexpected. (Compiler bugs are a thing.) Or we need to understand execution performance. Or our output just isn’t making sense and we need to debug why. Could still be our fault. Could be a misunderstanding of the abstraction on our part. But we READ THE CODE to know what it’s doing.
Don’t let anyone make you feel bad for reading code. The source code is the settings for the machine. If you’re not taking the time to understand the code, you don’t really know what the machine is doing. No matter how clear you think your specification is.
Polyduekes retweeted
To program the machine well, you need to know the latency, throughput, and port assignments of all instructions and keep its microarchitectural state in your head during programming. You need to become one with the machine. You need to live it, breathe it, and be a huge nerd.
Polyduekes retweeted
> finds interesting function in ms binary
> only 2 xrefs
> "nice, should be easy to reach"
> opens call graph
> 🥺🥺🥺
Polyduekes retweeted
The fuzzer that found project-zero.issues.chromium… (and a number of issues prior to that as well) is now open-source: crrev.com/c/7580844
It uses pkeys, trap-handling and single-stepping to intercept and mutate in-sandbox reads (see trap-fuzzer.h). Definitely had fun writing it!
Polyduekes retweeted
The Exploiting Reversing Series (ERS) currently features 945 pages of exploit development based on real-world targets:
[+] ERS 08: exploitreversing.com/2026/03…
[+] ERS 07: exploitreversing.com/2026/03…
[+] ERS 06: exploitreversing.com/2026/02…
[+] ERS 05: exploitreversing.com/2025/03…
[+] ERS 04: exploitreversing.com/2025/02…
[+] ERS 03: exploitreversing.com/2025/01…
[+] ERS 02: exploitreversing.com/2024/01…
[+] ERS 01: exploitreversing.com/2023/04…
In the coming weeks, I will publish new articles covering exploration in areas such as Windows, Chrome, iOS/macOS, and hypervisors.
Have a great day and enjoy reading.
#exploit #exploitation #windows #chrome #macOS #iOS #hypervisors #vulnerabilityresearch
Polyduekes retweeted
BREAKING: Claude found an RCE in Linux executable files. If you chmod +x and run it, it runs. This effects all binaries and shebangged scripts.
Polyduekes retweeted
This is the EDR crowdstrike fears
This is why EDR stonks go down 3000% for every new opus release
while true; do claude -p "is there a virus on my system if so remove it" --dangerously-skip-permissions; sleep 60; done
GG clamav
Polyduekes retweeted
Została wydana nowa wersja BSD Router Project 2.1. BSD Router Project (BSDRP) jest otwartoźródłową dystrybucją FreeBSD, systemem wbudowanym, na potrzeby routerów sieciowych. linuxiarze.pl/bsdrp-2-1/ #bsd #freebsd #router
Polyduekes retweeted
InfoSec: "Running random Docker containers is a massive security risk."
The risk: Spawning a native window to play ASCII DOOM at 60fps.
Polyduekes retweeted
I just released some free exploit development CTFs based on real world CVEs. They include hints, walkthroughs and working exploits if you get stuck.
zeropath.com/blog/zeropath-e…
Polyduekes retweeted
Optimizing subroutines in assembly language (by Agner Fog): agner.org/optimize/optimizin…
Polyduekes retweeted
Started a blog series on writing a minimal ARM hypervisor from scratch — boots as a UEFI app, claims EL2, identity-maps everything through Stage 2.
Chapter 0 just dropped: ARM vs x86 virtualization, UEFI internals, EDK2 setup, first app at EL2.
0xabe.io/hypervisor/arm/2026…
next time i need an audit of my shit i will claim ai wrote it in 2 hours and software engineering jobs are dead
Is this your Database??
Readers added context they thought people might want to know
It’s fake
x.com/cappyishihara/…
1
83



































