What is a Browser-in-the-Browser phishing attack?

The short answer

Browser-in-the-Browser (BitB) is a phishing trick where a scam page draws a fake sign-in pop-up inside your tab, with a padlock and address the attacker chose.

Animated diagram: What is a Browser-in-the-Browser phishing attack?

Browser-in-the-Browser

Browser-in-the-Browser (BitB) is a phishing trick. A scam page draws a fake sign-in window inside your browser tab, with a title bar, a padlock and an address. It usually starts with a lure, such as a shared document behind a “Sign in with Microsoft” button. The window looks like a real pop-up. In fact, it is part of the web page you’re on.

Many people count on two-factor authentication (2FA), a code typed after the password, to save them. Advanced BitB kits get past typed codes. That’s where passkeys come in. A passkey is locked to the real site’s domain, so your browser won’t use it on a look-alike. That makes passkeys phishing-resistant, and typed codes are not.

What a fake pop-up actually is

A real sign-in pop-up comes from window.open. It opens a separate window, and the browser decides what that window shows, generally including an address bar. The page can’t change or hide it. A BitB page opens nothing. It draws the window with HTML (HyperText Markup Language), CSS (Cascading Style Sheets) and an iframe, a frame that shows another page inside the tab. The title bar, the padlock and the address are pixels the attacker chose, styled like Edge on Windows or Safari on macOS. The address can even read login.microsoftonline.com, because it is just text the attacker copied.

The rest of the window is live. In advanced kits, the iframe loads Microsoft’s real login through the attacker’s relay, a reverse proxy. You can type in it, click it, and it steps you through the real two-factor prompts. So being able to type in a window doesn’t prove it is real.

How the relay steals the session

  1. You click the lure. The shared document asks you to sign in with Microsoft, and the fake window appears inside the same tab.
  2. Your details pass through. Your password and your two-factor code travel through the reverse proxy to Microsoft’s real login.
  3. The relay copies the cookie. When the sign-in succeeds, Microsoft returns a session cookie, and the relay keeps a copy.
  4. The attacker replays it. The cookie proves the sign-in, two-factor included, already happened. Replaying it skips the code.

MITRE ATT&CK (Adversarial Tactics, Techniques, and Common Knowledge) lists the theft as T1539 Steal Web Session Cookie and the use of the stolen cookie as T1550.004. MITRE notes that stolen cookies can be used to bypass some multi-factor authentication protocols. In November 2025, researchers caught Sneaky2FA, a Microsoft 365 phishing kit, using exactly this method.

A typed code is not phishing-resistant

The myth is that two-factor codes save you. The National Institute of Standards and Technology (NIST) says in SP 800-63B that authenticators where you type the output, such as one-time password (OTP) codes, shall not be considered phishing-resistant. The relay simply passes your code along. Passkeys work differently. Each one is scoped to the real site’s domain, and the browser checks that domain against the page it is on. On a look-alike site, your browser won’t use it.

What to do

  • Before typing a password on a computer, drag the pop-up past the edge of your browser. A real window leaves. A fake one stays trapped in the tab.
  • On a phone, close the tab and type the address yourself, because phone browsers have no separate windows you can drag.
  • Switch your accounts to passkeys where you can, since your browser won’t use them on a look-alike site.
  • Trust only your browser’s own address bar, never one drawn inside the page.

#BrowserInTheBrowser#BitB#Phishing#PhishingScam#Passkeys#AccountSecurity#CyberSecurity#InfoSec#OnlineSafety

Watch it in 60 seconds