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

writing-a-malware-analysis-report

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

v1.0.03 instalaciones+3 en 7 días24 EstrellasApache-2.0sincronizado hace 10 horas

Instalar

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

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

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

FirmaFirmado, ed25519
b2w/CuHjii…h5nu8kBQ==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete6c833d52…895c449d
6c833d52187f…d270895c449d4 archivos · ⁦3.9 KB⁩
EscaneoMedio2 hallazgos
  • Script ejecutable incluido con la skillscripts/analyst.py
  • Enlaces a dominios externos
Ver el escaneo completo
Fuentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/writing-a-malware-analysis-report@da7600a

Esta entrada todavía no está escrita en tu idioma, así que aparece en 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).

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosSíSí
Ejecuta comandos de shellSíSí
Usa la redSíSí
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

  1. MediaArchivo · Script ejecutable incluido con la skillscripts/analyst.py
  2. InfoEnlace · Enlaces a dominios externos

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

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v1.0.013 nov 2026da7600a6c833d52Firmada–

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