Browser Exploitation logo

Browser Exploitation

Community
hypnguyen1209
browser-exploitation

Use when building a client-side browser exploit — V8/JSC JIT type confusion to renderer R/W, V8 heap-sandbox escape, renderer-to-browser sandbox escape (Mojo IPC, GPU/Dawn/ANGLE), Electron/webview IPC abuse, 1-click RCE chains

Overview

Publisherhypnguyen1209
Repositoryoffensive-claude
Skill namebrowser-exploitation
Stars
396
Forks
71
Bundled files
11
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 11 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by hypnguyen1209 on GitHub. Read the source before you install it.

Installation

Install the Browser Exploitation AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/hypnguyen1209/offensive-claude/tree/main/skills/browser-exploitation
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/hypnguyen1209/offensive-claude.git /tmp/offensive-claude
mkdir -p .claude/skills
cp -r /tmp/offensive-claude/skills/browser-exploitation .claude/skills/browser-exploitation
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Browser Exploitation in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Browser Exploitation on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Browser Exploitation is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Browser & Client-Side Exploitation

Turn a single client-side bug into full host compromise. The modern browser is a chain target: a JS-engine bug yields an in-renderer arbitrary read/write, the V8 heap sandbox must be escaped to get a native R/W, then a second logic/memory bug in a privileged process (browser broker, GPU) escapes the OS sandbox. Electron and embedded webviews collapse several of these steps. Every cluster pairs the offensive primitive with renderer-crash/IPC telemetry, Sigma/EDR detection, and cleanup OPSEC.

When to Activate

  • A V8/JavaScriptCore bug (type confusion, OOB, UAF, JIT mis-speculation) must become addrof/fakeobj and an in-renderer arbitrary R/W.
  • An in-renderer R/W exists but is trapped inside the V8 heap sandbox (pointer compression) and needs a trusted-pointer / Wasm-object escape to native memory.
  • A renderer is fully compromised and you need to escape the OS sandbox via Mojo IPC handle/logic bugs or the GPU process (Dawn/WebGPU, ANGLE).
  • Auditing or exploiting an Electron / CEF / WebView2 app: contextIsolation/nodeIntegration/sandbox misconfig, preload-bridge & IPC abuse, ASAR/fuse/snapshot tampering.
  • Assembling a 1-click drive-by RCE chain (renderer → sandbox escape → host) for an authorized red-team delivery, or doing cross-engine (Safari/JSC) work.
  • Patch-diffing a Chrome/V8/WebKit security release to build an n-day client-side exploit.

Technique Map

TechniqueATT&CKCWEReferenceScript
JIT type confusion (TurboFan/Maglev/Turboshaft)T1203CWE-843references/v8-jit-typeconfusion.mdscripts/v8_typer.js
Element-kind confusion -> addrof/fakeobjT1203CWE-843references/v8-jit-typeconfusion.mdscripts/v8_typer.js
OOB read/write on JSArray/TypedArrayT1203CWE-787references/v8-jit-typeconfusion.mdscripts/v8_typer.js
In-renderer arbitrary R/W (fake TypedArray)T1203CWE-787references/v8-jit-typeconfusion.mdscripts/v8_typer.js
V8 heap-sandbox escape via raw Wasm pointerT1203CWE-787references/v8-sandbox-escape.mdscripts/sandbox_escape.js
Trusted Pointer Table / WasmExportedFunctionData abuseT1203CWE-843references/v8-sandbox-escape.mdscripts/sandbox_escape.js
Code/exec via Wasm JIT region pivotT1203CWE-94references/v8-sandbox-escape.mdscripts/sandbox_escape.js
Mojo IPC handle-confusion sandbox escapeT1203CWE-269references/renderer-to-browser-escape.mdscripts/mojo_fuzz_harness.py
GPU-process UAF/OOB (Dawn/WebGPU, ANGLE)T1203CWE-416references/renderer-to-browser-escape.mdscripts/mojo_fuzz_harness.py
Mojo interface fuzzing for broker bugsT1203CWE-20references/renderer-to-browser-escape.mdscripts/mojo_fuzz_harness.py
Electron contextIsolation/IPC bridge RCET1059.007CWE-1188references/electron-webview-rce.mdscripts/electron_audit.py
nodeIntegration / webviewTag preload abuseT1059.007CWE-829references/electron-webview-rce.mdscripts/electron_audit.py
ASAR integrity / fuse / V8 snapshot tamperT1574.002CWE-345references/electron-webview-rce.mdscripts/electron_audit.py
XSS/open-redirect -> Electron RCET1189CWE-79references/electron-webview-rce.mdscripts/electron_audit.py
1-click drive-by chain deliveryT1189CWE-693references/clientside-rce-chains.mdscripts/chain_server.py
Cross-engine (JSC/WebKit) primitive portT1203CWE-843references/clientside-rce-chains.mdscripts/chain_server.py

Quick Start

bash
# 0. Pin the exact target build (Chrome/Edge/Electron all carry a V8 version)
#    chrome://version  | edge://version  | electron --version
jsvu --engines=v8                                   # local d8 of matching version
./scripts/d8_debug.sh ./d8 ./poc.js                 # d8 w/ exploit-friendly flags

# 1. Engine bug -> in-renderer R/W  (see references/v8-jit-typeconfusion.md)
d8 --allow-natives-syntax --shell ./scripts/v8_typer.js
#   yields addrof(), fakeobj(), read64()/write64() inside the V8 heap cage

