Real breach investigations, written start to finish.
Each report rebuilds the full attack, from how the intruder got in to everything they did next, backed by a complete timeline and MITRE ATT&CK mapping. Investigated by Forge members in our hands-on SOC Simulator, CTF labs, and real phishing samples that hit our inbox.
Microsoft Edge Wrote to RunOnce Again: Why the Right Answer Isn't Always to Suppress the Alert
A Forge member's benign-triage playbook: two RunOnce alerts, a KQL historical baseline across three dates, and why the right call isn't always to suppress the detection.
DKIM=NONE Is Not DKIM=FAIL: Tuning an Over-Broad Email Auth Alert for DMARC Alignment
A benign SPF/DKIM alert triage from MYDFIR Forge: why DKIM=NONE is not DKIM=FAIL, and the two-line tuning fix using DMARC alignment.
A Multi-Host Python C2 Investigation at Kerning City Dental
Nigel Dean traces a py.exe C2 beacon alert on KCD-Web that IOC scoping surfaced as a two-host compromise, with identical Drivers_EveryMinute persistence on both hosts.
0/91 VirusTotal Detections, Still Phishing: The Structural Indicators Every Email Analyst Should Look For
Graham McKean analyzes a real Shure Media YouTube partnership phishing email received at MYDFIR: 0/91 VirusTotal detections, SPF and DKIM passed, but structural indicators reveal Likely Phishing.
Want to write reports like these?
Forge members investigate real attacks live in the SOC Simulator, CTF labs, and real phishing samples that land at MYDFIR, then publish their work here. Every report you read is the analyst's own investigation.