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
aeondave/dnspyEngenharia reversa e fuzzing

dnspy

⁨Use dnSpyEx to decompile and debug .NET and Unity assemblies on Windows.⁩

v2026.11.13-21cd5683 instalações+3 em 7 dias39 EstrelasMITsincronizado há 11 horas

Instalar

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

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/dnspy

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

AssinaturaAssinado, ed25519
1UJL+vF4He…HxSzazCw==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote85fb6910…0c8a7877
85fb6910278c…59e90c8a78773 arquivos · ⁦7.2 KB⁩
VarreduraMédio5 achados
  • command.base64_execSKILL.md:108
  • command.base64_execSKILL.md:145
  • command.base64_execreferences/deobfuscation.md:138
Ver a varredura completa
Fontegithub.com/AeonDave/malskill/tree/main/offensive-tools/rev/dnspy@21cd568

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

.NET and Unity assembly decompiler, debugger, and editor for Windows.

Installation

text
# Current upstream release: v6.6.0
# Download from https://github.com/dnSpyEx/dnSpy/releases
# Extract and launch dnSpy.exe

# Alternative CLI decompiler (cross-platform)
dotnet tool install --global ilspycmd

The original dnSpy project by 0xd4d is archived; this skill covers the maintained dnSpyEx fork. Check the official releases for updates.

Quick Start

  1. File → Open → select .exe or .dll (.NET assembly)
  2. Assembly Explorer (left panel) → expand namespaces → click class/method
  3. Decompiled C# appears in the main panel
  4. Right-click assembly → Go to Entry Point to start at Main()
  5. To debug: Debug → Start Debugging (F5) or Attach to Process

Key Panels

Panel Purpose
Assembly Explorer Tree view of loaded assemblies, namespaces, types
Decompiler C#/VB.NET/IL decompiled source
Output Debug output and log messages
Locals / Watch Variable inspection during debugging
Call Stack Stack trace during debugging
Breakpoints Manage all breakpoints
Modules Loaded assemblies/modules in debugged process
Key Action
Ctrl+Shift+K Search assemblies (types, methods, strings)
Ctrl+G Go to token/offset
F12 Go to definition
Ctrl+Shift+F Find all references
Ctrl+D Go to metadata token
F5 Start/continue debugging
F9 Toggle breakpoint
F10 Step over
F11 Step into
Shift+F11 Step out

Malware Analysis Workflow

Step 1: Verify .NET and detect obfuscation

Before opening in dnSpy, verify the sample is .NET:

bash
# Check for CLI header in PE
python -c "
import struct, sys
data = open(sys.argv[1], 'rb').read()
lfanew = struct.unpack_from('<I', data, 0x3c)[0]
opt = lfanew + 4 + 20
magic = struct.unpack_from('<H', data, opt)[0]
dd_off = opt + (112 if magic == 0x10b else 128)  # data dir 14 = COM descriptor
rva = struct.unpack_from('<I', data, dd_off)[0]
print('.NET' if rva else 'Native')
" sample.exe

# Detect obfuscator
de4dot --detect sample.exe

Common obfuscators: ConfuserEx, .NET Reactor, SmartAssembly, Dotfuscator, Babel, Eazfuscator

Step 2: Deobfuscate with de4dot

bash
# de4dot: .NET deobfuscator (supports most common protections)
de4dot sample.exe -o sample_clean.exe
# For specific obfuscator:
de4dot --un-name "!^[a-zA-Z]{1,2}$" sample.exe -o sample_clean.exe

Step 3: Static analysis in dnSpy

  1. Open cleaned assembly → Go to Entry Point (Main)
  2. Follow execution flow from Main through initialization
  3. Search for suspicious patterns:

Search targets (Ctrl+Shift+K):

  • WebClient, HttpClient, WebRequest — network communication
  • Process.Start, ProcessStartInfo — command execution
  • Assembly.Load, Assembly.LoadFrom — dynamic code loading
  • GetManifestResourceStream — embedded resource extraction
  • CryptoStream, AesManaged, RijndaelManaged — encryption
  • Convert.FromBase64String — base64 decoding
  • Registry, RegistryKey — persistence via registry
  • DllImport, Marshal.GetDelegateForFunctionPointer — P/Invoke to native
  • Thread, Timer, Task.Run — async/background execution

Step 4: Debug to extract runtime data

  1. Set breakpoint on decryption method or config loading
  2. Debug → Start Debugging (F5)
  3. When breakpoint hits:
    • Locals window shows decrypted values
    • Right-click variable → Add to Watch for complex objects
    • Use Immediate window to evaluate expressions
  4. For encrypted C2: break after decryption, inspect the string variable

Step 5: Edit and patch

text
# Patch a method:
1. Right-click method → Edit Method (C#)
2. Modify code (e.g., add Console.WriteLine for tracing)
3. Compile (Ctrl+Shift+P)
4. File → Save Module → save patched assembly

# Patch IL directly:
1. Right-click method → Edit IL Instructions
2. Modify opcodes
3. OK → Save Module

Key .NET Analysis Patterns

Config extraction

text
# Common patterns for embedded configs:
1. Hardcoded strings in static fields → visible in decompiler
2. Base64 in static constructor (.cctor) → decode with Convert.FromBase64String
3. Encrypted resource → GetManifestResourceStream + AES/XOR decrypt
4. Settings class → Properties.Settings or custom config class
5. Embedded JSON/XML in resources → check Resources node in Assembly Explorer

Stealers (RedLine, Raccoon, etc.)

Focus areas:

  • Credentials or Passwords class — browser credential theft
  • Crypto or Wallet class — cryptocurrency wallet targeting
  • FileGrabber — file exfiltration rules
  • SystemInfo — fingerprinting methods
  • Gate or Panel or Config — C2 URL and build config

RATs (AsyncRAT, QuasarRAT, etc.)

Focus areas:

  • Settings class — C2 IP/port, mutex, install path, encryption key
  • Connection or Client class — C2 protocol implementation
  • Plugin or Commands namespace — available capabilities
  • Install method — persistence mechanism
  • AntiVM or AntiDebug — evasion checks

Loaders and droppers

Focus areas:

  • Main → resource extraction → Assembly.Load (in-memory stage 2)
  • WebClient.DownloadData → Assembly.Load (download + execute)
  • RunPE or Inject method — process hollowing/injection
  • Delay/sleep before payload execution (sandbox evasion)

Resources

File When to load
references/deobfuscation.md Deobfuscation strategies per obfuscator family
references/dotnet-malware-patterns.md Common .NET malware family patterns and IOC locations

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosSimSim
Grava arquivosNãoNão
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édiaComando · command.base64_execSKILL.md:108
  2. MédiaComando · command.base64_execSKILL.md:145
  3. MédiaComando · command.base64_execreferences/deobfuscation.md:138
  4. MédiaComando · command.base64_execreferences/dotnet-malware-patterns.md:132
  5. 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
v2026.11.13-21cd56813 de nov. de 202621cd56885fb6910Assinada–

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