Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
zhaoxuya520/competition-forensic-timelineDFIR e 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 instalações+3 em 7 dias44,8 mil EstrelasMITsincronizado há 2 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

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

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
TB/+lQ1+77…LlMVTUDw==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote7fb2083c…8fffb8de
7fb2083c19ec…2ce18fffb8de3 arquivos · ⁦2.3 KB⁩
VarreduraBaixonenhum achado
A varredura não encontrou nada para apontar nesta versão.Ver a varredura completa
Fontegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-forensic-timeline@cab634b

Este item ainda não foi escrito no seu idioma, então aparece em 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

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosNãoNão
Roda comandos no shellNãoNão
Usa a redeNãoNão
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

A varredura não encontrou nada para apontar nesta versão.

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.9.22-cab634b13 de nov. de 2026cab634b7fb2083cAssinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login