Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
zhaoxuya520/competition-forensic-timelineDFIR y threat hunting

competition-forensic-timeline

⁨Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for DFIR chronology, cross-artifact correlation, persistence chains, and incident timeline reconstruction. Use when the user asks to build a forensic timeline, correlate EVTX, PCAP, registry, disk, memory, mailbox, or brows⁩

v2026.9.22-cab634b3 instalaciones+3 en 7 días44,8 mil EstrellasMITsincronizado hace 2 horas

Instalar

¿Aún no tienes la CLI de NotHoly? Instálala primero.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install zhaoxuya520/competition-forensic-timeline

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
TB/+lQ1+77…LlMVTUDw==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete7fb2083c…8fffb8de
7fb2083c19ec…2ce18fffb8de3 archivos · ⁦2.3 KB⁩
EscaneoBajosin hallazgos
El escaneo no encontró nada que señalar en esta versión.Ver el escaneo completo
Fuentegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-forensic-timeline@cab634b

Esta entrada todavía no está escrita en tu idioma, así que aparece en English.

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

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellNoNo
Usa la redNoNo
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

El escaneo no encontró nada que señalar en esta versión.

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.9.22-cab634b13 nov 2026cab634b7fb2083cFirmada–

Pregunta todo lo que tu alcance permite.

Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.

  1. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login