defense-malware-triage
Safely triage a suspicious file or process — is it malicious, what does it do, and what IOCs does it yield — with static then dynamic analysis. Load for "is this file malware", "analyze this binary/script/document", "suspicious process on a host", or extracting IOCs for hunting/detection.
v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/defense-malware-triageWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package03793900…59d4001d
03793900ed58…23c959d4001d1 file · 1.6 KBScanLowno findings
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/defense/defense-malware-triage@ee0e0c5
On this page
When it applies
You have a sample (a dropped binary, a macro-laden document, a suspicious script) or a live process and need a fast verdict plus IOCs — not full reverse engineering, but enough to decide and to feed detection/IR.
Why it works
Most samples reveal their nature cheaply: capabilities, embedded strings, and behaviour appear long before you need a disassembler. Triage front-loads the cheap signals and only escalates to deep RE when the verdict is still unclear — so you get IOCs fast without burning hours per file.
Method
- Handle safely: work in an isolated VM/network, never on a production host. Treat the sample as live; don't double-click to "see what it does" outside a sandbox.
- Identify: hashes, file type (magic bytes, not extension), and a reputation check by hash (not by uploading the file if it may be sensitive/targeted).
- Static, no execution:
capafor capabilities (persistence, injection, C2),FLOSS/strings for URLs, IPs, mutexes, registry keys; for Office/PDF, extract and de-obfuscate the macro/JS (olevba, CyberChef). PE: imports, sections, signing, compile time (pestudio). - Dynamic, if needed: detonate in a sandbox; capture process tree, file/registry writes, network. This confirms behaviour static analysis only hinted at.
- Extract IOCs & a rule: host IOCs (paths, mutexes, keys) and network IOCs (C2 domains/IPs); write a YARA rule on stable internals (not a rotating hash) for hunting.
- Feed the pipeline: hand behavioural IOCs to
defense-threat-huntingand turn stable ones into a detection; if it's live on a host, escalate todefense-incident-response. Deep dive →reverse-eng-*.
Gotchas
- Uploading a targeted sample to a public multiscanner can tip off the adversary — hash-check first.
- Malware detects sandboxes (sleeps, VM checks) and stays dormant — a clean dynamic run isn't clearance; weigh the static capabilities too.
- Hash-based rules rot instantly; write YARA on code/string internals that survive rebuilds.
Verify success
You have a supported verdict (malicious/suspicious/benign), a capability summary, host + network IOCs, and a YARA/detection rule — enough to hunt for other affected hosts.
References
Mandiant/FLARE capa & FLOSS; YARA; pestudio; olevba (oletools); MITRE ATT&CK.
Files in this version
- SKILL.md2.8 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
The scan found nothing to flag in this version.
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.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | 03793900 | Signed | – |
More from NoorQureshi
All from this publisherMore in Malware and ransomware analysis
See the category- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- 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
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