[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71DB5K58PVWR0FFVTN6H5ZA":3,"skill-same:01M71DB5K58PVWR0FFVTN6H5ZA":110},{"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":83,"commitSha":84,"skillDirectory":85,"forksCount":14,"repositoryHtmlUrl":86,"repositoryHomepageUrl":6,"ownerHtmlUrl":87,"ownerBlogUrl":6,"ownerDescription":88,"updatedAt":89,"install":90,"resources":103},"01M71DB5K58PVWR0FFVTN6H5ZA","phishing-business-exploit",null,"Business Email Compromise (BEC) is a sophisticated fraud scheme where attackers impersonate executives, vendors, or trusted partners to trick employees into transferring funds, sharing sensitive data,","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\u002Fphishing\u002Fbusiness\u002Fexploit\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],"business","phishing","phishing business exploit","exploit","defense","dmarc","sophisticated","read","at","co","de","Bash","aml","access","cybersecurity","map","remote","social","cm","t1566","2026-11-10 10:12:30",false,"---\nname: phishing-business-exploit\ndescription: Business Email Compromise (BEC) is a sophisticated fraud scheme where attackers impersonate executives, vendors, or trusted partners to trick employees into transferring funds, sharing sensitive data,\ndomain: cybersecurity\nsubdomain: phishing-defense\ntags:\n- phishing\n- email-security\n- social-engineering\n- dmarc\n- awareness\n- bec\n- fraud\natlas_techniques:\n- AML.T0052\n- AML.T0088\nnist_ai_rmf:\n- GOVERN-6.2\n- MAP-5.2\nd3fend_techniques:\n- Restore Object\n- Restore Configuration\n- Application Configuration Hardening\n- Application Hardening\n- Disable Remote Access\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- T1059\n- T1566\ncapec: []\n---\n\n# Detecting Business Email Compromise\n\n## Overview\nBusiness Email Compromise (BEC) is a sophisticated fraud scheme where attackers impersonate executives, vendors, or trusted partners to trick employees into transferring funds, sharing sensitive data, or changing payment details. Unlike traditional phishing, BEC often contains no malicious links or attachments, relying purely on social engineering. This skill covers detection techniques using email gateway rules, behavioral analytics, and financial process controls.\n\n\n## When to Use\n\n- When investigating security incidents that require detecting business email compromise\n- When building detection rules or threat hunting queries for this domain\n- When SOC analysts need structured procedures for this analysis type\n- When validating security monitoring coverage for related attack techniques\n\n## Prerequisites\n- Email security gateway with BEC detection capabilities\n- Understanding of organizational financial processes and approval chains\n- Access to email logs and SIEM platform\n- Knowledge of social engineering tactics\n\n## Key Concepts\n\n### BEC Attack Types (FBI IC3 Classification)\n1. **CEO Fraud**: Attacker impersonates CEO, requests urgent wire transfer\n2. **Account Compromise**: Employee email compromised, used to request payments from vendors\n3. **False Invoice Scheme**: Fake invoices from \"vendor\" with changed bank details\n4. **Attorney Impersonation**: Impersonates legal counsel for urgent confidential transfers\n5. **Data Theft**: Requests W-2, tax forms, or PII from HR\n\n### Detection Indicators\n- Urgency and secrecy language (\"confidential\", \"do not discuss with others\")\n- New or changed payment instructions\n- Executive communication outside normal patterns\n- Display name matches executive but email domain differs\n- Reply-to address differs from From address\n- First-time communication pattern between sender and recipient\n- Request for gift cards or cryptocurrency\n\n## Workflow\n\n### Step 1: Configure BEC-Specific Email Rules\n- Flag emails with VIP display names from external domains\n- Detect financial keywords combined with urgency language\n- Alert on first-time sender to finance\u002Faccounting staff\n- Check for Reply-To domain mismatch\n\n### Step 2: Deploy Behavioral Analytics\n- Baseline normal communication patterns per user\n- Detect anomalous requests (unusual recipient, unusual time, unusual request type)\n- Monitor for email forwarding rule changes (T1114.003)\n\n### Step 3: Implement Financial Controls\n- Dual-authorization for wire transfers above threshold\n- Out-of-band verification for payment detail changes (phone callback)\n- Vendor payment change verification process\n- Finance team training on BEC red flags\n\n### Step 4: Monitor for Account Compromise\n- Detect impossible travel in email login locations\n- Alert on email forwarding rule creation\n- Monitor for mailbox delegation changes\n- Check for inbox rules hiding BEC-related emails\n\n## Tools & Resources\n- **Microsoft Defender for O365 Anti-BEC**: Built-in BEC detection\n- **Proofpoint Email Fraud Defense**: BEC-specific solution\n- **Abnormal Security**: AI-driven BEC detection\n- **FBI IC3 BEC Advisory**: https:\u002F\u002Fwww.ic3.gov\u002F\n- **FinCEN BEC Advisory**: Financial institution guidance\n\n## Validation\n- BEC detection rules trigger on test scenarios\n- Financial controls prevent unauthorized transfers in drills\n- Account compromise detection catches simulated attacks\n- Reduced BEC susceptibility in awareness assessments\n","# Detecting Business Email Compromise\n\n## Overview\nBusiness Email Compromise (BEC) is a sophisticated fraud scheme where attackers impersonate executives, vendors, or trusted partners to trick employees into transferring funds, sharing sensitive data, or changing payment details. Unlike traditional phishing, BEC often contains no malicious links or attachments, relying purely on social engineering. This skill covers detection techniques using email gateway rules, behavioral analytics, and financial process controls.\n\n\n## When to Use\n\n- When investigating security incidents that require detecting business email compromise\n- When building detection rules or threat hunting queries for this domain\n- When SOC analysts need structured procedures for this analysis type\n- When validating security monitoring coverage for related attack techniques\n\n## Prerequisites\n- Email security gateway with BEC detection capabilities\n- Understanding of organizational financial processes and approval chains\n- Access to email logs and SIEM platform\n- Knowledge of social engineering tactics\n\n## Key Concepts\n\n### BEC Attack Types (FBI IC3 Classification)\n1. **CEO Fraud**: Attacker impersonates CEO, requests urgent wire transfer\n2. **Account Compromise**: Employee email compromised, used to request payments from vendors\n3. **False Invoice Scheme**: Fake invoices from \"vendor\" with changed bank details\n4. **Attorney Impersonation**: Impersonates legal counsel for urgent confidential transfers\n5. **Data Theft**: Requests W-2, tax forms, or PII from HR\n\n### Detection Indicators\n- Urgency and secrecy language (\"confidential\", \"do not discuss with others\")\n- New or changed payment instructions\n- Executive communication outside normal patterns\n- Display name matches executive but email domain differs\n- Reply-to address differs from From address\n- First-time communication pattern between sender and recipient\n- Request for gift cards or cryptocurrency\n\n## Workflow\n\n### Step 1: Configure BEC-Specific Email Rules\n- Flag emails with VIP display names from external domains\n- Detect financial keywords combined with urgency language\n- Alert on first-time sender to finance\u002Faccounting staff\n- Check for Reply-To domain mismatch\n\n### Step 2: Deploy Behavioral Analytics\n- Baseline normal communication patterns per user\n- Detect anomalous requests (unusual recipient, unusual time, unusual request type)\n- Monitor for email forwarding rule changes (T1114.003)\n\n### Step 3: Implement Financial Controls\n- Dual-authorization for wire transfers above threshold\n- Out-of-band verification for payment detail changes (phone callback)\n- Vendor payment change verification process\n- Finance team training on BEC red flags\n\n### Step 4: Monitor for Account Compromise\n- Detect impossible travel in email login locations\n- Alert on email forwarding rule creation\n- Monitor for mailbox delegation changes\n- Check for inbox rules hiding BEC-related emails\n\n## Tools & Resources\n- **Microsoft Defender for O365 Anti-BEC**: Built-in BEC detection\n- **Proofpoint Email Fraud Defense**: BEC-specific solution\n- **Abnormal Security**: AI-driven BEC detection\n- **FBI IC3 BEC Advisory**: https:\u002F\u002Fwww.ic3.gov\u002F\n- **FinCEN BEC Advisory**: Financial institution guidance\n\n## Validation\n- BEC detection rules trigger on test scenarios\n- Financial controls prevent unauthorized transfers in drills\n- Account compromise detection catches simulated attacks\n- Reduced BEC susceptibility in awareness assessments\n",{"name":5,"tags":49,"capec":55,"model":56,"tools":57,"domain":38,"maxTurns":61,"nist_csf":62,"subdomain":67,"description":7,"nist_ai_rmf":68,"mitre_attack":71,"atlas_techniques":74,"d3fend_techniques":77},[25,50,51,29,52,53,54],"email-security","social-engineering","awareness","bec","fraud",[],"sonnet",[58,35,59,60],"Read","Glob","Grep",20,[63,64,65,66],"PR.AT-01","DE.CM-09","RS.CO-02","DE.AE-02","phishing-defense",[69,70],"GOVERN-6.2","MAP-5.2",[72,73],"T1059","T1566",[75,76],"AML.T0052","AML.T0088",[78,79,80,81,82],"Restore Object","Restore Configuration","Application Configuration Hardening","Application Hardening","Disable Remote Access","main","a91f1293287ffa9f4f1b8f486cd6e835a1568c84","skills\u002Femail\u002Fphishing\u002Fbusiness\u002Fexploit","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace","https:\u002F\u002Fgithub.com\u002FDCx7C5","#Python","2026-09-01 11:21:00",{"source":8,"skillName":5,"commands":91,"prompt":101,"zipAvailable":102},[92,95,98],{"tool":93,"command":94},"npx","npx skills add DCx7C5\u002Fai-marketplace --skill phishing-business-exploit",{"tool":96,"command":97},"bunx","bunx skills add DCx7C5\u002Fai-marketplace --skill phishing-business-exploit",{"tool":99,"command":100},"pnpm","pnpm dlx skills add DCx7C5\u002Fai-marketplace --skill phishing-business-exploit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Femail\u002Fphishing\u002Fbusiness\u002Fexploit\u002FSKILL.md",true,[104],{"path":105,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":108,"sourceHtmlUrl":109},"index.json","REFERENCE","参考文档",686,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Femail\u002Fphishing\u002Fbusiness\u002Fexploit\u002Findex.json",[111,134,153,174,196,212],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"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",[],[118,119,120,121,122,34,42,123,124,125,126,127,128,129,130,131,132,38,133],"services","detect","services wmi persistence detect","wmi","persistence","process","activescript","event","subscriptions","commandline-consumer","repository","subscription","event-subscription","t1546.003","forensics","process-forensics",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"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",[],[27,118,141,121,142,40,143,38,35,144,145,146,147,148,34,149,150,31,151,152],"services wmi exec exploit","exec","traffic","analysis","team","across","crackmapexec","native","command","lateral movement","lateral-movement","Impacket",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"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",[],[160,161,162,163,164,165,38,35,166,144,167,168,34,31,169,170,171,172,173,56],"artifact","registry","registry artifact extract","extract","evidence-collection","artifact-analysis","collection","analyze","uncover","software","activity","digital-forensics","windows-registry","regripper",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":180,"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",[],[119,181,182,183,184,185,186,42,187,38,133,188,189,190,191,192,193,194,195,34],"processes token impersonate detect","token","processes","attacks","windows","escalation","techniques","privilege-escalation","seimpersonate","token-impersonation","printspoofer","exploitation","potato","impersonation","via",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":202,"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",[],[203,204,119,205,183,185,206,42,207,187,38,133,144,208,209,210,211,195,34,123],"thread","processes thread injection detect","injection","memory","process-injection","api","apc-injection","thread-injection","nt-api",{"skillNo":213,"name":214,"nameZh":6,"description":215,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":216,"categories":217,"keywords":218,"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",[],[219,119,183,220,206,42,221,222,38,133,223,224,225,226,227,228,34,123,229,230],"processes hollow technique detect","tree","memory-forensics","process-hollow","peb","runpe","image","pe-header","in memory","with","mismatched","headers"]