⚠️ No Connection Allowlist — this page can connect anywhere
← All demos · Connection Allowlist Demo 1 of 4

Skimmer Exfiltration

A card skimmer is copying payment details to a destination the allowlist never named, so the browser refuses the connection before it is opened.

Requires Chrome 152 or later. Other browsers ignore the header, so both modes will behave the same.

Skimmer active — card data can leave the browser

Checkout

Complete your purchase

🚨 Skimmer active. Both connections are carried. The beacon to evil-cyber-hacker.com is delivered exactly like the real order, because nothing has been told which destinations are acceptable.

💡 Open DevTools → Network tab before pressing the button to watch which requests leave the browser.

What the allowlist did

The list is just response-origin: this page may talk to itself and nothing else. The order matches and is carried as normal. The beacon to evil-cyber-hacker.com matches nothing, so the browser refuses to open the connection and sends a Connection Allowlist report naming the destination it refused.

A CSP connect-src 'self' would give you the same outcome here. The next three demos cover the cases where it would not.

← All demos Demo 2 →