[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ESDZMHASEDF558XBXBM8AE":3,"skill-same:01M6ESDZMHASEDF558XBXBM8AE":113},{"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":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6ESDZMHASEDF558XBXBM8AE","building-malware-incident-communication-template",null,"Build structured communication templates for malware incidents including stakeholder notifications, executive briefings, technical advisories, and regulatory disclosures with severity-based escalation procedures.","luokai0\u002Fai-agent-skills-by-luo-kai","luokai0","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F266954973?v=4","01M6E16VNT42JB8B3X3254QWJ7","luo kai","01M6E16VTFVP6S5XJF1V1MPV90",14,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F08-pinkpixel-collection\u002Fbuilding-malware-incident-communication-template\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"communication","incident","template","building malware incident communication template","malware","incident-communication","malware-response","stakeholder-notification","crisis-communication","executive-briefing","regulatory-disclosure","escalation","severity","notifications","technical","regulatory","build","cybersecurity","crisis","with","2026-11-10 10:12:30",false,"---\nname: building-malware-incident-communication-template\ndescription: Build structured communication templates for malware incidents including stakeholder notifications, executive briefings, technical advisories, and regulatory disclosures with severity-based escalation procedures.\ndomain: cybersecurity\nsubdomain: incident-response\ntags: [incident-communication, malware-response, stakeholder-notification, crisis-communication, executive-briefing, regulatory-disclosure]\nversion: \"1.0\"\nauthor: mahipal\nlicense: Apache-2.0\n---\n\n# Building Malware Incident Communication Template\n\n## Overview\n\nEffective communication during malware incidents is critical for coordinated response, stakeholder management, and regulatory compliance. A structured communication framework ensures the right people receive appropriate information at the right time, preventing panic while maintaining transparency. Communication templates should cover internal escalation, executive briefings, technical advisories for IT teams, customer notifications, regulatory disclosures, and media statements. The framework must account for different malware types (ransomware, wiper, trojan, worm) and severity levels that drive escalation speed and audience.\n\n\n## When to Use\n\n- When deploying or configuring building malware incident communication template 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\n- Familiarity with incident response concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Communication Framework\n\n### Severity Classification\n\n| Severity | Description | Notification Timeline | Audience |\n|----------|-------------|----------------------|----------|\n| P1 - Critical | Ransomware, wiper, or widespread infection affecting business operations | Within 15 minutes | CISO, CEO, Legal, Board (if applicable) |\n| P2 - High | Targeted malware on critical systems, data exfiltration suspected | Within 1 hour | CISO, IT Director, Legal |\n| P3 - Medium | Contained malware infection, limited spread | Within 4 hours | Security Manager, IT Director |\n| P4 - Low | Single endpoint infection, quickly contained | Within 24 hours | Security Team Lead |\n\n### Communication Channels\n\n| Channel | Use Case | Security Level |\n|---------|----------|---------------|\n| Out-of-band phone calls | Initial critical notifications | Highest |\n| Encrypted messaging (Signal) | Real-time IR team coordination | High |\n| Secure email (encrypted) | Formal notifications, documentation | High |\n| War room (physical\u002Fvirtual) | Ongoing incident coordination | Medium |\n| Incident ticketing system | Status tracking and documentation | Medium |\n| Company intranet | Broad employee communication | Standard |\n\n## Template 1: Initial Incident Notification (Internal)\n\n```\nSUBJECT: [SEVERITY] Malware Incident - Initial Notification - [DATE\u002FTIME UTC]\n\nCLASSIFICATION: CONFIDENTIAL - IR TEAM ONLY\n\nINCIDENT ID: IR-[YEAR]-[NUMBER]\nDETECTION TIME: [YYYY-MM-DD HH:MM UTC]\nNOTIFICATION TIME: [YYYY-MM-DD HH:MM UTC]\nSEVERITY: [P1\u002FP2\u002FP3\u002FP4]\n\nSUMMARY:\nA malware incident has been detected affecting [NUMBER] systems in\n[DEPARTMENT\u002FLOCATION]. The malware has been identified as [TYPE] with\n[KNOWN\u002FUNKNOWN] characteristics.\n\nCURRENT IMPACT:\n- Systems affected: [COUNT and DESCRIPTION]\n- Business functions impacted: [LIST]\n- Data at risk: [DESCRIPTION]\n- Current spread status: [CONTAINED\u002FSPREADING\u002FUNKNOWN]\n\nIMMEDIATE ACTIONS TAKEN:\n1. [ACTION - e.g., Affected endpoints isolated from network]\n2. [ACTION - e.g., EDR containment policies activated]\n3. [ACTION - e.g., Security team mobilized]\n\nNEXT STEPS:\n1. [PLANNED ACTION with TIMELINE]\n2. [PLANNED ACTION with TIMELINE]\n\nINCIDENT COMMANDER: [NAME]\nCONTACT: [PHONE\u002FENCRYPTED CHANNEL]\n\nNEXT UPDATE: [TIME] or sooner if situation changes\n\n---\nDo not forward this notification outside the IR team.\n```\n\n## Template 2: Executive Briefing\n\n```\nSUBJECT: Executive Briefing - Malware Incident IR-[YEAR]-[NUMBER]\n\nFOR: [CEO \u002F CISO \u002F CIO \u002F Board]\nFROM: [Incident Commander]\nDATE: [DATE]\nUPDATE: [#]\n\nSITUATION SUMMARY:\n[2-3 sentences describing the incident in business terms]\n\nBUSINESS IMPACT:\n- Revenue impact: [ESTIMATED\u002FNONE\u002FUNDER ASSESSMENT]\n- Operational impact: [DESCRIPTION]\n- Customer impact: [DESCRIPTION]\n- Regulatory implications: [DESCRIPTION]\n\nCURRENT STATUS: [DETECTED \u002F CONTAINED \u002F ERADICATING \u002F RECOVERING]\n\nKEY DECISIONS NEEDED:\n1. [DECISION with context and recommendation]\n2. [DECISION with context and recommendation]\n\nTIMELINE:\n- [TIME]: Incident detected\n- [TIME]: Containment initiated\n- [TIME]: [MILESTONE]\n- [TIME]: Estimated recovery (if known)\n\nEXTERNAL COMMUNICATION STATUS:\n- Regulatory notification: [REQUIRED\u002FSUBMITTED\u002FNOT REQUIRED]\n- Customer notification: [REQUIRED\u002FPLANNED\u002FNOT REQUIRED]\n- Law enforcement: [ENGAGED\u002FPLANNED\u002FNOT APPLICABLE]\n\nRESOURCE REQUIREMENTS:\n- [RESOURCE NEED - e.g., External IR firm engagement]\n- [RESOURCE NEED - e.g., Additional hardware for rebuild]\n\nNEXT UPDATE: [TIME]\n```\n\n## Template 3: Technical Advisory for IT Teams\n\n```\nSUBJECT: TECHNICAL ADVISORY - [MALWARE NAME] - Immediate Action Required\n\nSEVERITY: [CRITICAL\u002FHIGH\u002FMEDIUM]\nDATE: [DATE\u002FTIME UTC]\nADVISORY ID: TA-[YEAR]-[NUMBER]\n\nTHREAT DESCRIPTION:\n[Technical description of the malware, behavior, and indicators]\n\nAFFECTED SYSTEMS:\n- Operating Systems: [LIST]\n- Applications: [LIST]\n- Network segments: [LIST]\n\nINDICATORS OF COMPROMISE (IOCs):\nFile Hashes:\n  MD5: [HASH]\n  SHA256: [HASH]\n\nFile Names:\n  [FILENAME]\n\nNetwork Indicators:\n  C2 Domains: [DOMAIN]\n  C2 IPs: [IP ADDRESS]\n  User-Agent: [STRING]\n\nRegistry Keys:\n  [REGISTRY PATH]\n\nDETECTION METHODS:\n- EDR: [DETECTION RULE\u002FSIGNATURE]\n- SIEM: [CORRELATION RULE]\n- Network: [IDS\u002FIPS SIGNATURE]\n\nREQUIRED ACTIONS:\nPriority 1 (Immediate):\n  [ ] Block IOCs at firewall\u002Fproxy\n  [ ] Push EDR containment rules\n  [ ] Scan all endpoints for IOCs\n\nPriority 2 (Within 4 hours):\n  [ ] Apply patches [KB\u002FCVE NUMBER]\n  [ ] Update antivirus signatures\n  [ ] Review logs for historical indicators\n\nPriority 3 (Within 24 hours):\n  [ ] Conduct enterprise-wide hunt\n  [ ] Validate backup integrity\n  [ ] Update detection rules\n\nCONTACT: SOC - [PHONE] | Security Engineering - [PHONE]\n```\n\n## Template 4: Regulatory Notification\n\n```\n[ORGANIZATION LETTERHEAD]\n\n[REGULATORY BODY]\n[ADDRESS]\n\nDate: [DATE]\n\nRE: Data Security Incident Notification - [REFERENCE NUMBER]\n\nDear [TITLE\u002FNAME],\n\nPursuant to [REGULATION - e.g., GDPR Article 33, State Breach Notification Law],\n[ORGANIZATION] is providing notification of a data security incident.\n\nINCIDENT SUMMARY:\nOn [DATE], [ORGANIZATION] detected a malware incident affecting systems containing\n[TYPE OF DATA]. The incident was detected through [DETECTION METHOD].\n\nDATA POTENTIALLY AFFECTED:\n- Types of data: [PERSONAL DATA, FINANCIAL, HEALTH, etc.]\n- Number of individuals: [COUNT or ESTIMATE]\n- Categories of individuals: [CUSTOMERS, EMPLOYEES, etc.]\n\nTIMELINE:\n- [DATE]: Incident occurred (estimated)\n- [DATE]: Incident detected\n- [DATE]: Containment achieved\n- [DATE]: This notification\n\nMEASURES TAKEN:\n1. [CONTAINMENT ACTION]\n2. [INVESTIGATION ACTION]\n3. [REMEDIATION ACTION]\n\nMEASURES TO MITIGATE ADVERSE EFFECTS:\n1. [MITIGATION - e.g., Credit monitoring offered]\n2. [MITIGATION - e.g., Password resets enforced]\n\nCONTACT INFORMATION:\n[DPO\u002FPRIVACY OFFICER NAME]\n[TITLE]\n[EMAIL]\n[PHONE]\n\nRespectfully,\n[SIGNATORY]\n[TITLE]\n```\n\n## Template 5: Customer\u002FPublic Notification\n\n```\nSUBJECT: Important Security Notice from [ORGANIZATION]\n\nDear [CUSTOMER\u002FUSER],\n\nWe are writing to inform you of a security incident that may have affected\nyour information.\n\nWHAT HAPPENED:\nOn [DATE], we detected unauthorized activity on our systems involving\nmalicious software. We immediately activated our incident response procedures\nand engaged leading cybersecurity experts to investigate.\n\nWHAT INFORMATION WAS INVOLVED:\nBased on our investigation, the following types of information may have\nbeen affected: [LIST - e.g., names, email addresses, etc.]\n\nWHAT WE ARE DOING:\n- We have contained the incident and removed the malicious software\n- We have engaged [FORENSIC FIRM] to conduct a thorough investigation\n- We have enhanced our security controls to prevent similar incidents\n- We have notified relevant regulatory authorities\n\nWHAT YOU CAN DO:\n- Change your password for your [ORGANIZATION] account\n- Enable multi-factor authentication if not already active\n- Monitor your accounts for unusual activity\n- [Additional specific recommendations]\n\nADDITIONAL RESOURCES:\n- [DEDICATED SUPPORT LINE]\n- [FAQ PAGE URL]\n- [CREDIT MONITORING ENROLLMENT - if applicable]\n\nWe sincerely apologize for any concern this may cause and remain committed\nto protecting your information.\n\n[SIGNATORY]\n[TITLE]\n```\n\n## Communication Workflow\n\n### Escalation Matrix\n```\nMalware Detected\n  |\n  v\n[Classify Severity: P1\u002FP2\u002FP3\u002FP4]\n  |\n  |-- P1: Notify within 15 min\n  |     |-- Incident Commander\n  |     |-- CISO (phone call)\n  |     |-- CEO (phone call)\n  |     |-- Legal Counsel\n  |     |-- External IR firm\n  |     |-- Law enforcement (if applicable)\n  |\n  |-- P2: Notify within 1 hour\n  |     |-- CISO\n  |     |-- IT Director\n  |     |-- Legal Counsel\n  |\n  |-- P3: Notify within 4 hours\n  |     |-- Security Manager\n  |     |-- IT Director\n  |\n  |-- P4: Notify within 24 hours\n        |-- Security Team Lead\n```\n\n## References\n\n- NIST SP 800-61 Rev 2: Incident Communication Guidelines\n- GDPR Article 33: Data Breach Notification Requirements\n- SANS Incident Handler's Handbook: Communication Best Practices\n- CISA Incident Reporting Guidelines\n","# Building Malware Incident Communication Template\n\n## Overview\n\nEffective communication during malware incidents is critical for coordinated response, stakeholder management, and regulatory compliance. A structured communication framework ensures the right people receive appropriate information at the right time, preventing panic while maintaining transparency. Communication templates should cover internal escalation, executive briefings, technical advisories for IT teams, customer notifications, regulatory disclosures, and media statements. The framework must account for different malware types (ransomware, wiper, trojan, worm) and severity levels that drive escalation speed and audience.\n\n\n## When to Use\n\n- When deploying or configuring building malware incident communication template 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\n- Familiarity with incident response concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Communication Framework\n\n### Severity Classification\n\n| Severity | Description | Notification Timeline | Audience |\n|----------|-------------|----------------------|----------|\n| P1 - Critical | Ransomware, wiper, or widespread infection affecting business operations | Within 15 minutes | CISO, CEO, Legal, Board (if applicable) |\n| P2 - High | Targeted malware on critical systems, data exfiltration suspected | Within 1 hour | CISO, IT Director, Legal |\n| P3 - Medium | Contained malware infection, limited spread | Within 4 hours | Security Manager, IT Director |\n| P4 - Low | Single endpoint infection, quickly contained | Within 24 hours | Security Team Lead |\n\n### Communication Channels\n\n| Channel | Use Case | Security Level |\n|---------|----------|---------------|\n| Out-of-band phone calls | Initial critical notifications | Highest |\n| Encrypted messaging (Signal) | Real-time IR team coordination | High |\n| Secure email (encrypted) | Formal notifications, documentation | High |\n| War room (physical\u002Fvirtual) | Ongoing incident coordination | Medium |\n| Incident ticketing system | Status tracking and documentation | Medium |\n| Company intranet | Broad employee communication | Standard |\n\n## Template 1: Initial Incident Notification (Internal)\n\n```\nSUBJECT: [SEVERITY] Malware Incident - Initial Notification - [DATE\u002FTIME UTC]\n\nCLASSIFICATION: CONFIDENTIAL - IR TEAM ONLY\n\nINCIDENT ID: IR-[YEAR]-[NUMBER]\nDETECTION TIME: [YYYY-MM-DD HH:MM UTC]\nNOTIFICATION TIME: [YYYY-MM-DD HH:MM UTC]\nSEVERITY: [P1\u002FP2\u002FP3\u002FP4]\n\nSUMMARY:\nA malware incident has been detected affecting [NUMBER] systems in\n[DEPARTMENT\u002FLOCATION]. The malware has been identified as [TYPE] with\n[KNOWN\u002FUNKNOWN] characteristics.\n\nCURRENT IMPACT:\n- Systems affected: [COUNT and DESCRIPTION]\n- Business functions impacted: [LIST]\n- Data at risk: [DESCRIPTION]\n- Current spread status: [CONTAINED\u002FSPREADING\u002FUNKNOWN]\n\nIMMEDIATE ACTIONS TAKEN:\n1. [ACTION - e.g., Affected endpoints isolated from network]\n2. [ACTION - e.g., EDR containment policies activated]\n3. [ACTION - e.g., Security team mobilized]\n\nNEXT STEPS:\n1. [PLANNED ACTION with TIMELINE]\n2. [PLANNED ACTION with TIMELINE]\n\nINCIDENT COMMANDER: [NAME]\nCONTACT: [PHONE\u002FENCRYPTED CHANNEL]\n\nNEXT UPDATE: [TIME] or sooner if situation changes\n\n---\nDo not forward this notification outside the IR team.\n```\n\n## Template 2: Executive Briefing\n\n```\nSUBJECT: Executive Briefing - Malware Incident IR-[YEAR]-[NUMBER]\n\nFOR: [CEO \u002F CISO \u002F CIO \u002F Board]\nFROM: [Incident Commander]\nDATE: [DATE]\nUPDATE: [#]\n\nSITUATION SUMMARY:\n[2-3 sentences describing the incident in business terms]\n\nBUSINESS IMPACT:\n- Revenue impact: [ESTIMATED\u002FNONE\u002FUNDER ASSESSMENT]\n- Operational impact: [DESCRIPTION]\n- Customer impact: [DESCRIPTION]\n- Regulatory implications: [DESCRIPTION]\n\nCURRENT STATUS: [DETECTED \u002F CONTAINED \u002F ERADICATING \u002F RECOVERING]\n\nKEY DECISIONS NEEDED:\n1. [DECISION with context and recommendation]\n2. [DECISION with context and recommendation]\n\nTIMELINE:\n- [TIME]: Incident detected\n- [TIME]: Containment initiated\n- [TIME]: [MILESTONE]\n- [TIME]: Estimated recovery (if known)\n\nEXTERNAL COMMUNICATION STATUS:\n- Regulatory notification: [REQUIRED\u002FSUBMITTED\u002FNOT REQUIRED]\n- Customer notification: [REQUIRED\u002FPLANNED\u002FNOT REQUIRED]\n- Law enforcement: [ENGAGED\u002FPLANNED\u002FNOT APPLICABLE]\n\nRESOURCE REQUIREMENTS:\n- [RESOURCE NEED - e.g., External IR firm engagement]\n- [RESOURCE NEED - e.g., Additional hardware for rebuild]\n\nNEXT UPDATE: [TIME]\n```\n\n## Template 3: Technical Advisory for IT Teams\n\n```\nSUBJECT: TECHNICAL ADVISORY - [MALWARE NAME] - Immediate Action Required\n\nSEVERITY: [CRITICAL\u002FHIGH\u002FMEDIUM]\nDATE: [DATE\u002FTIME UTC]\nADVISORY ID: TA-[YEAR]-[NUMBER]\n\nTHREAT DESCRIPTION:\n[Technical description of the malware, behavior, and indicators]\n\nAFFECTED SYSTEMS:\n- Operating Systems: [LIST]\n- Applications: [LIST]\n- Network segments: [LIST]\n\nINDICATORS OF COMPROMISE (IOCs):\nFile Hashes:\n  MD5: [HASH]\n  SHA256: [HASH]\n\nFile Names:\n  [FILENAME]\n\nNetwork Indicators:\n  C2 Domains: [DOMAIN]\n  C2 IPs: [IP ADDRESS]\n  User-Agent: [STRING]\n\nRegistry Keys:\n  [REGISTRY PATH]\n\nDETECTION METHODS:\n- EDR: [DETECTION RULE\u002FSIGNATURE]\n- SIEM: [CORRELATION RULE]\n- Network: [IDS\u002FIPS SIGNATURE]\n\nREQUIRED ACTIONS:\nPriority 1 (Immediate):\n  [ ] Block IOCs at firewall\u002Fproxy\n  [ ] Push EDR containment rules\n  [ ] Scan all endpoints for IOCs\n\nPriority 2 (Within 4 hours):\n  [ ] Apply patches [KB\u002FCVE NUMBER]\n  [ ] Update antivirus signatures\n  [ ] Review logs for historical indicators\n\nPriority 3 (Within 24 hours):\n  [ ] Conduct enterprise-wide hunt\n  [ ] Validate backup integrity\n  [ ] Update detection rules\n\nCONTACT: SOC - [PHONE] | Security Engineering - [PHONE]\n```\n\n## Template 4: Regulatory Notification\n\n```\n[ORGANIZATION LETTERHEAD]\n\n[REGULATORY BODY]\n[ADDRESS]\n\nDate: [DATE]\n\nRE: Data Security Incident Notification - [REFERENCE NUMBER]\n\nDear [TITLE\u002FNAME],\n\nPursuant to [REGULATION - e.g., GDPR Article 33, State Breach Notification Law],\n[ORGANIZATION] is providing notification of a data security incident.\n\nINCIDENT SUMMARY:\nOn [DATE], [ORGANIZATION] detected a malware incident affecting systems containing\n[TYPE OF DATA]. The incident was detected through [DETECTION METHOD].\n\nDATA POTENTIALLY AFFECTED:\n- Types of data: [PERSONAL DATA, FINANCIAL, HEALTH, etc.]\n- Number of individuals: [COUNT or ESTIMATE]\n- Categories of individuals: [CUSTOMERS, EMPLOYEES, etc.]\n\nTIMELINE:\n- [DATE]: Incident occurred (estimated)\n- [DATE]: Incident detected\n- [DATE]: Containment achieved\n- [DATE]: This notification\n\nMEASURES TAKEN:\n1. [CONTAINMENT ACTION]\n2. [INVESTIGATION ACTION]\n3. [REMEDIATION ACTION]\n\nMEASURES TO MITIGATE ADVERSE EFFECTS:\n1. [MITIGATION - e.g., Credit monitoring offered]\n2. [MITIGATION - e.g., Password resets enforced]\n\nCONTACT INFORMATION:\n[DPO\u002FPRIVACY OFFICER NAME]\n[TITLE]\n[EMAIL]\n[PHONE]\n\nRespectfully,\n[SIGNATORY]\n[TITLE]\n```\n\n## Template 5: Customer\u002FPublic Notification\n\n```\nSUBJECT: Important Security Notice from [ORGANIZATION]\n\nDear [CUSTOMER\u002FUSER],\n\nWe are writing to inform you of a security incident that may have affected\nyour information.\n\nWHAT HAPPENED:\nOn [DATE], we detected unauthorized activity on our systems involving\nmalicious software. We immediately activated our incident response procedures\nand engaged leading cybersecurity experts to investigate.\n\nWHAT INFORMATION WAS INVOLVED:\nBased on our investigation, the following types of information may have\nbeen affected: [LIST - e.g., names, email addresses, etc.]\n\nWHAT WE ARE DOING:\n- We have contained the incident and removed the malicious software\n- We have engaged [FORENSIC FIRM] to conduct a thorough investigation\n- We have enhanced our security controls to prevent similar incidents\n- We have notified relevant regulatory authorities\n\nWHAT YOU CAN DO:\n- Change your password for your [ORGANIZATION] account\n- Enable multi-factor authentication if not already active\n- Monitor your accounts for unusual activity\n- [Additional specific recommendations]\n\nADDITIONAL RESOURCES:\n- [DEDICATED SUPPORT LINE]\n- [FAQ PAGE URL]\n- [CREDIT MONITORING ENROLLMENT - if applicable]\n\nWe sincerely apologize for any concern this may cause and remain committed\nto protecting your information.\n\n[SIGNATORY]\n[TITLE]\n```\n\n## Communication Workflow\n\n### Escalation Matrix\n```\nMalware Detected\n  |\n  v\n[Classify Severity: P1\u002FP2\u002FP3\u002FP4]\n  |\n  |-- P1: Notify within 15 min\n  |     |-- Incident Commander\n  |     |-- CISO (phone call)\n  |     |-- CEO (phone call)\n  |     |-- Legal Counsel\n  |     |-- External IR firm\n  |     |-- Law enforcement (if applicable)\n  |\n  |-- P2: Notify within 1 hour\n  |     |-- CISO\n  |     |-- IT Director\n  |     |-- Legal Counsel\n  |\n  |-- P3: Notify within 4 hours\n  |     |-- Security Manager\n  |     |-- IT Director\n  |\n  |-- P4: Notify within 24 hours\n        |-- Security Team Lead\n```\n\n## References\n\n- NIST SP 800-61 Rev 2: Incident Communication Guidelines\n- GDPR Article 33: Data Breach Notification Requirements\n- SANS Incident Handler's Handbook: Communication Best Practices\n- CISA Incident Reporting Guidelines\n",{"name":5,"tags":44,"author":45,"domain":36,"license":15,"version":46,"subdomain":47,"description":7},[24,25,26,27,28,29],"mahipal","1.0","incident-response","main","4d2fb89cdfb75f3f6fd3c6c5ec9ad90ea129eb3c","ai-agent-skills\u002F21-external-registries\u002F08-pinkpixel-collection\u002Fbuilding-malware-incident-communication-template",2,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai","https:\u002F\u002Fgithub.com\u002Fluokai0","a solo builder.","2026-05-06 04:29:04",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add luokai0\u002Fai-agent-skills-by-luo-kai --skill building-malware-incident-communication-template",{"tool":62,"command":63},"bunx","bunx skills add luokai0\u002Fai-agent-skills-by-luo-kai --skill building-malware-incident-communication-template",{"tool":65,"command":66},"pnpm","pnpm dlx skills add luokai0\u002Fai-agent-skills-by-luo-kai --skill building-malware-incident-communication-template","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F08-pinkpixel-collection\u002Fbuilding-malware-incident-communication-template\u002FSKILL.md",true,[70,76,81,87,91,95,99,105,109],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"assets\u002Ftemplate.md","ASSET","资产文件",1354,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F08-pinkpixel-collection\u002Fbuilding-malware-incident-communication-template\u002Fassets\u002Ftemplate.md",{"path":77,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F08-pinkpixel-collection\u002Fbuilding-malware-incident-communication-template\u002FLICENSE",{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fapi-reference.md","REFERENCE","参考文档",2204,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F08-pinkpixel-collection\u002Fbuilding-malware-incident-communication-template\u002Freferences\u002Fapi-reference.md",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fslack-tasks.md",8605,"https:\u002F\u002Fgithub.com\u002FAkaraChen\u002Fangel-engine\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fslack\u002Freferences\u002Fslack-tasks.md",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fstandards.md",1204,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F08-pinkpixel-collection\u002Fbuilding-malware-incident-communication-template\u002Freferences\u002Fstandards.md",{"path":96,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fworkflows.md",2388,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F08-pinkpixel-collection\u002Fbuilding-malware-incident-communication-template\u002Freferences\u002Fworkflows.md",{"path":100,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"scripts\u002Fagent.py","SCRIPT","脚本",8774,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F08-pinkpixel-collection\u002Fbuilding-malware-incident-communication-template\u002Fscripts\u002Fagent.py",{"path":106,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":107,"sourceHtmlUrl":108},"scripts\u002Fprocess.py",10488,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F08-pinkpixel-collection\u002Fbuilding-malware-incident-communication-template\u002Fscripts\u002Fprocess.py",{"path":110,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":111,"sourceHtmlUrl":112},"templates\u002Fslack-report-template.md",3621,"https:\u002F\u002Fgithub.com\u002FAkaraChen\u002Fangel-engine\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fslack\u002Ftemplates\u002Fslack-report-template.md",[114,142,159,188,219,256],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":118,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":39},"01M6F2SKTE208174C7S7JJCZC7","write-contracts","Generates secure Aptos Move V2 smart contracts with Object model, Digital Asset integration, security patterns, and storage type guidance. Includes comprehensive storage decision framework for optimal data structure selection. Triggers on: 'write contract', 'create NFT collection', 'build marketplace', 'implement minting', 'generate Move module', 'create token contract', 'build DAO', 'implement staking'. Ask storage questions when: 'store', 'track', 'registry', 'mapping', 'list', 'collection'.","MIT","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fwrite-contracts\u002FSKILL.md",[],[122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141],"write","contracts","write contracts","storage","secure","create","generate","collection","model","decision","ask","smart-contracts","selection","objects","structure","nft","token","aptos","critical","move",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":118,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":39},"01M6F2RFXJ6T9MKW0A7N7GM45B","web-search","通用网络搜索技能，支持多引擎搜索（百度、必应、DuckDuckGo），无需API密钥即可获取实时信息","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fweb-search-ex-skill\u002FSKILL.md",[],[149,150,151,152,153,154,155,156,157,158],"web","search","web search","搜索","baidu","bing","duckduckgo","百度","多引擎","internet",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":118,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":170,"publishedAt":39},"01M6F2K968G1FZEZFPW2E6B222","solo-build","Execute implementation plan tasks with TDD workflow, auto-commit, and phase gates. Use when user says \"build it\", \"start building\", \"execute plan\", \"implement tasks\", \"ship it\", or references a track ID. Do NOT use for planning (use \u002Fplan) or scaffolding (use \u002Fscaffold).","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fsolo-build\u002FSKILL.md",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":168,"taxonomyTypeDesc":169},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[35,171,172,173,174,175,176,177,150,178,179,180,122,181,182,183,184,185,186,187],"solo","solo build","MCP","workflow","commit","tasks","code","Bash","plan","read","auto","references","context7","query","scaffolding","ship it","project",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":118,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":200,"publishedAt":39},"01M6F2GKN39SGHSPWYB3662YC8","react-email","Use when building HTML email templates with React components, adding a visual email editor to an application using the React Email visual editor, rendering emails to HTML, or sending emails with Resend. Covers welcome emails, password resets, notifications, order confirmations, newsletters, transactional emails, and the embeddable email editor component.","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Freact-email-skills\u002FSKILL.md",[194,197],{"categoryNo":195,"categoryName":196,"taxonomyType":168,"taxonomyTypeDesc":169},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":198,"categoryName":199,"taxonomyType":168,"taxonomyTypeDesc":169},"01JBSEEDCAT000000000000009","前端开发",[201,202,203,204,205,206,207,208,209,210,32,211,212,213,214,215,216,217,218,38],"react","email","react email","github","editor","components","react components","component","welcome","https","password","node","use","html","resend","visual","emails","rendering",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":118,"licenseFileUrl":6,"sourceHtmlUrl":223,"categories":224,"keywords":237,"publishedAt":39},"01M6F2FBVGVDFSG8SSFJGXA40C","APITester Agent-Driven API Testing","Test API endpoints and document responses. Define tests in plain English, run them, get formatted results. Agent-driven Postman alternative.","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fopenclaw-api-tester\u002FSKILL.md",[225,228,231,232],{"categoryNo":226,"categoryName":227,"taxonomyType":168,"taxonomyTypeDesc":169},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":229,"categoryName":230,"taxonomyType":168,"taxonomyTypeDesc":169},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":166,"categoryName":167,"taxonomyType":168,"taxonomyTypeDesc":169},{"categoryNo":233,"categoryName":234,"taxonomyType":235,"taxonomyTypeDesc":236},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[238,239,240,241,242,243,244,245,246,247,248,249,250,251,252,253,254,255],"testing","api","api testing","driven","APITester Agent Driven API Testing","test","run","postman","results","plain english","tester","endpoints","document","get","define","tests","english","api-tester",{"skillNo":257,"name":258,"nameZh":6,"description":259,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":118,"licenseFileUrl":6,"sourceHtmlUrl":260,"categories":261,"keywords":262,"publishedAt":39},"01M6F273Y3NGAPVJZ608BC0G9G","hubspot-implementation-plan","Generate a phased implementation plan from a HubSpot audit report. Creates prioritized, sequenced cleanup processes with effort estimates, dependencies, and automation feasibility. Use after running \u002Fhubspot-audit.","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fhubspot-implementation-plan\u002FSKILL.md",[],[179,263,264,265,266,267,268,128,269,270,271,272,273,213,274,275,38,276],"implementation","hubspot","hubspot implementation plan","automation","feasibility","cleanup","planning","report","audit","audit report","phased implementation","dependencies","processes","hubspot audit"]