malware-triage
Safely triage unknown malware samples — static indicators, sandbox execution, behavior extraction, and reporting. Use when analyzing suspicious files during investigations.
v2026.8.26-b2b6b522 installs+2 in 7 days0 Starssynced 19 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install securityskills/malware-triageWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Packagec8a65e5a…274d6bb5
c8a65e5a91af…db48274d6bb51 file · 1.2 KBScanMedium1 finding
- No license found
Sourcegithub.com/securityskills/skills/tree/main/malware-analysis/malware-triage@b2b6b52
On this page
Analyze suspicious samples safely and extract actionable indicators fast.
Safety First
- Isolated VM or dedicated sandbox (Cuckoo/ANY.RUN/vendor sandbox), network simulated or sinkholed
- Samples stored in password-protected archives, hash-named; never opened on analysis-adjacent hosts
- Work from snapshots; revert after every detonation
1. Static Triage
- Hashes (MD5/SHA256), file type, entropy (
file,pestudio-style overview) - Strings: URLs, mutexes, registry paths, PDB paths, C2 patterns
- PE specifics: imports of interest (network, process injection, crypto APIs), digital signature validity, packer detection (entropy + section names)
- Document metadata (Office macros, embedded objects, remote templates)
2. Dynamic Detonation
- Execute in sandbox with monitoring: file, registry, network, process activity
- Capture: dropped files, persistence mechanism, C2 beacons (domains/IPs with ports/protocols)
- Trigger-dependent malware: require user interaction simulation, geo/fate checks, or debugger awareness — escalate to debugging if silent
3. Behavior Extraction
- Persistence: Run keys, services, scheduled tasks, WMI subscriptions
- Injection: process hollowing, APC, SetWindowsHookEx targets
- Exfiltration: DNS tunneling patterns, HTTP POST shapes, known protocol beacons
- Defense evasion: AV service stops, AMSI/ETW patching, timestamp manipulation
4. Classification and Reporting
- Family attribution via YARA rules against sample set; note confidence
- Map observed behavior to ATT&CK techniques
- Produce: IOCs (machine-readable, STIX if required), detection guidance (YARA + behavioral), and a one-page triage summary
Escalation Criteria
Deep-dive reversing (IDA/Ghidra) only when: C2 protocol reconstruction, config extraction, or unpacking is required for detection/response — not for curiosity.
Files in this version
- SKILL.md2.0 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
- MediumLicense · No license found
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.8.26-b2b6b52 | Nov 13, 2026 | b2b6b52 | c8a65e5a | Signed | – |
More from securityskills
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