[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EKAZQSM2JA2XSWVAFB3YZ5":3,"skill-same:01M7EKAZQSM2JA2XSWVAFB3YZ5":48},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7EKAZQSM2JA2XSWVAFB3YZ5","hunt-clickjacking",null,"Hunt Clickjacking — missing X-Frame-Options \u002F CSP frame-ancestors lets an attacker embed the target page in an invisible iframe and trick victims into clicking buttons they cannot see (UI redressing). Targets: login flows, money transfers, account settings, OAuth confirmation pages. Confirm by fetching the page, then PROVE it frames in a real browser and a sensitive state-changing action survives the cross-site context (SameSite cookies \u002F framebusting JS can defeat it) — header-absence alone is not a finding.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fhunt-clickjacking\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: hunt-clickjacking\ndescription: \"Hunt Clickjacking — missing X-Frame-Options \u002F CSP frame-ancestors lets an attacker embed the target page in an invisible iframe and trick victims into clicking buttons they cannot see (UI redressing). Targets: login flows, money transfers, account settings, OAuth confirmation pages. Confirm by fetching the page, then PROVE it frames in a real browser and a sensitive state-changing action survives the cross-site context (SameSite cookies \u002F framebusting JS can defeat it) — header-absence alone is not a finding.\"\nsources: hackerone_public, public_research\nreport_count: 6\n---\n\n## What is Clickjacking\n\nClickjacking (UI Redressing) lets an attacker load a target page inside a transparent iframe on a malicious site. The victim sees the attacker's decoy UI but clicks the hidden target UI beneath it. No JavaScript on the target is required.\n\n**Highest-value targets:**\n- Login \u002F authentication pages — force login with attacker credentials\n- Money transfer \u002F checkout \u002F \"confirm payment\" buttons\n- Account settings (email change, password change, 2FA disable)\n- OAuth \u002F social-login \"Authorize app\" confirmation dialogs\n- Admin actions (delete, promote user, change role)\n\n## Protection Headers\n\nTwo mechanisms prevent framing:\n\n```\nX-Frame-Options: DENY              # strongest — blocks all framing\nX-Frame-Options: SAMEORIGIN        # allows same-origin frames only\nContent-Security-Policy: frame-ancestors 'none'     # CSP equivalent of DENY\nContent-Security-Policy: frame-ancestors 'self'     # CSP equivalent of SAMEORIGIN\n```\n\nIf NEITHER is present, the page is frameable from any origin.\n\n## How to Test\n\nHeader-absence is the **trigger for investigation, not the finding**. Two steps:\n\n**Step 1 — Header check (screening).** Fetch the target page and inspect the response headers:\n\n```\ncurl -sI https:\u002F\u002Ftarget.example\u002Faccount\u002Ftransfer | grep -iE 'x-frame-options|content-security-policy'\n```\nIf BOTH `X-Frame-Options` and CSP `frame-ancestors` are absent, the page is a *candidate*. If either is present and restrictive (`DENY`\u002F`SAMEORIGIN`\u002F`frame-ancestors 'none'|'self'`), stop — it's protected.\n\n**Step 2 — Prove it actually frames and clicks (required for a real finding).** Build a minimal PoC and load it in a real browser:\n\n```html\n\u003C!doctype html>\n\u003Ch1>Win a prize — click below\u003C\u002Fh1>\n\u003Ciframe src=\"https:\u002F\u002Ftarget.example\u002Faccount\u002Ftransfer\"\n        style=\"opacity:0.1;position:absolute;top:0;left:0;width:1000px;height:800px\">\u003C\u002Fiframe>\n```\nConfirm ALL of the following, or it is not exploitable:\n- The page **actually renders inside the iframe** (no framebusting JS that blanks\u002Fredirects it — e.g. `if(top!==self)` breakout, or a `Sec-Fetch-Dest`\u002FJS frame check).\n- The **sensitive action still works while framed** — critically, the action must succeed *cross-site*. If it relies on a session cookie set `SameSite=Lax` or `SameSite=Strict` (the modern default), the cookie is **not** sent on the cross-site framed request, and the clickjack fails. Verify the victim's authenticated state carries into the frame.\n- The target is a **state-changing action** (transfer, settings\u002Femail\u002Fpassword change, 2FA disable, OAuth authorize, admin action), not a read-only page.\n\n**Strategy:** target the most sensitive action pages first — severity scales directly with what the victim is tricked into doing.\n\n## False Positives\n\n- Public, read-only pages (home\u002Fmarketing) lacking frame protection are low\u002Finformational — no sensitive action to redress.\n- APIs and non-HTML endpoints (JSON, images) are not clickjacking targets.\n- **Header-absence alone is NOT a finding.** SameSite cookies, framebusting JS, or the lack of any sensitive framed action can each fully defeat it — which is why Step 2 is mandatory.\n\n## Proof Requirements\n\nA valid clickjacking report shows: (1) the target page rendered inside an attacker-controlled iframe in a real browser, (2) a sensitive state-changing action reachable by a framed click while the victim is authenticated (cookies survive the cross-site context), and (3) a screenshot\u002Frecording of the overlay. Reporting missing headers with no working frame PoC is a documentation-quality issue, not a vulnerability.\n","## What is Clickjacking\n\nClickjacking (UI Redressing) lets an attacker load a target page inside a transparent iframe on a malicious site. The victim sees the attacker's decoy UI but clicks the hidden target UI beneath it. No JavaScript on the target is required.\n\n**Highest-value targets:**\n- Login \u002F authentication pages — force login with attacker credentials\n- Money transfer \u002F checkout \u002F \"confirm payment\" buttons\n- Account settings (email change, password change, 2FA disable)\n- OAuth \u002F social-login \"Authorize app\" confirmation dialogs\n- Admin actions (delete, promote user, change role)\n\n## Protection Headers\n\nTwo mechanisms prevent framing:\n\n```\nX-Frame-Options: DENY              # strongest — blocks all framing\nX-Frame-Options: SAMEORIGIN        # allows same-origin frames only\nContent-Security-Policy: frame-ancestors 'none'     # CSP equivalent of DENY\nContent-Security-Policy: frame-ancestors 'self'     # CSP equivalent of SAMEORIGIN\n```\n\nIf NEITHER is present, the page is frameable from any origin.\n\n## How to Test\n\nHeader-absence is the **trigger for investigation, not the finding**. Two steps:\n\n**Step 1 — Header check (screening).** Fetch the target page and inspect the response headers:\n\n```\ncurl -sI https:\u002F\u002Ftarget.example\u002Faccount\u002Ftransfer | grep -iE 'x-frame-options|content-security-policy'\n```\nIf BOTH `X-Frame-Options` and CSP `frame-ancestors` are absent, the page is a *candidate*. If either is present and restrictive (`DENY`\u002F`SAMEORIGIN`\u002F`frame-ancestors 'none'|'self'`), stop — it's protected.\n\n**Step 2 — Prove it actually frames and clicks (required for a real finding).** Build a minimal PoC and load it in a real browser:\n\n```html\n\u003C!doctype html>\n\u003Ch1>Win a prize — click below\u003C\u002Fh1>\n\u003Ciframe src=\"https:\u002F\u002Ftarget.example\u002Faccount\u002Ftransfer\"\n        style=\"opacity:0.1;position:absolute;top:0;left:0;width:1000px;height:800px\">\u003C\u002Fiframe>\n```\nConfirm ALL of the following, or it is not exploitable:\n- The page **actually renders inside the iframe** (no framebusting JS that blanks\u002Fredirects it — e.g. `if(top!==self)` breakout, or a `Sec-Fetch-Dest`\u002FJS frame check).\n- The **sensitive action still works while framed** — critically, the action must succeed *cross-site*. If it relies on a session cookie set `SameSite=Lax` or `SameSite=Strict` (the modern default), the cookie is **not** sent on the cross-site framed request, and the clickjack fails. Verify the victim's authenticated state carries into the frame.\n- The target is a **state-changing action** (transfer, settings\u002Femail\u002Fpassword change, 2FA disable, OAuth authorize, admin action), not a read-only page.\n\n**Strategy:** target the most sensitive action pages first — severity scales directly with what the victim is tricked into doing.\n\n## False Positives\n\n- Public, read-only pages (home\u002Fmarketing) lacking frame protection are low\u002Finformational — no sensitive action to redress.\n- APIs and non-HTML endpoints (JSON, images) are not clickjacking targets.\n- **Header-absence alone is NOT a finding.** SameSite cookies, framebusting JS, or the lack of any sensitive framed action can each fully defeat it — which is why Step 2 is mandatory.\n\n## Proof Requirements\n\nA valid clickjacking report shows: (1) the target page rendered inside an attacker-controlled iframe in a real browser, (2) a sensitive state-changing action reachable by a framed click while the victim is authenticated (cookies survive the cross-site context), and (3) a screenshot\u002Frecording of the overlay. Reporting missing headers with no working frame PoC is a documentation-quality issue, not a vulnerability.\n",{"name":5,"sources":24,"description":7,"report_count":25},"hackerone_public, public_research",6,"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fhunt-clickjacking",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill hunt-clickjacking",{"tool":40,"command":41},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill hunt-clickjacking",{"tool":43,"command":44},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill hunt-clickjacking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fhunt-clickjacking\u002FSKILL.md",true,[],[49,57,62,69,76,83],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":56},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":58,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":56},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":56},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":56},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":56},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":56},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]