Paras

Posted on Nov 3

Fully Autonomous

Someone drops a file in your lap. No source code, no docs, no idea what it does. Maybe it's a CTF challenge. Maybe it's a suspicious attachment. Maybe it's a dependency you don't quite trust.

So you start the usual ritual: strings here, xxd there, objdump for the imports, another tool for the headers, a different one for the hash. Five tools, five outputs, and you're still stitching the story together by hand.

That's the exact friction hexlens was built to kill.

The problem hiding in plain sight

Binaries don't explain themselves. Every question you ask needs a different tool:

What kind of file is this? — PE, ELF, Mach-O, DEX, .NET — each with its own parser

What does it import? — and does its imphash match known malware?

What's inside? — strings, sections, headers, all scattered across outputs

For CTF players, malware triage, and forensics work, that tool-hopping is the slowest part of the job.…