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/analyzing-ransomware-encryption-behaviorAnálisis de malware y ransomware

analyzing-ransomware-encryption-behavior

⁨Analyzes how a ransomware sample encrypts files: identifying the crypto scheme⁩

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/analyzing-ransomware-encryption-behavior

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

FirmaFirmado, ed25519
EsRMiOM4gi…GrQk8hAQ==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquetec7aa0b89…54144625
c7aa0b896431…ff91541446254 archivos · ⁦3.7 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/analyzing-ransomware-encryption-behavior@da7600a

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

When to Use

  • You need to understand how a ransomware sample encrypts data and whether recovery without the key is feasible.
  • You are documenting file targeting, markers, and the ransom workflow for an IR report.
  • You want to identify the crypto primitives to assess decryptability and detection points.

Do not use this to attempt key recovery on production data without backups; analyze in the lab on disposable test files only.

Prerequisites

  • Isolated lab with disposable test files of varied types/sizes.
  • Static/RE tools (see the Ghidra and crypto-identification skills) and the dynamic-analysis setup.
  • A clean snapshot to revert.

Safety & Handling

  • Detonate only against throwaway files in the isolated victim VM; never real data.
  • Treat the sample and any dropped components as live; revert after each run.

Workflow

Step 1: Identify the crypto scheme statically

Locate crypto constants and APIs to classify the scheme:

text
Symmetric only (AES/ChaCha/RC4)  -> key may be derivable/recoverable if mishandled
Asymmetric (RSA/ECC) wrapping    -> per-file symmetric key wrapped with attacker pubkey
Hybrid (typical)                 -> AES per file, RSA-wrapped key in the encrypted file/footer

Look for AES S-boxes, ChaCha constants ("expand 32-byte k"), and CryptImportKey/BCrypt*.

Step 2: Trace key generation and handling

Determine where the symmetric key comes from (CSPRNG vs weak source), whether it is stored, and how it is protected. Weak/reused keys or keys left in memory are recovery opportunities.

Step 3: Map file targeting

Identify which directories/extensions are targeted or skipped (allowlist of system paths), size thresholds, and partial-vs-full encryption (many encrypt only the first N bytes/blocks for speed).

Step 4: Capture markers and metadata

Most families append an extension, write a per-file footer/magic marker, and store the wrapped key or IV there. The script fingerprints before/after test files to extract markers.

bash
python scripts/analyst.py compare plain/ encrypted/

Step 5: Document recovery-relevant facts

Note shadow-copy/backup deletion (vssadmin delete shadows), the ransom note, and any cryptographic mistakes that affect decryptability.

Validation

  • The identified scheme matches observed file changes (e.g. hybrid → high-entropy body + a fixed-size footer).
  • File markers/extensions are consistent across encrypted test files.
  • Shadow-copy deletion and note-drop are confirmed dynamically.

Pitfalls

  • Assuming decryptability from the algorithm name; correct AES/RSA usage is not recoverable. Recovery hinges on implementation flaws or leaked keys.
  • Missing partial-encryption schemes, leading to wrong impact assessment.
  • Running against real files instead of disposable test data.

References

  • See references/api-reference.md for the file-marker comparison tool.
  • No More Ransom and NIST crypto standards (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 2026da7600ac7aa0b89Firmada–

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