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

analyzing-ransomware-encryption-behavior

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

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

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

AssinaturaAssinado, ed25519
EsRMiOM4gi…GrQk8hAQ==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacotec7aa0b89…54144625
c7aa0b896431…ff91541446254 arquivos · ⁦3.7 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/analyzing-ransomware-encryption-behavior@da7600a

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

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 2026da7600ac7aa0b89Assinada–

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