dnspy
Use dnSpyEx to decompile and debug .NET and Unity assemblies on Windows.
v2026.11.13-21cd5683 installs+3 in 7 days39 StarsMITsynced 11 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/dnspyWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package85fb6910…0c8a7877
85fb6910278c…59e90c8a78773 files · 7.2 KBScanMedium5 findings
- command.base64_execSKILL.md:108
- command.base64_execSKILL.md:145
- command.base64_execreferences/deobfuscation.md:138
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/rev/dnspy@21cd568
On this page
.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 |
Files in this version
references/211.4 KB
- deobfuscation.md5.5 KB
- dotnet-malware-patterns.md6.0 KB
- SKILL.md6.0 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | Yes | Yes |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumCommand · command.base64_execSKILL.md:108
- MediumCommand · command.base64_execSKILL.md:145
- MediumCommand · command.base64_execreferences/deobfuscation.md:138
- MediumCommand · command.base64_execreferences/dotnet-malware-patterns.md:132
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | Nov 13, 2026 | 21cd568 | 85fb6910 | Signed | – |
More from AeonDave
All from this publisherMore in Reverse engineering and fuzzing
See the categoryAsk anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login