I will reverse engineer firmware, binaries, or protocols

At minimum, I need the binary or firmware image and a clear description of what you want to understand or achieve. If you have sample data, logs, network captures, or observed behavior, that helps, but it’s not required.

No. My work is specifically focused on situations where source code and documentation are missing, incomplete, or unavailable. I work directly with compiled binaries and runtime behavior.

No. Reverse engineering is investigative work. I guarantee a thorough, professional analysis and clear documentation of findings, but not the existence of a specific vulnerability.

Yes. I do not perform piracy, license bypassing, DRM cracking, or illegal activity. Work must be lawful and within ethical or contractual boundaries.

You receive a written technical report explaining behavior, data structures, execution flow, and relevant findings. This may include diagrams, pseudocode, and recommendations depending on the project.

Yes. I regularly work with confidential binaries and private systems and am comfortable signing NDAs if required.

It depends on size and complexity. Small binaries may take a few days, while firmware or protocol-heavy projects can take longer. I’ll give a realistic estimate before starting.