agentsclimarketplace
Sign in

Analyzing wiper malware

Skill meltedinhex/analyst-ai-pack/skills/analyzing-wiper-malware

Analyzes destructive wiper malware by identifying raw-disk and MBR/VBR overwrite primitives, boot-record tampering, mass-deletion and backup-destruction behavior, and distinguishing wipers from ransomware. Activates for requests to analyze a wiper, identify destructive disk-overwrite behavior, or tell a wiper apart from ransomware.From its SKILL.md

Install
npx -y skills add meltedinhex/analyst-ai-pack --skill analyzing-wiper-malware

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 21 stars21 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.8 KB, 472 tokens by cl100k_base, as published. Nobody here has run it

Analyzing Wiper Malware

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.bin

Flags 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

What ships with it: 3 files

4.7 KB alongside SKILL.md, 1 of them executable

references/

scripts/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.