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
meltedinhex/writing-a-malware-analysis-reportAnálise de malware e ransomware

writing-a-malware-analysis-report

⁨Structures a clear, actionable malware analysis report covering summary,⁩

v1.0.03 instalações+3 em 7 dias24 EstrelasApache-2.0sincronizado há 10 horas

Instalar

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

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/writing-a-malware-analysis-report

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

AssinaturaAssinado, ed25519
b2w/CuHjii…h5nu8kBQ==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote6c833d52…895c449d
6c833d52187f…d270895c449d4 arquivos · ⁦3.9 KB⁩
VarreduraMédio2 achados
  • Script executável junto com a skillscripts/analyst.py
  • Links para domínios externos
Ver a varredura completa
Fontegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/writing-a-malware-analysis-report@da7600a

Este item ainda não foi escrito no seu idioma, então aparece em English.

When to Use

  • You have completed static, dynamic, or reverse-engineering analysis and need to communicate findings to responders, detection engineers, and leadership.
  • You need a consistent report structure so findings are actionable and comparable across samples.
  • You are reviewing a draft report for completeness before distribution.

Do not use this as a substitute for analysis; a report only documents work already done. Do not pad a report with tool output that has no analytic conclusion.

Prerequisites

  • Completed analysis artifacts: sample hashes, behavioral notes, extracted IOCs, screenshots, and any reversed routines.
  • An ATT&CK reference for mapping observed behaviors to techniques.

Workflow

Step 1: Lead with an executive summary

Three to five sentences a non-analyst can act on: what the sample is, what it does, the risk, and the recommended action. State your confidence and the basis for it.

Step 2: Record sample identity

A table the reader can match against their telemetry:

text
Filename (as received) : invoice.exe
SHA-256                : 9f86d0818...
SHA-1 / MD5            : ...
File type / size        : PE32 executable / 412 KB
First seen / source     : 2026-06-20 / MalwareBazaar
Signing                 : unsigned / invalid certificate

Step 3: Describe capabilities, not just events

Group findings by capability (persistence, C2, defense evasion, collection), each with the evidence and the ATT&CK technique:

text
Persistence  : Run key HKCU\...\Run "Updater" -> %APPDATA%\svc.exe   [T1547.001]
C2           : HTTPS beacon to evil[.]com/api every 60s +/- jitter   [T1071.001]
Defense evasion: UPX-packed; checks for VM artifacts before running  [T1027, T1497]

Step 4: Provide IOCs in a usable form

Defanged for reading, plus a machine-ingestible block (CSV/STIX/MISP) for detection teams. Separate host IOCs (paths, registry keys, mutexes) from network IOCs (domains, IPs, URLs, JA3).

Step 5: Give detection and response guidance

Concrete next steps: YARA/Sigma rules, what to hunt for, containment, and remediation.

Step 6: Generate the skeleton and validate completeness

bash
python scripts/analyst.py scaffold --sha256 <sha256> --name "Sample" > report.md
python scripts/analyst.py check report.md

Validation

  • An incident responder can act on the report without reading the raw tool logs.
  • Every capability claim cites specific evidence (offset, registry key, packet, decompiled routine).
  • IOCs appear both defanged (for humans) and in a structured block (for tools).
  • ATT&CK techniques are valid current IDs and tied to observed behavior, not guessed.

Pitfalls

  • Dumping raw tool output without interpretation — the reader needs conclusions.
  • Overclaiming attribution ("this is APT-X") from weak signals; state confidence and evidence instead.
  • Mixing host and network IOCs, or leaving IOCs clickable in the human-readable section.
  • Mapping to ATT&CK techniques that the evidence does not actually support.

References

  • See references/api-reference.md for the scaffold and completeness-check tooling.
  • MITRE ATT&CK and MISP/STIX IOC formats (linked in frontmatter).

Arquivos desta versão

Permissões

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

Achados da varredura

Revisado em 13 de nov. de 2026

  1. MédiaArquivo · Script executável junto com a skillscripts/analyst.py
  2. InfoLink · Links para domínios externos

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
v1.0.013 de nov. de 2026da7600a6c833d52Assinada–

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