Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Tabnabbing is a phishing technique in which a page the victim has left open in a background tab quietly rewrites itself into a convincing login screen while their attention is elsewhere.

What Is Tabnabbing?
Tabnabbing takes advantage of a habit almost everyone has: leaving a dozen tabs open and not looking at most of them for hours. The attack lets a page that was harmless when you opened it change into a login screen for a service you trust, so that when you return to the tab you assume your session expired and type your password into the attacker’s form.
Aza Raskin, then at Mozilla, described the technique in May 2010. It is a user interface attack rather than a software vulnerability: nothing in the browser malfunctions, and the deception relies entirely on the fact that people identify a tab by its favicon and title rather than by re-reading the address bar.
The sequence is short:
The only reliable tell is the address bar, which still shows the attacker’s domain. That is precisely the element users stop checking once a tab has been open for a while.
The more damaging variant works in the opposite direction and does not need the victim to visit a malicious site at all. When a page opens a link with target="_blank", the new page historically received a window.opener reference to the page that opened it. Cross-origin script access is blocked, but one property was not: the new page could set window.opener.location and navigate the original tab anywhere it liked.
So a user on a trusted site, such as a forum, a webmail client, or an intranet portal, clicks an external link. The external page sends their original tab to a convincing copy of that trusted site. The user finishes with the new tab, closes it, finds the old tab apparently logged out, and signs in again.
Browsers fixed the default in 2020 and 2021. Safari 12.1, Firefox 79, and Chrome 88 made target="_blank" imply rel="noopener", so window.opener is null. The problem has not disappeared, because a great deal of software renders links in older components, in email clients, in desktop applications embedding a web view, and in content authored with an explicit rel="opener".
rel="noopener noreferrer" to every link that opens in a new tab, including links generated from user content. It costs nothing and protects users on older browsers and embedded web views.Cross-Origin-Opener-Policy: same-origin severs the opener relationship for cross-origin documents in both directions, which is the structural fix rather than a per-link one.rel="opener" or inject their own anchors. Treat this as part of your HTTP security headers and output encoding work.OWASP lists reverse tabnabbing in its guidance on HTML5 security, and the fix appears in most secure coding checklists as a one-line change that is frequently missed in older codebases.
Credential theft is the goal, so the controls that blunt phishing generally apply. Password managers are particularly effective here: they fill credentials only on a matching origin, so a replica page on a different domain simply does not autofill, which is a far more reliable signal than human vigilance. Phishing-resistant multi-factor authentication, such as FIDO2 security keys or passkeys, binds the authentication to the real origin and makes a captured password insufficient.
In security awareness training, the useful habit to teach is narrow and memorable: if a tab you did not just open is asking you to sign in, close it and navigate to the service yourself. The NCSC takes the same line in its phishing guidance, placing the emphasis on technical controls and easy reporting rather than on expecting staff to spot every fake.
At Privia Security, our Social Engineering Services include browser-based credential harvesting scenarios like this one, so you can see how your staff and your controls respond before a real attacker tries.
Classic tabnabbing is, because nothing stops a page from changing its own content, title, and favicon after you switch away. That behaviour is normal web functionality. Reverse tabnabbing is largely blocked in current browsers, which treat target=”_blank” as implying rel=”noopener”. Older browsers, embedded web views, and desktop applications that render HTML can still be affected.
noopener makes window.opener null in the newly opened page, so it cannot navigate or inspect the page that opened it. noreferrer does the same and additionally suppresses the Referer header, so the destination does not learn where the user came from. Using both together is the standard recommendation for any link that opens in a new tab.
A password manager matches saved credentials to the origin in the address bar, not to the appearance of the page. A replica login screen hosted on a different domain will not trigger autofill. That silence is a strong signal, and it works even when the user has not noticed anything unusual, which is why managers outperform visual inspection.
Not directly, because the attacking page controls its own policy. The relevant header is Cross-Origin-Opener-Policy, which when set to same-origin isolates your pages from any window that opened them or that they open. Combine it with rel=”noopener” on outbound links so that users on browsers without full COOP support are still protected.
You May Be Interested In These
Cybersecurity Terms
17 November 2026
What Is a Cloud-Native Application Protection Platform?
Read MoreWe use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.