@sunsetsyntax Thanks! The level data was embedded directly in the Mach-O executables’ __DATA sections.
Claude Code reverse-engineered the level tables and binary formats, then built a decoder that extracts all the original levels automatically at build time, including some unused ones!
Played Chromatron with my dad ~20 years ago.
I had Claude Code reverse-engineer the PowerPC Mac binaries and remake all 4 games in Rust for Apple Silicon.
I never knew there were 4. The early levels? I can still remember them. Just pure muscle memory.
https://t.co/lAZJuP8VnP
A use-after-free in safe Rust, across the C FFI boundary.
I used rllvm-query on CVE-2026-11941 in quiche to trace the Rust/C path, narrow 169 FFI entry points to 7 candidates, and show where call-graph analysis runs out.
https://t.co/LDQ0Vb6WqU
Merging LLVM bitcode too early throws away structure you may want later.
rllvm 0.5 now treats whole-program bitcode as one possible output: acquire modules, catalog provenance, select what matters, then materialize.
https://t.co/jFzQzHfUHX
Whole-program LLVM bitcode generation sounds simple until you try it on a real codebase. I ran into this years ago while doing program analysis, which led me to build rllvm in Rust and later rules_rllvm for Bazel.
Wrote up the approaches + trade-offs here:
https://t.co/GnLAGZciLC
Starting cairn, a Rust archive of CVE reproductions, for personal learning.
Stone #1: Copy Fail (CVE-2026-31431). Rust port of @theori_io's PoC, reproduced on both aarch64 and x86_64.
My repo: https://t.co/gWm3GvvKv1
We’re hiring Ant Star candidates(https://t.co/hZ98HPj95F) and research interns at Ant Group to work on AI security red-teaming and defense.
If you’re interested in AI + Security research, send your CV to [email protected]
@bcherny There is a plugin called “superpowers” https://t.co/vM39PBBzh7, which works quite well in writing implementation plan, implementation, and code review.
Want to learn about security artifacts? 🤖🧪🚀
@NDSSSymposium seeks enthusiastic Artifact Evaluation committee members (PhD/graduate students, postdocs, industry researchers) to review cutting-edge research materials.
Apply by May 31st: https://t.co/WsgASbb2HS
RTs appreciated 🙏
VehicleSec'24 is ON! Excited to announce the Second ISOC VehicleSec Symposium co-located w/ @NDSSSymposium ! Accept any security/privacy topics that can be related to vehicles (e.g., ground/aerial/underwater/...) & related tech. Paper due: *Dec 15*. Official CFP will be out soon!
CFP officially out here: https://t.co/HsuQy6FqyX! Save the date **Jan 3, 2023** for your awesome work on *any security/privacy issues that can be related to vehicles*, no matter ground, aerial, or underwater. Will also have cash-prized awards, travel grants & community reception!