Fake Login Popup Showing a Real URL? How Browser-in-the-Browser Phishing Works

You click a link and a Google or Microsoft login window appears. The window looks legitimate. It has a familiar logo, a lock icon, browser controls, and even…

You click a link and a Google or Microsoft login window appears.

The window looks legitimate. It has a familiar logo, a lock icon, browser controls, and even an address bar showing a trusted domain such as accounts.google.com or a Microsoft login address.

You check the URL and everything appears correct.

So you log in.

Unfortunately, that URL may not be real.

It may simply be text drawn inside a fake browser window created by the webpage you are already visiting.

This technique is called Browser-in-the-Browser phishing, commonly abbreviated as BitB.

It is designed to defeat one of the most common pieces of phishing advice:

“Always check the URL before entering your password.”

Checking the real browser address bar is still important. The problem is that BitB attacks can create a second, fake address bar inside the webpage.

That fake address bar can display whatever the attacker wants.

What Is Browser-in-the-Browser Phishing?

Browser-in-the-Browser is a phishing technique where an attacker creates a fake browser window inside a normal webpage.

The fake window is built using ordinary web technologies such as HTML, CSS, and JavaScript.

It can be designed to look like a genuine browser window, including:

  • a title bar
  • browser tabs
  • back and refresh buttons
  • a lock icon
  • an address bar
  • a trusted-looking domain
  • a Google, Microsoft, Apple, or other login page

The important detail is that the fake window is still part of the webpage.

It is not necessarily a separate browser window.

The attacker is essentially drawing a picture of a browser and placing a phishing login form inside it.

The Trick: There Are Two “Browsers” on Your Screen

This is the easiest way to understand the attack.

Imagine the real browser is currently visiting:

https://example-phishing-site.com

That is the real URL.

The webpage then displays a fake login popup.

Inside that popup, the attacker draws an address bar containing:

https://accounts.google.com/

You see the Google address.

But the actual browser address bar still contains:

https://example-phishing-site.com

The Google URL is simply part of the webpage's visual content.

It is not the browser's real navigation address.

How the Attack Works

A simplified Browser-in-the-Browser attack looks like this:

Victim visits phishing website
          |
          v
Attacker creates fake browser window
          |
          v
Fake address bar displays trusted domain
          |
          v
Fake Google/Microsoft login form appears
          |
          v
Victim enters username + password
          |
          v
Credentials are sent to attacker
          |
          v
Attacker may attempt real-time login
          |
          v
MFA may be requested
          |
          v
Session or authentication data may be captured
  

The fake window can be extremely convincing because the attacker controls its appearance completely.

Why Does the URL Look Correct?

Because the attacker is not necessarily changing your browser's real address bar.

They are creating another address bar inside the webpage.

Webpages can display arbitrary text.

For example, a website can display:

accounts.google.com

as plain text.

It can style that text to look exactly like a browser address bar.

It can even add a lock icon beside it.

That does not make the displayed address authoritative.

The browser itself controls the real address bar.

A URL drawn inside a webpage is not the same thing as the URL displayed by your actual browser.

How Can You Tell a Fake Browser Popup From a Real One?

There is no single visual trick that works against every BitB implementation.

However, several checks are useful.

1. Look at the actual browser address bar

This remains the first check.

Do not inspect only the URL displayed inside the login window.

Look at the browser's own address bar at the very top of the browser.

If the real browser says:

random-site.example

while a popup inside the page claims to be:

accounts.google.com

the popup is not a genuine Google browser window.

2. Try moving the popup outside the browser

A genuine separate browser window can normally be moved independently of the webpage that opened it.

A fake BitB window is constrained by the webpage.

Depending on how it was implemented, you may notice that the “window” cannot actually leave the boundaries of the browser tab.

This is a useful clue, although it should not be treated as a universal detection method.

3. Try browser features

Fake browser interfaces often imitate only the controls necessary to look convincing.

Real browser windows have access to genuine browser functionality.

A fake window may have buttons that merely trigger webpage actions instead of behaving like actual browser controls.

4. Pay attention to password-manager behavior

A password manager can provide a useful additional signal.

Because password managers can associate credentials with the actual website origin, they may refuse to autofill credentials into a fake login window embedded in an unrelated page.

If your password manager normally recognizes a website but suddenly refuses to offer the expected login, stop and investigate rather than manually typing the password.

5. Use phishing-resistant authentication

Passkeys and FIDO2 security keys provide a much stronger defense against this class of attack.

Unlike a password or one-time code, a passkey is cryptographically associated with the legitimate website origin.

A fake login window cannot simply display a trusted domain and obtain a valid passkey signature for that domain.

Why MFA Does Not Automatically Protect You From BitB

This is one of the most important parts of the attack.

Many people assume:

“I have MFA, so even if they steal my password, they cannot get into my account.”

MFA is still extremely valuable.

But some forms of MFA can be relayed by an attacker during an active phishing session.

For example, an attacker may collect your username and password through the fake login window.

They then attempt to log in to the real service at the same time.

The real service asks for your second factor.

The attacker causes the phishing page to display a matching MFA request.

You enter the code.

The attacker immediately relays that code to the real service.

If the authentication succeeds, the attacker may obtain the resulting session.

This is why traditional MFA methods such as SMS codes, authenticator codes, and approval prompts are not equivalent to phishing-resistant authentication.

BitB vs Traditional Phishing

Traditional phishing Browser-in-the-Browser phishing
Fake login webpage Fake browser window inside a webpage
Fake or suspicious URL often visible Fake window can display a trusted-looking URL
Victim checks browser address Victim may accidentally inspect the fake address bar
Password theft Password and potentially MFA/session theft
Usually easier to recognize Designed to defeat visual URL checking

