hunting-fileless-and-in-memory-threats
Hunts for fileless and in-memory threats by correlating PowerShell script-block logs,
v1.0.02 installs+2 in 7 days24 StarsApache-2.0synced 11 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/hunting-fileless-and-in-memory-threatsWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Packagead266eff…c703e733
ad266eff5f2c…149dc703e7334 files · 3.2 KBScanMedium10 findings
- command.pipe_to_shellSKILL.md:56
- command.pipe_to_shellSKILL.md:79
- command.pipe_to_shellreferences/api-reference.md:22
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/hunting-fileless-and-in-memory-threats@da7600a
On this page
When to Use
- You have PowerShell script-block logs (4104), process telemetry, and registry-write events and want to detect fileless execution that leaves little on disk.
- You are hunting reflective loading, in-memory .NET execution, and registry-resident payloads.
Do not use this to alert on all PowerShell use — hunt the in-memory loading and encoded-payload patterns specifically.
Prerequisites
- 4104 script-block logs and/or process and registry telemetry (CSV/JSON).
Workflow
Step 1: Hunt in-memory loading patterns
python scripts/analyst.py hunt events.csvFlags [Reflection.Assembly]::Load, VirtualAlloc/WriteProcessMemory via PowerShell,
Invoke-Expression of decoded blobs, DownloadString+IEX, and large base64 in script blocks.
Step 2: Detect registry-resident payloads
Surface writes of large encoded blobs to HKCU\Software\... Run-adjacent or custom keys (fileless
storage).
Step 3: Confirm
Correlate script-block content with the parent process and subsequent network/child activity.
Step 4: Operationalize
Write detections for reflective loading and base64-heavy script blocks.
Validation
- Flags are based on in-memory loading/encoded-payload patterns, not PowerShell presence.
- Registry-resident payload detection keys on large encoded values.
- Findings map to ATT&CK T1620/T1059.001/T1112.
Pitfalls
- Legitimate admin scripts using
Invoke-Expression— corroborate with content/parent. - Obfuscated script blocks splitting indicators across logs.
- Constrained Language Mode evasions changing the observable API surface.
References
- See
references/api-reference.mdfor the hunter. - ATT&CK T1620 and script-block logging docs (linked in frontmatter).
Files in this version
references/11.4 KB
- api-reference.md1.4 KB
scripts/13.1 KB
- analyst.py3.1 KB
- LICENSE340 B
- SKILL.md2.7 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
- MediumCommand · command.pipe_to_shellSKILL.md:56
- MediumCommand · command.pipe_to_shellSKILL.md:79
- MediumCommand · command.pipe_to_shellreferences/api-reference.md:22
- MediumCommand · command.pipe_to_shellreferences/api-reference.md:23
- MediumCommand · command.base64_execreferences/api-reference.md:23
- MediumFile · Executable script shipped with the skillscripts/analyst.py
- MediumCommand · command.pipe_to_shellscripts/analyst.py:5
- MediumCommand · command.pipe_to_shellscripts/analyst.py:20
- MediumCommand · command.base64_execscripts/analyst.py:20
- 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 | ad266eff | 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 DFIR and threat hunting
See the category- hunting-for-command-and-control-beaconingmukul975/hunting-for-command-and-control-beaconing5
- audit-context-buildingtrailofbits/audit-context-building4
- incident-response-forensicssecurityskills/incident-response-forensics3
- extracting-credentials-from-memory-dumpmukul975/extracting-credentials-from-memory-dump3
- analyzing-browser-forensics-with-hindsightmukul975/analyzing-browser-forensics-with-hindsight3
- forensics-ctfaeondave/forensics-ctf3
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