[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71G6MP4KA1Y94P64HXMN46P":3,"skill-same:01M71G6MP4KA1Y94P64HXMN46P":97},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":70,"commitSha":71,"skillDirectory":72,"forksCount":14,"repositoryHtmlUrl":73,"repositoryHomepageUrl":6,"ownerHtmlUrl":74,"ownerBlogUrl":6,"ownerDescription":75,"updatedAt":76,"install":77,"resources":90},"01M71G6MP4KA1Y94P64HXMN46P","hunting-suspicious-detect",null,"Detect suspicious PowerShell execution patterns including encoded commands, download cradles, AMSI bypass attempts, and constrained language mode evasion.","DCx7C5\u002Fai-marketplace","DCx7C5","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42419559?v=4","01M71C01G2AZV3NTNGWAWSHJPP","DC","01M71C01GQW6G50S2BYMS7PP3E",0,"MIT","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fsoc\u002Fhunting\u002Fsuspicious\u002Fdetect\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"hunting","hunting suspicious detect","detect","suspicious","patterns","evasion","commands","threat-hunting","read","de","mitre-attack","conversion","analysis","Bash","cybersecurity","content analysis","mode","cm","powershell","T1059.001","2026-11-10 10:12:30",false,"---\nname: hunting-suspicious-detect\ndescription: Detect suspicious PowerShell execution patterns including encoded commands, download cradles, AMSI bypass attempts, and constrained language mode evasion.\ndomain: cybersecurity\nsubdomain: threat-hunting\ntags:\n- threat-hunting\n- mitre-attack\n- powershell\n- execution\n- t1059\n- amsi\n- proactive-detection\nd3fend_techniques:\n- Executable Denylisting\n- Execution Isolation\n- File Metadata Consistency Validation\n- Content Format Conversion\n- File Content Analysis\nnist_csf:\n- DE.CM-01\n- DE.AE-02\n- DE.AE-07\n- ID.RA-05\nmodel: sonnet\nmaxTurns: 20\ntools: [Read, Bash, Glob, Grep]\nmitre_attack:\n- T1059\n- T1059.001\n- T1070\ncapec: []\n---\n\n# Detecting Suspicious Powershell Execution\n\n## When to Use\n\n- When proactively hunting for indicators of detecting suspicious powershell execution in the environment\n- After threat intelligence indicates active campaigns using these techniques\n- During incident response to scope compromise related to these techniques\n- When EDR or SIEM alerts trigger on related indicators\n- During periodic security assessments and purple team exercises\n\n## Prerequisites\n\n- EDR platform with process and network telemetry (CrowdStrike, MDE, SentinelOne)\n- SIEM with relevant log data ingested (Splunk, Elastic, Sentinel)\n- Sysmon deployed with comprehensive configuration\n- Windows Security Event Log forwarding enabled\n- Threat intelligence feeds for IOC correlation\n\n## Workflow\n\n1. **Formulate Hypothesis**: Define a testable hypothesis based on threat intelligence or ATT&CK gap analysis.\n2. **Identify Data Sources**: Determine which logs and telemetry are needed to validate or refute the hypothesis.\n3. **Execute Queries**: Run detection queries against SIEM and EDR platforms to collect relevant events.\n4. **Analyze Results**: Examine query results for anomalies, correlating across multiple data sources.\n5. **Validate Findings**: Distinguish true positives from false positives through contextual analysis.\n6. **Correlate Activity**: Link findings to broader attack chains and threat actor TTPs.\n7. **Document and Report**: Record findings, update detection rules, and recommend response actions.\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| T1059.001 | PowerShell |\n| T1059.003 | Windows Command Shell |\n| T1562.001 | Disable or Modify Tools |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| CrowdStrike Falcon | EDR telemetry and threat detection |\n| Microsoft Defender for Endpoint | Advanced hunting with KQL |\n| Splunk Enterprise | SIEM log analysis with SPL queries |\n| Elastic Security | Detection rules and investigation timeline |\n| Sysmon | Detailed Windows event monitoring |\n| Velociraptor | Endpoint artifact collection and hunting |\n| Sigma Rules | Cross-platform detection rule format |\n\n## Common Scenarios\n\n1. **Scenario 1**: Base64 encoded PowerShell command launched by macro document\n2. **Scenario 2**: IEX download cradle fetching payload from C2 server\n3. **Scenario 3**: AMSI bypass via reflection patching before payload execution\n4. **Scenario 4**: PowerShell Empire agent communicating with C2\n\n## Output Format\n\n```\nHunt ID: TH-DETECT-[DATE]-[SEQ]\nTechnique: T1059.001\nHost: [Hostname]\nUser: [Account context]\nEvidence: [Log entries, process trees, network data]\nRisk Level: [Critical\u002FHigh\u002FMedium\u002FLow]\nConfidence: [High\u002FMedium\u002FLow]\nRecommended Action: [Containment, investigation, monitoring]\n```\n","# Detecting Suspicious Powershell Execution\n\n## When to Use\n\n- When proactively hunting for indicators of detecting suspicious powershell execution in the environment\n- After threat intelligence indicates active campaigns using these techniques\n- During incident response to scope compromise related to these techniques\n- When EDR or SIEM alerts trigger on related indicators\n- During periodic security assessments and purple team exercises\n\n## Prerequisites\n\n- EDR platform with process and network telemetry (CrowdStrike, MDE, SentinelOne)\n- SIEM with relevant log data ingested (Splunk, Elastic, Sentinel)\n- Sysmon deployed with comprehensive configuration\n- Windows Security Event Log forwarding enabled\n- Threat intelligence feeds for IOC correlation\n\n## Workflow\n\n1. **Formulate Hypothesis**: Define a testable hypothesis based on threat intelligence or ATT&CK gap analysis.\n2. **Identify Data Sources**: Determine which logs and telemetry are needed to validate or refute the hypothesis.\n3. **Execute Queries**: Run detection queries against SIEM and EDR platforms to collect relevant events.\n4. **Analyze Results**: Examine query results for anomalies, correlating across multiple data sources.\n5. **Validate Findings**: Distinguish true positives from false positives through contextual analysis.\n6. **Correlate Activity**: Link findings to broader attack chains and threat actor TTPs.\n7. **Document and Report**: Record findings, update detection rules, and recommend response actions.\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| T1059.001 | PowerShell |\n| T1059.003 | Windows Command Shell |\n| T1562.001 | Disable or Modify Tools |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| CrowdStrike Falcon | EDR telemetry and threat detection |\n| Microsoft Defender for Endpoint | Advanced hunting with KQL |\n| Splunk Enterprise | SIEM log analysis with SPL queries |\n| Elastic Security | Detection rules and investigation timeline |\n| Sysmon | Detailed Windows event monitoring |\n| Velociraptor | Endpoint artifact collection and hunting |\n| Sigma Rules | Cross-platform detection rule format |\n\n## Common Scenarios\n\n1. **Scenario 1**: Base64 encoded PowerShell command launched by macro document\n2. **Scenario 2**: IEX download cradle fetching payload from C2 server\n3. **Scenario 3**: AMSI bypass via reflection patching before payload execution\n4. **Scenario 4**: PowerShell Empire agent communicating with C2\n\n## Output Format\n\n```\nHunt ID: TH-DETECT-[DATE]-[SEQ]\nTechnique: T1059.001\nHost: [Hostname]\nUser: [Account context]\nEvidence: [Log entries, process trees, network data]\nRisk Level: [Critical\u002FHigh\u002FMedium\u002FLow]\nConfidence: [High\u002FMedium\u002FLow]\nRecommended Action: [Containment, investigation, monitoring]\n```\n",{"name":5,"tags":44,"capec":49,"model":50,"tools":51,"domain":33,"maxTurns":55,"nist_csf":56,"subdomain":26,"description":7,"mitre_attack":61,"d3fend_techniques":64},[26,29,37,45,46,47,48],"execution","t1059","amsi","proactive-detection",[],"sonnet",[52,32,53,54],"Read","Glob","Grep",20,[57,58,59,60],"DE.CM-01","DE.AE-02","DE.AE-07","ID.RA-05",[62,38,63],"T1059","T1070",[65,66,67,68,69],"Executable Denylisting","Execution Isolation","File Metadata Consistency Validation","Content Format Conversion","File Content Analysis","main","a91f1293287ffa9f4f1b8f486cd6e835a1568c84","skills\u002Fsoc\u002Fhunting\u002Fsuspicious\u002Fdetect","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace","https:\u002F\u002Fgithub.com\u002FDCx7C5","#Python","2026-09-01 11:21:00",{"source":8,"skillName":5,"commands":78,"prompt":88,"zipAvailable":89},[79,82,85],{"tool":80,"command":81},"npx","npx skills add DCx7C5\u002Fai-marketplace --skill hunting-suspicious-detect",{"tool":83,"command":84},"bunx","bunx skills add DCx7C5\u002Fai-marketplace --skill hunting-suspicious-detect",{"tool":86,"command":87},"pnpm","pnpm dlx skills add DCx7C5\u002Fai-marketplace --skill hunting-suspicious-detect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fsoc\u002Fhunting\u002Fsuspicious\u002Fdetect\u002FSKILL.md",true,[91],{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"index.json","REFERENCE","参考文档",636,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fsoc\u002Fhunting\u002Fsuspicious\u002Fdetect\u002Findex.json",[98,120,140,161,183,199],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":39},"01M71HAPZ01KQ30RKTB0FFSQ05","services-wmi-persistence-detect","Detect WMI event subscription persistence by enumerating ActiveScriptEventConsumer, CommandLineEventConsumer, and permanent subscriptions in the WMI repository.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fpersistence\u002Fdetect\u002FSKILL.md",[],[105,21,106,107,108,28,36,109,110,111,112,113,114,115,116,117,118,33,119],"services","services wmi persistence detect","wmi","persistence","process","activescript","event","subscriptions","commandline-consumer","repository","subscription","event-subscription","t1546.003","forensics","process-forensics",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":39},"01M71HAK6JTTTS229T17WJMMCG","services-wmi-exec-exploit","Perform lateral movement across Windows networks using WMI-based remote execution techniques including Impacket wmiexec.py, CrackMapExec, and native WMI commands for stealthy post-exploitation during red team engagements.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fexec\u002Fexploit\u002FSKILL.md",[],[127,105,128,107,129,130,131,33,32,31,132,133,134,135,28,136,137,27,138,139],"exploit","services wmi exec exploit","exec","remote","traffic","team","across","crackmapexec","native","command","lateral movement","lateral-movement","Impacket",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":39},"01M71HAG6MHKNQV8KDZKMT4886","registry-artifact-extract","Extract and analyze Windows Registry hives to uncover user activity, installed software, autostart entries, and evidence of system compromise.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fregistry\u002Fartifact\u002Fextract\u002FSKILL.md",[],[147,148,149,150,151,152,33,32,153,31,154,155,28,27,156,157,158,159,160,50],"artifact","registry","registry artifact extract","extract","evidence-collection","artifact-analysis","collection","analyze","uncover","software","activity","digital-forensics","windows-registry","regripper",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":39},"01M71HACR4A8XTWTTSXK4124AA","processes-token-impersonate-detect","Detect Windows token impersonation and privilege abuse including SeImpersonatePrivilege exploitation via Potato attacks and token stealing techniques.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Ftoken\u002Fimpersonate\u002Fdetect\u002FSKILL.md",[],[21,168,169,170,171,172,173,36,174,33,119,175,176,177,178,179,180,181,182,28],"processes token impersonate detect","token","processes","attacks","windows","escalation","techniques","privilege-escalation","seimpersonate","token-impersonation","printspoofer","exploitation","potato","impersonation","via",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":189,"publishedAt":39},"01M71HAABSB4Z6QFSXEG00R4RK","processes-thread-injection-detect","Detect Windows thread injection techniques including CreateRemoteThread, QueueUserAPC, NtCreateThreadEx, and thread hijacking via process memory analysis.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fthread\u002Finjection\u002Fdetect\u002FSKILL.md",[],[190,191,21,192,170,172,193,36,194,174,33,119,31,195,196,197,198,182,28,109],"thread","processes thread injection detect","injection","memory","process-injection","api","apc-injection","thread-injection","nt-api",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":205,"publishedAt":39},"01M71HA7H311V5G14WMX58HQSS","processes-hollow-technique-detect","Detect process hollowing (RunPE) by identifying processes with mismatched image paths between PEB and VAD tree, or unmapped PE headers in memory.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fhollow\u002Ftechnique\u002Fdetect\u002FSKILL.md",[],[206,21,170,207,193,36,208,209,33,119,210,211,212,213,214,215,28,109,216,217],"processes hollow technique detect","tree","memory-forensics","process-hollow","peb","runpe","image","pe-header","in memory","with","mismatched","headers"]