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/dnspyGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacote85fb6910…0c8a7877
85fb6910278c…59e90c8a78773 arquivos · 7.2 KBVarreduraMédio5 achados
- command.base64_execSKILL.md:108
- command.base64_execSKILL.md:145
- command.base64_execreferences/deobfuscation.md:138
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.
Nesta página
.NET and Unity assembly decompiler, debugger, and editor for Windows.
Installation
# 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 ilspycmdThe original dnSpy project by 0xd4d is archived; this skill covers the maintained dnSpyEx fork. Check the official releases for updates.
Quick Start
- File → Open → select
.exeor.dll(.NET assembly) - Assembly Explorer (left panel) → expand namespaces → click class/method
- Decompiled C# appears in the main panel
- Right-click assembly → Go to Entry Point to start at
Main() - 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 |
Navigation Shortcuts
| 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:
# 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.exeCommon obfuscators: ConfuserEx, .NET Reactor, SmartAssembly, Dotfuscator, Babel, Eazfuscator
Step 2: Deobfuscate with de4dot
# 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.exeStep 3: Static analysis in dnSpy
- Open cleaned assembly → Go to Entry Point (
Main) - Follow execution flow from
Mainthrough initialization - Search for suspicious patterns:
Search targets (Ctrl+Shift+K):
WebClient,HttpClient,WebRequest— network communicationProcess.Start,ProcessStartInfo— command executionAssembly.Load,Assembly.LoadFrom— dynamic code loadingGetManifestResourceStream— embedded resource extractionCryptoStream,AesManaged,RijndaelManaged— encryptionConvert.FromBase64String— base64 decodingRegistry,RegistryKey— persistence via registryDllImport,Marshal.GetDelegateForFunctionPointer— P/Invoke to nativeThread,Timer,Task.Run— async/background execution
Step 4: Debug to extract runtime data
- Set breakpoint on decryption method or config loading
- Debug → Start Debugging (F5)
- When breakpoint hits:
- Locals window shows decrypted values
- Right-click variable → Add to Watch for complex objects
- Use Immediate window to evaluate expressions
- For encrypted C2: break after decryption, inspect the string variable
Step 5: Edit and patch
# 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 ModuleKey .NET Analysis Patterns
Config extraction
# 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 ExplorerStealers (RedLine, Raccoon, etc.)
Focus areas:
CredentialsorPasswordsclass — browser credential theftCryptoorWalletclass — cryptocurrency wallet targetingFileGrabber— file exfiltration rulesSystemInfo— fingerprinting methodsGateorPanelorConfig— C2 URL and build config
RATs (AsyncRAT, QuasarRAT, etc.)
Focus areas:
Settingsclass — C2 IP/port, mutex, install path, encryption keyConnectionorClientclass — C2 protocol implementationPluginorCommandsnamespace — available capabilitiesInstallmethod — persistence mechanismAntiVMorAntiDebug— evasion checks
Loaders and droppers
Focus areas:
Main→ resource extraction →Assembly.Load(in-memory stage 2)WebClient.DownloadData→Assembly.Load(download + execute)RunPEorInjectmethod — 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
references/211.4 KB
- deobfuscation.md5.5 KB
- dotnet-malware-patterns.md6.0 KB
- SKILL.md6.0 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Sim | Sim |
| Grava arquivos | Não | Não |
| Roda comandos no shell | Sim | Sim |
| Usa a rede | Sim | Sim |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
- MédiaComando · command.base64_execSKILL.md:108
- MédiaComando · command.base64_execSKILL.md:145
- MédiaComando · command.base64_execreferences/deobfuscation.md:138
- MédiaComando · command.base64_execreferences/dotnet-malware-patterns.md:132
- 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ão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | 13 de nov. de 2026 | 21cd568 | 85fb6910 | Assinada | – |
Mais de AeonDave
Tudo deste publicadorMais em Engenharia reversa e fuzzing
Ver a categoriaPergunte 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/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login