hunting-persistence-mechanisms-on-windows
Hunts for Windows persistence across autostart locations: Run keys, services,
v1.0.03 installazioni+3 in 7 giorni24 StelleApache-2.0sincronizzato 10 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/hunting-persistence-mechanisms-on-windowsScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto1df430d0…3042aa78
1df430d0a51d…0fed3042aa784 file · 3.3 KBScansioneMedio2 segnalazioni
- Script eseguibile incluso nella skillscripts/analyst.py
- Link a domini esterni
Sorgentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/hunting-persistence-mechanisms-on-windows@da7600a
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
When to Use
- You are hunting for how an adversary maintains a foothold across reboots.
- You have autostart inventories (Autoruns exports, registry/scheduled-task/WMI dumps) from one or many hosts and want to surface anomalies.
- You want to baseline a fleet and flag entries that deviate or were recently added.
Do not use a single host's autoruns list as ground truth — many legitimate entries look unusual; comparison against a fleet baseline is what makes anomalies meaningful.
Prerequisites
- Autostart data per host: Run/RunOnce keys, services, scheduled tasks, WMI event subscriptions, startup folders, and (ideally) signing status.
- A baseline (golden image or fleet majority) to diff against.
Workflow
Step 1: Inventory the ASEPs
Collect the common Autostart Extensibility Points across hosts: Run keys (T1547.001), services (T1543.003), scheduled tasks (T1053.005), and WMI subscriptions (T1546.003).
Step 2: Baseline and diff
Compare each host's entries to the fleet baseline; entries appearing on few hosts, unsigned, or pointing to user-writable/temp paths bubble up.
python scripts/analyst.py hunt autostart.json --baseline baseline.jsonStep 3: Score anomalies
Raise priority for: unsigned binaries, LOLBins launched with encoded args, paths in
%TEMP%/%APPDATA%, recently created tasks, and WMI consumers running scripts.
Step 4: Triage candidates
For each high-score entry, pull the target binary's signing/hash, the creating user/time, and correlate with process and network telemetry.
Step 5: Confirm and respond
Validate suspicious entries (sandbox/RE the binary), escalate confirmed persistence to IR, and turn the pattern into a detection.
Validation
- Anomalies are ranked against a baseline, not flagged from one host in isolation.
- High-score entries map to concrete artifacts (path, hash, signer) for triage.
- Confirmed persistence ties back to a known intrusion timeline.
Pitfalls
- Treating every unsigned entry as malicious; many legitimate tools are unsigned.
- Checking only Run keys and missing services/tasks/WMI subscriptions.
- No timestamps, so you cannot distinguish long-standing from newly planted entries.
References
- See
references/api-reference.mdfor the autostart hunter. - ATT&CK Persistence tactic and Autoruns (linked in frontmatter).
File di questa versione
references/11.2 KB
- api-reference.md1.2 KB
scripts/12.7 KB
- analyst.py2.7 KB
- LICENSE340 B
- SKILL.md3.3 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | Sì | Sì |
| Usa la rete | Sì | Sì |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- MediaFile · Script eseguibile incluso nella skillscripts/analyst.py
- InfoLink · Link a domini esterni
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v1.0.0 | 13 nov 2026 | da7600a | 1df430d0 | Firmata | – |
Altro da meltedinhex
Tutto da questo editore- 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
Altro in Active Directory e Windows
Vai alla categoria- offensive-windows-mitigationssnailsploit/offensive-windows-mitigations4
- active-directory-attack-pathssecurityskills/active-directory-attack-paths3
- analyzing-powershell-script-block-loggingmukul975/analyzing-powershell-script-block-logging3
- offensive-windows-boundariessnailsploit/offensive-windows-boundaries3
- evil-winrmaeondave/evil-winrm3
- bloodyadaeondave/bloodyad3
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login