Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
mukul975/hunting-for-persistence-mechanisms-in-windowsActive Directory e Windows

hunting-for-persistence-mechanisms-in-windows

⁨Systematically hunts for adversary persistence mechanisms across Windows⁩

v1.03 instalações+3 em 7 dias36,3 mil EstrelasApache-2.0sincronizado há 11 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install mukul975/hunting-for-persistence-mechanisms-in-windows

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
r3P+vtaDuC…MDJL+yDg==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote6d5bf4b6…35bc7d27
6d5bf4b6b1bb…0f1535bc7d278 arquivos · ⁦14.1 KB⁩
VarreduraMédio5 achados
  • Script executável junto com a skillscripts/agent.py
  • command.pipe_to_shellscripts/agent.py:30
  • Script executável junto com a skillscripts/process.py
Ver a varredura completa
Fontegithub.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/hunting-for-persistence-mechanisms-in-windows@54a7988

Este item ainda não foi escrito no seu idioma, então aparece em English.

When to Use

  • During periodic proactive threat hunts for dormant backdoors
  • After an incident to identify all persistence mechanisms an attacker planted
  • When investigating unusual services, scheduled tasks, or startup entries
  • When threat intel reports describe new persistence techniques in the wild
  • During security posture assessments to identify unauthorized persistent software

Prerequisites

  • Sysmon deployed with Event IDs 12/13/14 (Registry), 19/20/21 (WMI), 1 (Process Creation)
  • Windows Security Event forwarding for 4697 (Service Install), 4698 (Scheduled Task)
  • EDR with registry and file monitoring capabilities
  • PowerShell script block logging enabled (Event ID 4104)
  • Autoruns or equivalent baseline of legitimate persistent entries

Workflow

  1. Enumerate Known Persistence Locations: Build a comprehensive list of Windows persistence points (Run keys, services, scheduled tasks, WMI, startup folder, DLL search order, COM hijacks, AppInit DLLs, Image File Execution Options).
  2. Collect Endpoint Data: Use EDR, Sysmon, or Velociraptor to collect current persistence artifacts from endpoints across the environment.
  3. Baseline Legitimate Persistence: Compare collected data against known-good baselines (Autoruns snapshots, GPO-deployed entries, SCCM configurations).
  4. Identify Anomalies: Flag new, unsigned, or unknown entries in persistence locations that deviate from the baseline.
  5. Investigate Suspicious Entries: For each anomaly, examine the binary it points to, its digital signature, file hash, and creation timestamp.
  6. Correlate with Process Activity: Link persistence entries to process execution, network activity, and user login events.
  7. Document and Remediate: Record findings, remove malicious persistence, and update detection rules.

Key Concepts

Concept Description
T1547.001 Registry Run Keys / Startup Folder
T1543.003 Windows Service (Create or Modify)
T1053.005 Scheduled Task
T1546.003 WMI Event Subscription
T1546.015 Component Object Model (COM) Hijacking
T1546.012 Image File Execution Options Injection
T1546.010 AppInit DLLs
T1547.004 Winlogon Helper DLL
T1547.005 Security Support Provider
T1574.001 DLL Search Order Hijacking
TA0003 Persistence Tactic
Autoruns Sysinternals tool showing persistent entries

Tools & Systems

Tool Purpose
Sysinternals Autoruns Comprehensive persistence enumeration
Velociraptor Endpoint-wide persistence artifact collection
CrowdStrike Falcon Real-time persistence monitoring
Sysmon Registry and WMI event monitoring
OSQuery SQL-based persistence queries
RECmd Registry Explorer for forensic analysis
Splunk SIEM correlation of persistence events

Common Scenarios

  1. Registry Run Key Backdoor: Malware adds HKCU\Software\Microsoft\Windows\CurrentVersion\Run entry pointing to payload in %APPDATA%.
  2. WMI Event Subscription: Adversary creates WMI consumer/filter pair that executes PowerShell on system boot.
  3. Malicious Service: Attacker creates Windows service with sc create pointing to a backdoor binary.
  4. COM Object Hijack: Legitimate COM CLSID InprocServer32 path replaced with malicious DLL.
  5. IFEO Debugger Injection: Image File Execution Options key set with debugger pointing to implant for common utilities.

Output Format

text
Hunt ID: TH-PERSIST-[DATE]-[SEQ]
Persistence Type: [Registry/Service/Task/WMI/COM/Other]
MITRE Technique: T1547.xxx / T1543.xxx / T1053.xxx
Location: [Full registry key / service name / task path]
Value: [Binary path / command line]
Host(s): [Affected endpoints]
Signed: [Yes/No]
Hash: [SHA256]
Creation Time: [Timestamp]
Risk Level: [Critical/High/Medium/Low]
Verdict: [Malicious/Suspicious/Benign]

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosSimSim
Roda comandos no shellSimSim
Usa a redeSimSim
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

  1. MédiaArquivo · Script executável junto com a skillscripts/agent.py
  2. MédiaComando · command.pipe_to_shellscripts/agent.py:30
  3. MédiaArquivo · Script executável junto com a skillscripts/process.py
  4. MédiaComando · command.pipe_to_shellscripts/process.py:309
  5. InfoLink · Links para domínios externos

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v1.013 de nov. de 202654a79886d5bf4b6Assinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login