[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71DCCF96V1RGS7R7E40JF8R":3,"skill-same:01M71DCCF96V1RGS7R7E40JF8R":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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":70,"commitSha":71,"skillDirectory":72,"forksCount":14,"repositoryHtmlUrl":73,"repositoryHomepageUrl":6,"ownerHtmlUrl":74,"ownerBlogUrl":6,"ownerDescription":75,"updatedAt":76,"install":77,"resources":90},"01M71DCCF96V1RGS7R7E40JF8R","threat-phishing-detect",null,"Implement a phishing report button in email clients with automated triage workflow that analyzes user-reported suspicious emails and provides feedback to reporters.","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\u002Femail\u002Fthreat\u002Fphishing\u002Fdetect\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"threat","phishing","detect","threat phishing detect","reporting","read","at","co","microsoft-365","de","security-awareness","phishing-reporting","suspicious","soar","Bash","workflow","cybersecurity","incident","cm","t1566","2026-11-10 10:12:30",false,"---\nname: threat-phishing-detect\ndescription: Implement a phishing report button in email clients with automated triage workflow that analyzes user-reported suspicious emails and provides feedback to reporters.\ndomain: cybersecurity\nsubdomain: phishing-defense\ntags:\n- phishing-reporting\n- email-security\n- incident-response\n- security-awareness\n- outlook\n- microsoft-365\n- soar\nnist_csf:\n- PR.AT-01\n- DE.CM-09\n- RS.CO-02\n- DE.AE-02\nmodel: sonnet\nmaxTurns: 20\ntools: [Read, Bash, Glob, Grep]\nmitre_attack:\n- T1566\n- T1204\n- T1534\ncapec: []\n---\n\n# Building Phishing Reporting Button Workflow\n\n## Overview\nA phishing reporting button empowers users to flag suspicious emails directly from their email client, creating a critical feedback loop between end users and the security operations center. Microsoft's built-in Report button is now the recommended approach, replacing the deprecated Report Message and Report Phishing add-ins. When combined with automated triage using SOAR platforms, reported emails can be classified, IOCs extracted, and remediation actions taken within minutes. Organizations with effective phishing reporting programs see 70%+ report rates in phishing simulations.\n\n\n## When to Use\n\n- When deploying or configuring building phishing reporting button workflow capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- Microsoft 365 or Google Workspace with administrative access\n- SOAR platform or automation capability (Microsoft Sentinel, Splunk SOAR, Cortex XSOAR)\n- Dedicated reporting mailbox for phishing submissions\n- Email security gateway with message retraction capability\n- Security awareness training platform for feedback loop\n\n## Workflow\n\n### Step 1: Deploy Phishing Report Button\n- Enable Microsoft built-in Report button via Security & Compliance Center\n- Configure user reported settings: route to reporting mailbox and Microsoft\n- For third-party: deploy KnowBe4 Phish Alert Button or Cofense Reporter\n- Verify button appears in Outlook desktop, web, and mobile clients\n- Configure report options: Report Phishing, Report Junk, Report Not Junk\n\n### Step 2: Build Automated Triage Pipeline\n- Configure reporting mailbox monitored by SOAR platform\n- Auto-extract IOCs from reported emails: URLs, attachments, sender info, headers\n- Submit URLs to VirusTotal, URLScan.io for reputation check\n- Submit attachments to sandbox for dynamic analysis\n- Check sender against known threat intelligence feeds\n- Auto-classify: confirmed phishing, spam, simulation, legitimate\n\n### Step 3: Implement Response Actions\n- Confirmed phishing: auto-retract from all inboxes, block sender domain\n- Confirmed spam: move to junk for all recipients\n- Simulation email: mark as correctly reported, credit user\n- Legitimate email: return to inbox, notify reporter\n- Generate IOC report for threat intelligence team\n\n### Step 4: Create Feedback Loop\n- Send automated thank-you response to reporter within 5 minutes\n- Include classification result when analysis completes\n- Track reporter accuracy and engagement metrics\n- Recognize top reporters in monthly security newsletter\n- Feed reporting metrics into security awareness training program\n\n### Step 5: Measure and Optimize\n- Track mean time to triage (target: under 10 minutes automated)\n- Monitor report volume trends and false positive rates\n- Measure user reporting rate in phishing simulations\n- Report on confirmed threats caught by user reports vs. gateway\n- Optimize automation rules based on classification accuracy\n\n## Tools & Resources\n- **Microsoft Report Button**: Built-in Outlook phishing reporting\n- **Cofense Reporter + Triage**: Enterprise phishing reporting and automated analysis\n- **KnowBe4 Phish Alert Button**: Integrated reporting with simulation platform\n- **Microsoft Sentinel**: SOAR automation for triage workflow\n- **Proofpoint CLEAR**: Closed-loop email analysis and response\n\n## Validation\n- Report button visible and functional across all Outlook platforms\n- Reported email arrives in dedicated mailbox within 60 seconds\n- Automated triage classifies test phishing email correctly\n- Auto-retraction removes confirmed phishing from all inboxes\n- Reporter receives feedback notification with classification\n- Metrics dashboard shows report volume and accuracy trends\n","# Building Phishing Reporting Button Workflow\n\n## Overview\nA phishing reporting button empowers users to flag suspicious emails directly from their email client, creating a critical feedback loop between end users and the security operations center. Microsoft's built-in Report button is now the recommended approach, replacing the deprecated Report Message and Report Phishing add-ins. When combined with automated triage using SOAR platforms, reported emails can be classified, IOCs extracted, and remediation actions taken within minutes. Organizations with effective phishing reporting programs see 70%+ report rates in phishing simulations.\n\n\n## When to Use\n\n- When deploying or configuring building phishing reporting button workflow capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- Microsoft 365 or Google Workspace with administrative access\n- SOAR platform or automation capability (Microsoft Sentinel, Splunk SOAR, Cortex XSOAR)\n- Dedicated reporting mailbox for phishing submissions\n- Email security gateway with message retraction capability\n- Security awareness training platform for feedback loop\n\n## Workflow\n\n### Step 1: Deploy Phishing Report Button\n- Enable Microsoft built-in Report button via Security & Compliance Center\n- Configure user reported settings: route to reporting mailbox and Microsoft\n- For third-party: deploy KnowBe4 Phish Alert Button or Cofense Reporter\n- Verify button appears in Outlook desktop, web, and mobile clients\n- Configure report options: Report Phishing, Report Junk, Report Not Junk\n\n### Step 2: Build Automated Triage Pipeline\n- Configure reporting mailbox monitored by SOAR platform\n- Auto-extract IOCs from reported emails: URLs, attachments, sender info, headers\n- Submit URLs to VirusTotal, URLScan.io for reputation check\n- Submit attachments to sandbox for dynamic analysis\n- Check sender against known threat intelligence feeds\n- Auto-classify: confirmed phishing, spam, simulation, legitimate\n\n### Step 3: Implement Response Actions\n- Confirmed phishing: auto-retract from all inboxes, block sender domain\n- Confirmed spam: move to junk for all recipients\n- Simulation email: mark as correctly reported, credit user\n- Legitimate email: return to inbox, notify reporter\n- Generate IOC report for threat intelligence team\n\n### Step 4: Create Feedback Loop\n- Send automated thank-you response to reporter within 5 minutes\n- Include classification result when analysis completes\n- Track reporter accuracy and engagement metrics\n- Recognize top reporters in monthly security newsletter\n- Feed reporting metrics into security awareness training program\n\n### Step 5: Measure and Optimize\n- Track mean time to triage (target: under 10 minutes automated)\n- Monitor report volume trends and false positive rates\n- Measure user reporting rate in phishing simulations\n- Report on confirmed threats caught by user reports vs. gateway\n- Optimize automation rules based on classification accuracy\n\n## Tools & Resources\n- **Microsoft Report Button**: Built-in Outlook phishing reporting\n- **Cofense Reporter + Triage**: Enterprise phishing reporting and automated analysis\n- **KnowBe4 Phish Alert Button**: Integrated reporting with simulation platform\n- **Microsoft Sentinel**: SOAR automation for triage workflow\n- **Proofpoint CLEAR**: Closed-loop email analysis and response\n\n## Validation\n- Report button visible and functional across all Outlook platforms\n- Reported email arrives in dedicated mailbox within 60 seconds\n- Automated triage classifies test phishing email correctly\n- Auto-retraction removes confirmed phishing from all inboxes\n- Reporter receives feedback notification with classification\n- Metrics dashboard shows report volume and accuracy trends\n",{"name":5,"tags":49,"capec":53,"model":54,"tools":55,"domain":40,"maxTurns":59,"nist_csf":60,"subdomain":65,"description":7,"mitre_attack":66},[35,50,51,34,52,32,37],"email-security","incident-response","outlook",[],"sonnet",[56,38,57,58],"Read","Glob","Grep",20,[61,62,63,64],"PR.AT-01","DE.CM-09","RS.CO-02","DE.AE-02","phishing-defense",[67,68,69],"T1566","T1204","T1534","main","a91f1293287ffa9f4f1b8f486cd6e835a1568c84","skills\u002Femail\u002Fthreat\u002Fphishing\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 threat-phishing-detect",{"tool":83,"command":84},"bunx","bunx skills add DCx7C5\u002Fai-marketplace --skill threat-phishing-detect",{"tool":86,"command":87},"pnpm","pnpm dlx skills add DCx7C5\u002Fai-marketplace --skill threat-phishing-detect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Femail\u002Fthreat\u002Fphishing\u002Fdetect\u002FSKILL.md",true,[91],{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"index.json","REFERENCE","参考文档",641,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Femail\u002Fthreat\u002Fphishing\u002Fdetect\u002Findex.json",[98,120,141,162,184,200],{"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":44},"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,26,106,107,108,33,42,109,110,111,112,113,114,115,116,117,118,40,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":44},"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,40,38,132,133,134,135,136,33,137,138,29,139,140],"exploit","services wmi exec exploit","exec","remote","traffic","analysis","team","across","crackmapexec","native","command","lateral movement","lateral-movement","Impacket",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":44},"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",[],[148,149,150,151,152,153,40,38,154,132,155,156,33,29,157,158,159,160,161,54],"artifact","registry","registry artifact extract","extract","evidence-collection","artifact-analysis","collection","analyze","uncover","software","activity","digital-forensics","windows-registry","regripper",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":44},"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",[],[26,169,170,171,172,173,174,42,175,40,119,176,177,178,179,180,181,182,183,33],"processes token impersonate detect","token","processes","attacks","windows","escalation","techniques","privilege-escalation","seimpersonate","token-impersonation","printspoofer","exploitation","potato","impersonation","via",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":190,"publishedAt":44},"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",[],[191,192,26,193,171,173,194,42,195,175,40,119,132,196,197,198,199,183,33,109],"thread","processes thread injection detect","injection","memory","process-injection","api","apc-injection","thread-injection","nt-api",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":206,"publishedAt":44},"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",[],[207,26,171,208,194,42,209,210,40,119,211,212,213,214,215,216,33,109,217,218],"processes hollow technique detect","tree","memory-forensics","process-hollow","peb","runpe","image","pe-header","in memory","with","mismatched","headers"]