analyzing-wiper-malware
Analyzes destructive wiper malware by identifying raw-disk and MBR/VBR overwrite
v1.0.02 installazioni+2 in 7 giorni24 StelleApache-2.0sincronizzato 10 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/analyzing-wiper-malwareScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto03cd645b…f5d36536
03cd645b5d02…22f5f5d365364 file · 3.3 KBScansioneMedio2 segnalazioni
- Script eseguibile incluso nella skillscripts/analyst.py
- Link a domini esterni
Sorgentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/analyzing-wiper-malware@da7600a
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
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).
File di questa versione
references/11.4 KB
- api-reference.md1.4 KB
scripts/13.0 KB
- analyst.py3.0 KB
- LICENSE340 B
- SKILL.md2.8 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | Sì | Sì |
| Usa la rete | Sì | Sì |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- MediaFile · Script eseguibile incluso nella skillscripts/analyst.py
- InfoLink · Link a domini esterni
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v1.0.0 | 13 nov 2026 | da7600a | 03cd645b | Firmata | – |
Altro da meltedinhex
Tutto da questo editore- 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
Altro in Analisi di malware e ransomware
Vai alla categoria- 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
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login