[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HEBNT3MCQ2N7JSWVHTV2KS":3,"skill-same:01M6HEBNT3MCQ2N7JSWVHTV2KS":140},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":83,"commitSha":84,"skillDirectory":85,"forksCount":86,"repositoryHtmlUrl":87,"repositoryHomepageUrl":6,"ownerHtmlUrl":88,"ownerBlogUrl":6,"ownerDescription":89,"updatedAt":90,"install":91,"resources":104},"01M6HEBNT3MCQ2N7JSWVHTV2KS","detecting-qr-code-phishing-with-email-security",null,"Detect and prevent QR code phishing (quishing) attacks that bypass traditional email security by embedding malicious URLs in QR code images within emails.","HenriqueMC17\u002Fagente-core","HenriqueMC17","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206460478?v=4","01M6HB63HBBF18AC4H09XTB549","Henrique Monteiro Cardoso","01M6HB63NGSQXWKWCFWW2B20W0",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-qr-code-phishing-with-email-security\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"qr code","qr","email security","detecting","with","detecting qr code phishing with email security","phishing","email","code","security","qr-code","ocr","t1566","image","aml","cm","images","map","embedding","cybersecurity","2026-11-10 10:12:30",false,"---\nname: detecting-qr-code-phishing-with-email-security\ndescription: Detect and prevent QR code phishing (quishing) attacks that bypass traditional email security by embedding malicious URLs in QR code images within emails.\ndomain: cybersecurity\nsubdomain: phishing-defense\ntags:\n- quishing\n- qr-code\n- phishing\n- email-security\n- image-analysis\n- ocr\n- mobile-security\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\natlas_techniques:\n- AML.T0052\n- AML.T0024\n- AML.T0035\nnist_ai_rmf:\n- MEASURE-2.8\n- MAP-5.1\nnist_csf:\n- PR.AT-01\n- DE.CM-09\n- RS.CO-02\n- DE.AE-02\nmitre_attack:\n- T1566\n- T1598\n- T1534\n- T1036\n- T1027\ncategory: detecting-qr-code-phishing-with-email-security\n---\n# Detecting QR Code Phishing with Email Security\n\n## Overview\nQR code phishing (quishing) is a rapidly growing attack vector where malicious URLs are embedded in QR code images within phishing emails. Quishing incidents grew fivefold from 46,000 to 250,000 between August and November 2025, with credential phishing comprising 89.3% of detected incidents. Traditional email security filters struggle because QR codes cannot be read by humans or standard URL scanners, and when scanned, users typically use personal mobile devices that lack corporate security controls. Attackers have evolved to use split QR codes (two separate images), nested QR codes, and ASCII text-based QR codes to evade detection.\n\n\n## When to Use\n\n- When investigating security incidents that require detecting qr code phishing with email security\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 image analysis capabilities\n- Understanding of QR code structure and encoding\n- Mobile device management (MDM) or mobile threat defense solution\n- Security awareness training program\n- SIEM platform for correlation and alerting\n\n## Key Concepts\n\n### Why Quishing Works\n1. **Bypasses URL Scanners**: Traditional gateways scan text-based URLs but cannot decode image-embedded URLs\n2. **Shifts to Unprotected Devices**: Corporate email arrives on secured systems but QR scan occurs on personal mobile devices\n3. **User Trust**: QR codes are normalized in daily life (payments, menus, parking)\n4. **Low Detection Rate**: Only 36% of quishing incidents are accurately identified by recipients\n\n### Evasion Techniques (2025)\n- **Split QR Codes**: QR code divided into two separate images that look benign individually (Gabagool PhaaS kit)\n- **Nested QR Codes**: QR code within a QR code, with first scan leading to intermediate page\n- **ASCII QR Codes**: QR rendered as text characters instead of images, bypassing image analysis (12% of attacks in Jan 2026)\n- **Styled\u002FArtistic QR Codes**: Custom-designed QR codes with logos that evade pattern matching\n- **PDF Attachment QR**: QR code embedded in PDF attachment rather than email body\n\n### Detection Challenges\n- Pattern-based detection faces trade-off: aggressive tuning causes false positives, cautious tuning causes misses\n- Average similarity score of 0.209 between quishing and legitimate QR emails\n- QR codes in image attachments require OCR and deep image processing\n\n## Workflow\n\n### Step 1: Enable Image-Based Threat Detection\n- Configure email gateway to scan embedded images for QR codes\n- Enable OCR processing on image attachments (PNG, JPG, GIF, BMP)\n- Deploy multimodal AI that combines image processing, OCR, and NLP analysis\n- Configure PDF scanning to detect QR codes within attachments\n- Set up detection for ASCII\u002Ftext-based QR code rendering\n\n### Step 2: Configure QR Code URL Analysis\n- Extract URLs from detected QR codes and submit to URL reputation services\n- Apply same URL scanning policies to QR-extracted URLs as text-based URLs\n- Enable real-time sandbox analysis for QR-decoded destination pages\n- Configure time-of-click protection for QR-extracted URLs where possible\n- Block known phishing domains extracted from QR codes\n\n### Step 3: Deploy Mobile-Side Protection\n- Implement mobile threat defense (MTD) with QR code scanning capability\n- Deploy Palo Alto ALFA or equivalent safe-by-design QR scanning\n- Configure MDM policies to warn users before opening scanned URLs\n- Enable corporate VPN\u002Fsecure browser for QR-scanned destinations\n- Block known credential harvesting domains at the mobile proxy level\n\n### Step 4: Build Detection Rules\n- Alert on emails containing only an image and minimal text (common quishing pattern)\n- Flag emails with QR code images from external first-time senders\n- Detect urgency language combined with QR code presence\n- Alert on emails impersonating IT\u002Fsecurity team requesting QR scan for MFA setup\n- Monitor for common quishing themes: MFA reset, document signing, voicemail notification\n\n### Step 5: Train Users on Quishing Recognition\n- Update security awareness program to include QR code phishing scenarios\n- Conduct quishing simulation campaigns using controlled QR codes\n- Teach users to verify QR destination URLs before entering credentials\n- Establish reporting process for suspicious QR code emails\n- Distribute guidance on safe QR scanning practices\n\n## Tools & Resources\n- **Barracuda Multimodal AI**: OCR + deep image processing for QR detection\n- **Palo Alto ALFA**: Safe-by-design QR code scanning assessment\n- **Microsoft Defender for O365**: QR code detection in email images\n- **Proofpoint TAP**: Image-based threat analysis with QR decoding\n- **Lookout\u002FZimperium**: Mobile threat defense with QR scanning\n\n## Validation\n- QR code phishing emails detected in controlled testing\n- Split QR code and ASCII QR code evasion techniques caught\n- QR-extracted URLs submitted to sandbox analysis\n- Mobile devices alert on malicious QR destinations\n- User reporting rate for quishing simulations exceeds 50%\n- False positive rate for QR detection below 1%\n","# Detecting QR Code Phishing with Email Security\n\n## Overview\nQR code phishing (quishing) is a rapidly growing attack vector where malicious URLs are embedded in QR code images within phishing emails. Quishing incidents grew fivefold from 46,000 to 250,000 between August and November 2025, with credential phishing comprising 89.3% of detected incidents. Traditional email security filters struggle because QR codes cannot be read by humans or standard URL scanners, and when scanned, users typically use personal mobile devices that lack corporate security controls. Attackers have evolved to use split QR codes (two separate images), nested QR codes, and ASCII text-based QR codes to evade detection.\n\n\n## When to Use\n\n- When investigating security incidents that require detecting qr code phishing with email security\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 image analysis capabilities\n- Understanding of QR code structure and encoding\n- Mobile device management (MDM) or mobile threat defense solution\n- Security awareness training program\n- SIEM platform for correlation and alerting\n\n## Key Concepts\n\n### Why Quishing Works\n1. **Bypasses URL Scanners**: Traditional gateways scan text-based URLs but cannot decode image-embedded URLs\n2. **Shifts to Unprotected Devices**: Corporate email arrives on secured systems but QR scan occurs on personal mobile devices\n3. **User Trust**: QR codes are normalized in daily life (payments, menus, parking)\n4. **Low Detection Rate**: Only 36% of quishing incidents are accurately identified by recipients\n\n### Evasion Techniques (2025)\n- **Split QR Codes**: QR code divided into two separate images that look benign individually (Gabagool PhaaS kit)\n- **Nested QR Codes**: QR code within a QR code, with first scan leading to intermediate page\n- **ASCII QR Codes**: QR rendered as text characters instead of images, bypassing image analysis (12% of attacks in Jan 2026)\n- **Styled\u002FArtistic QR Codes**: Custom-designed QR codes with logos that evade pattern matching\n- **PDF Attachment QR**: QR code embedded in PDF attachment rather than email body\n\n### Detection Challenges\n- Pattern-based detection faces trade-off: aggressive tuning causes false positives, cautious tuning causes misses\n- Average similarity score of 0.209 between quishing and legitimate QR emails\n- QR codes in image attachments require OCR and deep image processing\n\n## Workflow\n\n### Step 1: Enable Image-Based Threat Detection\n- Configure email gateway to scan embedded images for QR codes\n- Enable OCR processing on image attachments (PNG, JPG, GIF, BMP)\n- Deploy multimodal AI that combines image processing, OCR, and NLP analysis\n- Configure PDF scanning to detect QR codes within attachments\n- Set up detection for ASCII\u002Ftext-based QR code rendering\n\n### Step 2: Configure QR Code URL Analysis\n- Extract URLs from detected QR codes and submit to URL reputation services\n- Apply same URL scanning policies to QR-extracted URLs as text-based URLs\n- Enable real-time sandbox analysis for QR-decoded destination pages\n- Configure time-of-click protection for QR-extracted URLs where possible\n- Block known phishing domains extracted from QR codes\n\n### Step 3: Deploy Mobile-Side Protection\n- Implement mobile threat defense (MTD) with QR code scanning capability\n- Deploy Palo Alto ALFA or equivalent safe-by-design QR scanning\n- Configure MDM policies to warn users before opening scanned URLs\n- Enable corporate VPN\u002Fsecure browser for QR-scanned destinations\n- Block known credential harvesting domains at the mobile proxy level\n\n### Step 4: Build Detection Rules\n- Alert on emails containing only an image and minimal text (common quishing pattern)\n- Flag emails with QR code images from external first-time senders\n- Detect urgency language combined with QR code presence\n- Alert on emails impersonating IT\u002Fsecurity team requesting QR scan for MFA setup\n- Monitor for common quishing themes: MFA reset, document signing, voicemail notification\n\n### Step 5: Train Users on Quishing Recognition\n- Update security awareness program to include QR code phishing scenarios\n- Conduct quishing simulation campaigns using controlled QR codes\n- Teach users to verify QR destination URLs before entering credentials\n- Establish reporting process for suspicious QR code emails\n- Distribute guidance on safe QR scanning practices\n\n## Tools & Resources\n- **Barracuda Multimodal AI**: OCR + deep image processing for QR detection\n- **Palo Alto ALFA**: Safe-by-design QR code scanning assessment\n- **Microsoft Defender for O365**: QR code detection in email images\n- **Proofpoint TAP**: Image-based threat analysis with QR decoding\n- **Lookout\u002FZimperium**: Mobile threat defense with QR scanning\n\n## Validation\n- QR code phishing emails detected in controlled testing\n- Split QR code and ASCII QR code evasion techniques caught\n- QR-extracted URLs submitted to sandbox analysis\n- Mobile devices alert on malicious QR destinations\n- User reporting rate for quishing simulations exceeds 50%\n- False positive rate for QR detection below 1%\n",{"name":5,"tags":57,"author":62,"domain":51,"license":15,"version":63,"category":5,"nist_csf":64,"subdomain":69,"description":7,"nist_ai_rmf":70,"mitre_attack":73,"atlas_techniques":79},[58,42,38,59,60,43,61],"quishing","email-security","image-analysis","mobile-security","mahipal","1.0",[65,66,67,68],"PR.AT-01","DE.CM-09","RS.CO-02","DE.AE-02","phishing-defense",[71,72],"MEASURE-2.8","MAP-5.1",[74,75,76,77,78],"T1566","T1598","T1534","T1036","T1027",[80,81,82],"AML.T0052","AML.T0024","AML.T0035","main","5eea5b3296f4673b5f481e8bcc1ba76281149f16","modules\u002Fdetecting-qr-code-phishing-with-email-security",0,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core","https:\u002F\u002Fgithub.com\u002FHenriqueMC17","Qualquer tecnologia suficientemente avançada é indistinguível da mágica.","2026-09-28 22:40:38",{"source":8,"skillName":5,"commands":92,"prompt":102,"zipAvailable":103},[93,96,99],{"tool":94,"command":95},"npx","npx skills add HenriqueMC17\u002Fagente-core --skill detecting-qr-code-phishing-with-email-security",{"tool":97,"command":98},"bunx","bunx skills add HenriqueMC17\u002Fagente-core --skill detecting-qr-code-phishing-with-email-security",{"tool":100,"command":101},"pnpm","pnpm dlx skills add HenriqueMC17\u002Fagente-core --skill detecting-qr-code-phishing-with-email-security","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-qr-code-phishing-with-email-security\u002FSKILL.md",true,[105,111,116,122,126,130,136],{"path":106,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":109,"sourceHtmlUrl":110},"assets\u002Ftemplate.md","ASSET","资产文件",1502,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-qr-code-phishing-with-email-security\u002Fassets\u002Ftemplate.md",{"path":112,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":114,"sourceHtmlUrl":115},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-qr-code-phishing-with-email-security\u002FLICENSE",{"path":117,"resourceType":118,"resourceTypeDesc":119,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Fapi-reference.md","REFERENCE","参考文档",2445,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-qr-code-phishing-with-email-security\u002Freferences\u002Fapi-reference.md",{"path":123,"resourceType":118,"resourceTypeDesc":119,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fstandards.md",1668,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-qr-code-phishing-with-email-security\u002Freferences\u002Fstandards.md",{"path":127,"resourceType":118,"resourceTypeDesc":119,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fworkflows.md",2558,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-qr-code-phishing-with-email-security\u002Freferences\u002Fworkflows.md",{"path":131,"resourceType":132,"resourceTypeDesc":133,"sizeBytes":134,"sourceHtmlUrl":135},"scripts\u002Fagent.py","SCRIPT","脚本",6055,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-qr-code-phishing-with-email-security\u002Fscripts\u002Fagent.py",{"path":137,"resourceType":132,"resourceTypeDesc":133,"sizeBytes":138,"sourceHtmlUrl":139},"scripts\u002Fprocess.py",11736,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fdetecting-qr-code-phishing-with-email-security\u002Fscripts\u002Fprocess.py",[141,170,195,217,233,252],{"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":150,"publishedAt":52},"01M6HPFF0RCN0X6WT5EBSV71GY","validating-backup-integrity-for-recovery","Validate backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to ensure backups are reliable for disaster recovery and ransomware response scenarios.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[147],{"categoryNo":148,"categoryName":149,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[151,152,153,154,155,156,51,157,158,159,160,161,162,163,164,165,166,167,168,169],"integrity","backup","recovery","validating backup integrity for recovery","for","testing","validate","verification","hash-verification","incident-response","ransomware","detection","t1078","t1490","disaster-recovery","restore","incident","disaster recovery","ransomware response",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":52},"01M6HPFAWJVFK25Q33K3T7WQ8G","triaging-vulnerabilities-with-ssvc-framework","Triage and prioritize vulnerabilities using CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree framework to produce actionable remediation priorities.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[],[177,178,179,180,36,51,181,182,183,184,185,186,187,188,189,190,191,192,193,194],"vulnerabilities","framework","ssvc","triaging vulnerabilities with ssvc framework","triage and prioritize","CISA","vulnerability-management","risk-management","cvss","remediation","vulnerability","prioritization","decision-tree","prioritize","decision","priorities","actionable","tree",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":201,"publishedAt":52},"01M6HPF6JS9X72WP59094H3ASQ","triaging-security-incident","Performs initial triage of security incidents to determine severity, scope, and required response actions using the NIST SP 800-61r3 and SANS PICERL frameworks. Classifies incidents by type, assigns priority based on business impact, and routes...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident\u002FSKILL.md",[],[41,202,167,51,203,204,205,163,164,206,207,208,209,210,211,212,213,214,215,216],"triaging security incident","actions","soc","NIST","analysis","severity-classification","incident-triage","SANS-PICERL","SOC-operations","picerl","conversion","isolation","scope","impact","consistency",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":223,"publishedAt":52},"01M6HPF2EX6ZYNYYHKBRJN7GEF","triaging-security-incident-with-ir-playbook","Classify and prioritize security incidents using structured IR playbooks to determine severity, assign response teams, and initiate appropriate response procedures.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident-with-ir-playbook\u002FSKILL.md",[],[41,224,225,202,167,36,51,226,204,160,227,228,163,164,229,207,190,230,231,232],"playbook","triaging security incident with ir playbook","teams","IR-playbook","severity","classification","classify","incidents","initiate",{"skillNo":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":237,"categories":238,"keywords":239,"publishedAt":52},"01M6HPEY9XPGE7X95AG4XJFQAW","triaging-security-alerts-in-splunk","Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL queries and the Incident Review dashboard. Use when...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-alerts-in-splunk\u002FSKILL.md",[],[41,240,241,242,243,244,51,245,246,247,204,248,163,44,249,250,210,47,167,251],"security alerts","splunk","triaging security alerts in splunk","alerts","review","siem","dashboard","search","correlation-search","notable-events","incident-review","de",{"skillNo":253,"name":254,"nameZh":6,"description":255,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":256,"categories":257,"keywords":258,"publishedAt":52},"01M6HPET6XGEPEJPN7V032JGZ0","tracking-threat-actor-infrastructure","Threat actor infrastructure tracking involves monitoring and mapping adversary-controlled assets including command-and-control (C2) servers, phishing domains, exploit kit hosts, bulletproof hosting, a","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftracking-threat-actor-infrastructure\u002FSKILL.md",[],[259,260,261,262,51,263,264,265,266,267,268,44,269,270,47,271,251,272,273,274],"infrastructure","tracking threat actor infrastructure","tracking","threat","monitoring","mitre-attack","threat-actor","threat-intelligence","command-and-control","dns","command","exploit","intelligence","domains","kit","hosts"]