# 2. Escape the V8 heap sandbox -> native R/W  (references/v8-sandbox-escape.md)
d8 --no-sandbox-testing-mode ./scripts/sandbox_escape.js   # local test;
#   on a real build: abuse trusted Wasm object raw pointer -> overwrite RWX Wasm code

# 3. Escape the OS sandbox: Mojo broker logic bug OR GPU-process memory bug
python3 scripts/mojo_fuzz_harness.py --interface FileSystemAccess --iters 100000

# 4. Electron / webview target: audit + weaponize
python3 scripts/electron_audit.py /path/to/app.asar      # finds nodeIntegration/IPC/fuse gaps
#   craft IPC/preload payload from the report; package XSS->RCE

# 5. Stage the full 1-click chain and serve it
python3 scripts/chain_server.py --stage1 renderer.js --stage2 escape.js --lhost 10.0.0.5 --lport 8080

OPSEC & Detection (summary)

TechniqueTelemetry/IOCDetection (Sigma/EDR)OPSEC note
JIT type confusionRenderer crash dumps (chrome_crashpad, crashpad_handler), GPU/renderer restarts, *-crash in ~/AppData/Local/.../CrashpadSigma: spike in renderer crash reports; EDR on crashpad_handler burstsSpray/clean up corrupted arrays; bail without crashing on failed type-check; do not leave %DebugPrint calls
V8 sandbox escapeNative R/W faults if math is off; abnormal RWX Wasm pagesEDR: RWX region churn inside chrome.exe/renderer; ETW VirtualProtect to RWXKeep corruption inside the cage until the last step; reuse existing RWX Wasm code page rather than allocating new
Mojo broker escapeBrowser process spawning cmd.exe/powershell.exe/rundll32.exe; unexpected file writes by brokerSigma: chrome.exe/msedge.exe parent -> shell child; EDR child-process rule; Mojo message auditLive off the broker's own capabilities (file write, process launch); avoid spawning a console child — inject instead
GPU-process bugGPU process crashes (--type=gpu), Dawn/ANGLE asserts, DXGI/Metal faultsEDR on GPU-process child anomalies; WebGPU enabled via policy = surfaceTest against the right GPU backend (D3D11/Metal/Vulkan); fail closed without crashing the GPU process
Electron IPC/preload RCEapp.asar mtime change, node child of Electron app, child_process.execSigma: Electron app spawning shells; FIM on app.asar/snapshot blobsPrefer in-process JS exec (require gadget) over child_process; restore app.asar mtime after fuse/snapshot tamper
Drive-by chain deliverySuspicious text/html with large encoded JS, WebSocket/long-poll to attacker host, UA-gated contentProxy/Sigma on long base64/%u blobs in HTML; JA3/JA4 of staging hostUA/feature gate so only the exact target build receives stage-2; single-use, expiring URLs

Deep Dives

  • references/v8-jit-typeconfusion.md — V8 object model, Map/element-kinds, TurboFan/Maglev/Turboshaft speculation bugs; CVE-2024-4947/5274, CVE-2025-2135/5419/10585 patterns. Build addrof/fakeobj and an in-cage arbitrary R/W via a fake TypedArray. Backed by v8_typer.js, d8_debug.sh.
  • references/v8-sandbox-escape.md — The V8 heap sandbox (pointer compression, external-pointer & trusted-pointer tables); escaping via raw pointers in Wasm objects (WasmIndirectFunctionTable / Liftoff), Trusted Pointer Table abuse, and pivot to RWX Wasm code. Backed by sandbox_escape.js.
  • references/renderer-to-browser-escape.md — Escaping the OS sandbox: Mojo IPC handle-confusion logic bugs (CVE-2025-2783 ForumTroll, CVE-2025-4609 ipcz), GPU-process memory bugs (Dawn/WebGPU, ANGLE CVE-2025-6558), fuzzing Mojo interfaces. Backed by mojo_fuzz_harness.py.
  • references/electron-webview-rce.md — Electron/CEF/WebView2 model; nodeIntegration/contextIsolation/sandbox matrix, preload-bridge & IPC abuse, deprecated webviewTag, ASAR integrity bypass (CVE-2025-55305) and V8 snapshot/fuse tampering, XSS->RCE. Backed by electron_audit.py.
  • references/clientside-rce-chains.md — Stitching primitives into a reliable 1-click chain; staged delivery, UA/feature gating, reliability hardening, cross-engine (JSC/WebKit CVE-2025-43529) primitive porting, patch-diffing for n-days. Backed by chain_server.py.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Browser Exploitation AI skill do?

Use when building a client-side browser exploit — V8/JSC JIT type confusion to renderer R/W, V8 heap-sandbox escape, renderer-to-browser sandbox escape (Mojo IPC, GPU/Dawn/ANGLE), Electron/webview IPC abuse, 1-click RCE chains

Why use Browser Exploitation on TypingMind?

Because you install it once and use it with any model. Browser Exploitation is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Browser Exploitation in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/hypnguyen1209/offensive-claude/tree/main/skills/browser-exploitation. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Browser Exploitation?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Browser Exploitation?

As many as you like. As long as a model supports skills, you can use Browser Exploitation with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Browser Exploitation AI skill free?

Yes. It is published on GitHub by hypnguyen1209 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