Skip to content
AS
01 / Security Engineering2026

Malware Analysis Tool

Static analysis that speaks detection language: PE inspection, YARA matches and MITRE ATT&CK mapping in under thirty seconds.

PythonYARAPE analysisMITRE ATT&CK
Case file
Role
Solo build — research, engineering, documentation, release
Status
v1.1.0 · released
Year
2026
Position
01 of 13
Case 01 / malware-analysis-toolArchitecture · Evidence · Signal

01 — Context

The problem worth solving.

SOC tier-1 analysts burn hours on static checks that should be automated. Worse, the output is usually a wall of strings — not a decision an analyst can act on within the first five minutes of a queue.

02 — Approach

How it was built.

  1. 01

    Parse PE headers, sections and imports into a normalised triage feature set.

  2. 02

    Layer YARA rules over the sample and weight matches by confidence, not by count.

  3. 03

    Map every meaningful finding to a MITRE ATT&CK technique.

  4. 04

    Emit an explainable risk score plus a Markdown summary an analyst can paste into a ticket.

03 — Architecture

The shape of the system.

01Entry

One CLI command takes a sample directory and a rule pack.

02Analysis

PE parser normalises headers, sections, imports and entropy.

03Detection

YARA rule packs run with per-match explainability.

04Mapping

Findings are mapped to ATT&CK techniques and scored.

05Output

JSON for machines, Markdown for humans, exit code for pipelines.

04 — Evidence

Receipts, not adjectives.

6/6tests passing
<30stypical triage
v1.1.0tagged release

05 — Hiring signal

“Shows detection engineering instincts, not just scripting: every finding maps to a technique an analyst would actually hunt for.”

Ships working systemsDocuments the methodExplains the trade-offsKeeps evidence attached

06 — What's next

Still being built.

Add sandboxed dynamic execution and Sigma rule export so detections can ship straight to a SIEM.