mcpField
C
competition-forensic-timeline

competition-forensic-timeline

github.com/zhaoxuya520Security43.7k93 installsUpdated 5w ago
Repository

About competition-forensic-timeline

A CTF skill for turning artifacts from logs, hosts, networks, and mail into a replayable forensic chronology. It follows the sandbox and evidence setup established by `$ctf-sandbox-orchestrator`.

Key features

  1. 01Choose reliable timeline anchors
  2. 02Normalize timestamps and identifiers
  3. 03Correlate events across sources
  4. 04Separate confirmed order from inference

Use cases

  1. 01Reconstruct a chain from initial access to persistence
  2. 02Correlate host and mail artifacts to recover an event sequence

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/zhaoxuya520/reverse-skill --skill competition-forensic-timeline

After installing, type/competition-forensic-timelinein Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/forensic-timeline.md

Details

From the project README

Competition Forensic Timeline

Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.

Use this skill when the hard part is not finding one artifact, but turning many artifacts into one replayable chronology.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Pick the smallest reliable anchor: first execution, first logon, first network session, first file write, or first mailbox action.
  2. Normalize timestamps, time zones, hostnames, users, process IDs, message IDs, and file paths before correlating.
  3. Build one minimal chain from foothold to persistence, execution, access, or exfiltration.
  4. Separate confirmed event order from inferred gaps.
  5. Reproduce the decisive timeline segment that yields the artifact or privilege conclusion.

Workflow

1. Establish Timeline Anchors
  • Collect only the active surfaces: EVTX, Sysmon, registry, Amcache, prefetch, browser artifacts, mail traces, PCAPs, memory, or filesystem metadata.
  • Record clock source, timezone, and any drift or truncation that could reorder events.
  • Link shared identifiers across sources: PID, logon ID, GUID, message ID, hostname, username, IP, or hash.
2. Correlate The Execution Graph
  • Track process tree, service or task creation, network sessions, file writes, registry changes, mailbox rules, or token use as one path.
  • Distinguish causal edges from coincidence by matching identifiers and adjacency, not just nearby timestamps.
  • Keep raw artifact and parsed summary side by side so every step can be traced back.
3. Compress To The Decisive Story
  • Reduce the timeline to the smallest sequence that proves initial access, persistence, lateral movement, collection, or artifact recovery.
  • Call out missing validation steps separately instead of mixing them into confirmed chronology.
  • If the task becomes mainly about malware config extraction or a Windows pivot edge, switch to the tighter specialized skill.

Read This Reference

  • Load references/forensic-timeline.md for anchor selection, cross-source correlation, and evidence packaging.
  • If the hard part is packet reassembly, protocol framing, or transferred-object extraction from a capture, prefer $competition-pcap-protocol.

What To Preserve

  • Source file paths, event IDs, logon IDs, message IDs, PIDs, hashes, and timestamps with timezone noted
  • One compact timeline table or ordered list for the decisive segment
  • Raw artifacts, parsed output, and inferred edges kept separate

Comments

Markdown supported