analyzing-wiper-malware
Analyzes destructive wiper malware by identifying raw-disk and MBR/VBR overwrite
v1.0.02 installs+2 in 7 days24 StarsApache-2.0synced 10 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/analyzing-wiper-malwareWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package03cd645b…f5d36536
03cd645b5d02…22f5f5d365364 files · 3.3 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/analyzing-wiper-malware@da7600a
On this page
When to Use
- You have a sample suspected of destructive intent and need to identify disk-overwrite, MBR/VBR tampering, and mass-deletion primitives.
- You must distinguish a wiper (irreversible destruction) from ransomware (encryption for ransom).
Do not use this on a live host or by running the sample — destructive behavior is the threat. Analyze statically in isolation.
Prerequisites
- The sample, read inertly.
Safety & Handling
- Read bytes statically; never execute. A wiper run is unrecoverable — isolation is mandatory.
Workflow
Step 1: Detect destructive primitives
python scripts/analyst.py scan sample.binFlags raw-disk handles (\\.\PhysicalDrive, \\.\C:), DeviceIoControl, MBR/VBR write patterns,
CreateFileMapping over the boot sector, and bulk DeleteFile/overwrite loops.
Step 2: Detect backup/recovery destruction
Surface vssadmin delete shadows, wbadmin delete, bcdedit /set recoveryenabled no, and
wevtutil cl (log clearing) — common wiper recovery-denial steps.
Step 3: Distinguish wiper vs ransomware
Weigh destruction-without-crypto and absence of a ransom note / key exchange against encryption-and-extortion indicators to classify intent.
Step 4: Document
Record the destruction method (overwrite pattern, MBR vs file-level) and recovery-denial steps.
Validation
- Destructive primitives reference real raw-disk/boot-record APIs, not generic file IO.
- Recovery-denial commands are detected where present.
- The wiper-vs-ransomware classification cites concrete evidence.
Pitfalls
- Disk utilities and secure-erase tools share these primitives — context is essential.
- Pseudo-ransomware wipers that display a note but cannot decrypt (intent is destruction).
- Bootloader-only wipers needing boot-sector analysis (pair with the rootkit/bootkit skill).
References
- See
references/api-reference.mdfor the scanner. - ATT&CK T1561 and T1485 (linked in frontmatter).
Files in this version
references/11.4 KB
- api-reference.md1.4 KB
scripts/13.0 KB
- analyst.py3.0 KB
- LICENSE340 B
- SKILL.md2.8 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| 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
- MediumFile · Executable script shipped with the skillscripts/analyst.py
- 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 |
|---|---|---|---|---|---|
| v1.0.0 | Nov 13, 2026 | da7600a | 03cd645b | Signed | – |
More from meltedinhex
All from this publisher- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
More in Malware and ransomware analysis
See the category- yara-sigsdariushoule/yara-sigs4
- monitoring-darkweb-sourcesmukul975/monitoring-darkweb-sources3
- deploying-ransomware-canary-filesmukul975/deploying-ransomware-canary-files3
- implementing-honeypot-for-ransomware-detectionmukul975/implementing-honeypot-for-ransomware-detection3
- yaraaeondave/yara3
- testing-ransomware-recovery-proceduresmukul975/testing-ransomware-recovery-procedures3
Ask 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