hunting-suspicious-powershell-execution
Hunts malicious PowerShell using script-block (EID 4104) and module logging:
v1.0.03 instalaciones+3 en 7 días24 EstrellasApache-2.0sincronizado hace 10 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/hunting-suspicious-powershell-executionEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquete5c2a893c…63805edb
5c2a893c02b6…b76563805edb4 archivos · 3.4 KBEscaneoMedio7 hallazgos
- command.pipe_to_shellSKILL.md:57
- command.base64_execSKILL.md:58
- command.pipe_to_shellSKILL.md:87
Fuentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/hunting-suspicious-powershell-execution@da7600a
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
When to Use
- You have PowerShell script-block (Event ID 4104) and/or module logging and want to hunt abuse.
- You are testing a hypothesis that attackers use encoded commands, download cradles, or AMSI/logging bypasses.
- You need to score and decode a large volume of PowerShell events into a triage queue.
Do not use simple keyword blocklists as the sole method — admins legitimately use many of the same cmdlets; score combinations and decode before judging.
Prerequisites
- Script-block logging enabled (Event ID 4104) and exported to a queryable store.
- A baseline of normal administrative PowerShell for your environment.
Workflow
Step 1: Collect script-block events
Pull EID 4104 script-block text (and EID 4103 module logging) over the hunt window. Reassemble multi-part script blocks before analysis.
Step 2: Score suspicious constructs
Weight combinations rather than single keywords: -EncodedCommand, IEX/Invoke-Expression
with Net.WebClient/Invoke-WebRequest, FromBase64String, -w hidden -nop, AMSI strings,
and [Ref].Assembly reflection.
python scripts/analyst.py score events.jsonStep 3: Decode payloads
Base64-decode -EncodedCommand (UTF-16LE) and recover layered encodings to read the real
intent (download URLs, in-memory loaders).
Step 4: Baseline and pivot
Compare against normal admin activity; for survivors, pull the parent process, user, host, and network connections to confirm.
Step 5: Confirm and operationalize
Validate true positives, escalate to IR, and convert the scoring logic into a detection rule.
Validation
- High-score events decode to coherent malicious intent, not benign admin scripts.
- Multi-part script blocks are reassembled before scoring (no truncated false negatives).
- Confirmed cases tie to a parent process and user consistent with intrusion.
Pitfalls
- Flagging single keywords (
IEXalone) and drowning in admin noise. - Forgetting
-EncodedCommandis UTF-16LE, producing garbled decodes. - Ignoring AMSI/logging-bypass attempts that precede the real payload.
References
- See
references/api-reference.mdfor the scorer/decoder. - Script-block logging docs and ATT&CK T1059.001 (linked in frontmatter).
Archivos de esta versión
references/11.3 KB
- api-reference.md1.3 KB
scripts/13.1 KB
- analyst.py3.1 KB
- LICENSE340 B
- SKILL.md3.2 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | Sí | Sí |
| Usa la red | Sí | Sí |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
- MediaComando · command.pipe_to_shellSKILL.md:57
- MediaComando · command.base64_execSKILL.md:58
- MediaComando · command.pipe_to_shellSKILL.md:87
- MediaArchivo · Script ejecutable incluido con la skillscripts/analyst.py
- MediaComando · command.base64_execscripts/analyst.py:20
- MediaComando · command.pipe_to_shellscripts/analyst.py:21
- InfoEnlace · Enlaces a dominios externos
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v1.0.0 | 13 nov 2026 | da7600a | 5c2a893c | Firmada | – |
Más de meltedinhex
Todo de este publicador- 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
Más en DFIR y threat hunting
Ver la categoría- 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
Pregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login