Why Attackers Use BitB Against Google and Microsoft Accounts

Google and Microsoft accounts are particularly valuable because one compromised identity can provide access to many other services.

A compromised Google identity may expose:

  • Gmail
  • Google Drive
  • Google Ads
  • YouTube
  • business applications
  • other connected services

A compromised Microsoft identity can provide access to:

  • Outlook
  • Microsoft 365
  • OneDrive
  • SharePoint
  • Teams
  • enterprise applications

For organizations, the consequences can extend beyond one employee's account.

An attacker who compromises an advertising manager, administrator, or privileged employee may gain access to business systems, advertising budgets, client accounts, or sensitive documents.

Why the Attack Is Especially Relevant in 2026

Browser-in-the-Browser is not a brand-new concept.

What has changed is how attackers are integrating it into modern phishing operations.

On October 6, 2026, security researchers disclosed a human-operated phishing platform impersonating AI advertising products associated with ChatGPT, Gemini, Claude, Perplexity, Manus, and Meta Muse.

The fake products used a “Connect” workflow that opened a browser-like window inside the webpage.

The fake window displayed trusted-looking login origins while the actual browser remained on the phishing site.

The platform could then capture credentials and allow an operator to influence which MFA challenge the victim encountered.

This is important because it demonstrates that BitB is no longer merely a theoretical visual trick.

It is being integrated into human-operated phishing infrastructure.

What If the Popup Looks Exactly Like Google?

That is not enough.

Attackers can reproduce:

  • Google's logo
  • Microsoft's logo
  • browser buttons
  • fonts
  • colors
  • icons
  • address-bar styling
  • login forms

The visual appearance of a login window is therefore not strong evidence of authenticity.

The strongest question is:

Where is the real browser actually navigating?

What If the Address Bar Shows HTTPS and a Lock?

HTTPS does not mean the content is trustworthy.

HTTPS protects the connection between your browser and the website you are actually visiting.

A phishing website can also use HTTPS.

More importantly, in a BitB attack, the lock icon and URL you see inside the fake browser window may simply be webpage graphics.

So:

Lock icon ≠ trusted website.

HTTPS ≠ legitimate business.

Visible URL inside a popup ≠ actual browser origin.

What If You Already Entered Your Password?

If you entered your password into a suspicious login popup, treat it as potentially exposed.

From a separate trusted device where practical:

  1. Change the affected password.
  2. Review recent account activity.
  3. Review active sessions and signed-in devices.
  4. Sign out unfamiliar sessions.
  5. Review recovery email addresses and phone numbers.
  6. Check whether new authentication methods were added.
  7. Enable phishing-resistant MFA or a passkey.

If the account is used for work, contact your organization's security or IT team immediately.

Do not assume that changing the password alone has removed every active session.

What If You Also Entered an MFA Code?

Take the incident more seriously.

An attacker may have attempted to relay the code into the real authentication process in real time.

From a trusted device, review:

  • recent sign-ins
  • new devices
  • active sessions
  • authentication methods
  • connected applications
  • account-security alerts

Revoke suspicious sessions and credentials where the service provides that capability.

For business accounts, administrators should also investigate identity-provider logs and unexpected account or permission changes.

Why Passkeys Are Stronger Against Browser-in-the-Browser

Passkeys use public-key cryptography and are bound to the legitimate website origin.

This creates a major difference from passwords and one-time codes.

An attacker can draw:

accounts.google.com

inside a fake popup.

But that does not change the actual origin of the webpage.

A passkey's cryptographic operation is tied to the legitimate origin, so simply drawing the correct-looking URL does not give the attacker the cryptographic credential.

This is one reason passkeys and FIDO2 security keys are considered phishing-resistant authentication methods.

A Simple Rule for Login Popups

Whenever a login appears inside another website, stop for a moment.

Ask:

  1. Did I intentionally start this login?
  2. What does the actual browser address bar say?
  3. Is this a genuine separate browser window or a window drawn inside the page?
  4. Does my password manager recognize the site?
  5. Can I use a passkey instead?

If something feels unusual, close the login window.

Then navigate directly to the service yourself rather than continuing through the original link.

Do Not Rely on the Address Bar Alone

Checking URLs is still useful.

But modern phishing requires a more complete mental model.

Instead of asking only:

“Does this URL look correct?”

ask:

“Is this URL actually controlled by my browser, or is it just something the webpage is showing me?”

That small change in thinking makes Browser-in-the-Browser attacks much easier to understand.

Quick Browser-in-the-Browser Checklist

  • Never enter credentials into an unexpected login popup.
  • Check the browser's actual address bar, not just the popup's address bar.
  • Be suspicious when a login window appears inside another website.
  • Do not trust a lock icon displayed inside webpage content.
  • Let your password manager recognize the real origin.
  • Prefer passkeys or FIDO2 security keys for important accounts.
  • Verify unexpected login requests through a separate channel.
  • After suspected phishing, revoke active sessions rather than changing only the password.

Bottom Line

Browser-in-the-Browser phishing works by exploiting something humans naturally trust: the visual interface of a web browser.

An attacker can create a fake login window that contains a convincing logo, browser controls, lock icon, and even a trusted-looking URL.

But the address shown inside that window may simply be text rendered by the webpage.

The real browser could still be visiting a completely different domain.

That is why the most important distinction is:

A URL displayed inside a webpage is not the same as the browser's actual URL.

If you see an unexpected login popup, do not trust it simply because it looks like Google, Microsoft, Apple, or another familiar service.

Check the real browser context, avoid entering credentials through unexpected popups, and use phishing-resistant authentication wherever possible.

Modern phishing is no longer only about creating a fake website.

Sometimes the attacker creates a fake browser inside the website you are already looking at.


Keep reading

Related articles

Browse all articles