naming functions in a stripped binary by behavior, not byte signatures
Source Reddit Malware
Discussion
Fnprint is a tool that identifies functions in stripped x86-64 binaries by their runtime behavior rather than byte signatures or control-flow graphs. It microexecutes each function with synthetic inputs, records side effects, and generates behavioral fingerprints to match functions across different builds or optimization levels. This approach is more resilient to recompilation and optimization changes than traditional signature or graph-based methods. Fnprint can also diff two binaries to detect behavioral changes in functions. It currently supports only x86-64 ELF binaries and is open source under the MIT license.
r/Malware (opens in a new tab)u/BusinessStreet21470 points0 comments
strip --strip-all a binary and this still names functions by micro-executing
them and matching the effect trace against a corpus. spot check: zlib corpus vs
a fully stripped O0 build, it named 9 functions and all 9 were right, and it
stays quiet on the ones it isn't sure about (no confident garbage on thunks).
where byte sigs (FLIRT) die on recompile and CFG diffing gets fragile across
opt levels, behavior holds up better. optimized-vs-optimized is still the hard
case, i'm honest about that in the numbers.
x86-64 only atm. https://github.com/1rhino2/fnprint