EvilRBI weaponizes Remote Browser Isolation mechanics against the user they were meant to protect — a pixel-faithful IdP mirror, relayed clicks and keys, and MFA ceremonies completed in the middle browser. No Chrome 0-days. No CRX install.
Reverse proxy on the HTTP stream. Captures and injects session tokens as they flow. Auth UI still runs in the victim browser.
Attacker’s real Chrome holds the session. Victim sees an MHTML/DOM mirror; every click, key, credential, and MFA ceremony is relayed upstream.
Public HTTPS face (TunnelTug or any ingress) serves the portal. One-click stream targets via portal routing.
chromedp captures MHTML from a managed upstream Chrome tab. Client hydrates into a Shadow DOM stage over WebSocket.
Keys, clicks, WebAuthn, and Okta FastPass complete in the middle browser — not the victim’s.
Built-in Google Endpoint Verification and chromewebdata footholds — intended surfaces, confused-deputy privilege.
MHTML capture + client hydration for SPAs and stable auth flows — Google, Okta, Microsoft, AWS.
Upstream ceremony proxy with victim-side signing at the RP origin; CDP virtual authenticator fallback.
Relays Verify challenges without binding the victim’s loopback FastPass port.
chrome://dino / chromewebdata confused deputy — extension-bridge and apex SW privileges without CRX install.
Pairs with Google’s Endpoint Verification component already inside Chrome — magic RPC, host wildcard.
Stock Chrome. No memory corruption, sandbox escape, or unpatched CVE. Trust boundaries disregarded, not broken.
Visitors hit a public edge. EvilRBI streams a faithful mirror of the real IdP from a chromedp-managed middle browser. Input and MFA flow the other way. The victim never holds the authoritative session.
# Research lab — never expose --dev to untrusted networks go build -o proxy . ./proxy --dev --headed --no-tui # Open http://127.0.0.1:8879/?url=https://example.com
Released when the DEF CON 34 talk starts (Fri Aug 7, 2026 10:30 PDT). Server-gated until then.
Manifesto: Dante’s Inferno of Deflected Responsibility, LGCO, Four Constants of Emergent Vulnerabilities. Security Considerations and Non-Goals under composition.
Reflections on Disregarding Trust write-up: BiTM architecture, multi-rail control, no 0-days thesis.
Fri, Aug 7 · 10:30–11:30 PDT · What happens when RBI isolation, component extensions, and service-worker scope are weaponized against the user they were meant to protect.
Schedule entry Talk materialsEvilRBI is designed for controlled research, red-team exercises with explicit authorization, and defender education. Improper use creates significant legal and compliance risk. Never run open-relay modes on networks reachable by untrusted users. Treat captured cookies, snapshots, and debug endpoints as sensitive material.
MIT licensed · Repository: github.com/EvilRBI/phisheries
Go 1.26+, Chrome/Chromium for the upstream session.
git clone https://github.com/EvilRBI/phisheries.git cd phisheries go build -o proxy .
Headed Chrome recommended for OAuth / CAPTCHA flows.
./proxy --dev --headed --no-tui # → http://127.0.0.1:8879/?url=https://…