Farel

THE RESEARCH NOTEBOOK

Under the surface.

Investigations, experiments, and tools.
A closer look at how systems work — and where they break.

Project outlines · TODO fields identify work and evidence still to be added. No findings are claimed.

6 projects

RESEARCH NOTE 01TODO: DIAGRAM
Firmware imageFilesystemAnalysis
Concept illustration · replace with your evidence
Firmware analysisTODO · Details

Inside router firmware

TODO: Identify the router, firmware version, and security question behind the analysis.

What I did
TODO: Describe your extraction, filesystem inspection, and binary analysis workflow.
Result / learning
TODO: Add a verified result or a specific lesson from the investigation.
TODO: BinwalkGhidraLinux
TODO: Repository link
RESEARCH NOTE 02TODO: DIAGRAM
BoardUART / SPICapture
Concept illustration · replace with your evidence
UART & SPI researchTODO · Details

At the hardware boundary

TODO: Identify the board and the UART or SPI interface you investigated.

What I did
TODO: Document your pin identification, voltage checks, and capture process.
Result / learning
TODO: Add an observed behavior and the evidence supporting it.
TODO: Logic analyzerUARTSPI
TODO: Repository link
RESEARCH NOTE 03TODO: DIAGRAM
DeviceProtocolTrust boundary
Concept illustration · replace with your evidence
Embedded & IoT securityTODO · Details

Mapping an embedded system

TODO: Introduce the authorized test device and its trust boundaries.

What I did
TODO: Describe the architecture mapping and testing you personally performed.
Result / learning
TODO: Summarize a supported finding or threat-model improvement.
TODO: WiresharkLinuxPython
TODO: Repository link
RESEARCH NOTE 04TODO: DIAGRAM
BinaryControl flowBehavior
Concept illustration · replace with your evidence
Reverse engineeringTODO · Details

From binary to behavior

TODO: Describe the binary, architecture, and behavior you wanted to understand.

What I did
TODO: Explain your static and dynamic analysis and how you validated the interpretation.
Result / learning
TODO: Add a documented explanation of the recovered behavior.
TODO: GhidraGDBAssembly
TODO: Repository link
RESEARCH NOTE 05TODO: DIAGRAM
InputMemoryMitigation
Concept illustration · replace with your evidence
Binary exploitationTODO · Details

Understanding memory safety

TODO: Name the local lab or CTF challenge and its learning objective.

What I did
TODO: Describe your debugging, root-cause analysis, and local proof of concept.
Result / learning
TODO: Explain the memory-safety lesson and relevant mitigations.
TODO: pwntoolsGDBC
TODO: Repository link
RESEARCH NOTE 06TODO: DIAGRAM
InputAutomationEvidence
Concept illustration · replace with your evidence
CTF tooling & automationTODO · Details

Less repetition. More analysis.

TODO: Identify a repetitive security or CTF workflow you wanted to simplify.

What I did
TODO: Describe the scripts, command-line tools, or automation you built.
Result / learning
TODO: Add an example output or a measured, reproducible improvement.
TODO: PythonBashGit
TODO: Repository link

LET’S CONNECT

Good research starts
with a conversation.

Get in touch