# Reproducing the browser path leak study

Public package for **17 November 2026** collection on a Cursor Cloud Agent USA VM
(Playwright Chromium **131.0.6778.33**). Gap-deepened documentation:
**18 November 2026**.

This folder’s public JSON/screenshots are redacted. Raw IPs, credentials, and
full route dumps stay private/gitignored. Do not commit secrets.

## Offline inspection (no credentials)

1. Read `protocol.md` (A0 cloud freeze + A1 ProxySeller unlock).
2. Read `research-article.md` for methods, six findings, limits, disclosure.
3. Load `summary-table.json`, `sha-relations.json`, and `cross-compare.json`.
   Cite which comparison artifact you use (session union vs pass baseline).
4. Spot-check per-visit files (`cloud-direct-p*.json`, `proxy-us-http-p*.json`,
   `proxy-us-socks-p*.json`, `proxy-dead-p1.json`) for echo counts, ICE state,
   `matchesDocumentEcho`, and error strings.
5. Review collector reliability artifacts: `http-fixture-debug.json`,
   `playwright-http-smoke.json`, `proxy-connectivity-probe.json`,
   `chromium-socks-auth-guard.json`, `secret-presence-probe*.json`.
6. Open `screenshots/*.png` (local fixture UI only; public shots are redacted).

No network access is required for the steps above.

## Live re-run (requires your own secrets)

Use **your** ProxySeller residential credentials as Cursor Cloud Agents Runtime
Secrets (or equivalent env injection). Expected names:

- `PROXYSELLER_HOST`
- `PROXYSELLER_HTTP_PORT`
- `PROXYSELLER_SOCKS_PORT`
- `PROXYSELLER_USER`
- `PROXYSELLER_PASS`

Never paste values into chat, git, or committed `.env` files.

Approximate collector flow (see scripts in this directory):

```bash
# From research/browser-path-leak-study/
python3 prepare-proxies.py          # writes private/proxies.json (gitignored)
python3 route-check.py              # pre-visit urllib echoes + ip route
node collect.cjs --condition=...    # Playwright Chromium visit
python3 route-check.py              # post-visit
python3 run-study.py                # orchestrates matrix when configured
```

Notes that must match the frozen methods:

- Chromium rejects SOCKS5 username/password; bridge with a local anonymizer
  (`proxy-chain`) for SOCKS legs, or expect the auth guard error.
- Do **not** use Chromium bypass token `<-loopback>` for the local fixture
  unless you intend to send loopback through the residential gateway
  (`http-fixture-debug.json` recorded `503 Target host denied`).
- Prefer `127.0.0.1,localhost,<loopback>` bypass so the fixture stays local.
- Under proxy conditions: document echoes via Playwright `APIRequestContext`;
  WebRTC via `fixture/webrtc-only.html`.
- CometVPN is VPN-only. Do not supply CometVPN as HTTP/SOCKS. Do not claim
  tunnel results without a proven VPN path on the host (TUN presence alone is
  insufficient on hosted Cursor VMs).

## What this package does not support

- Population leak rates or ProxySeller uptime rankings
- Claims about provider logging or deception
- CometVPN tunnel measurements
- Recreation of raw IP bytes from published SHA-12 prefixes
- Treating smoke/probe hashes as identical to A1 matrix document-echo hashes
  (residential rotation was observed)

## Citation

FreePolicyTools, “Proxy Connected, Browser Still Direct: WebRTC Left the Cloud
Path Open,” 17 November 2026. Report visits individually.
