Blob URL Phishing: Fake Login Pages Rendered Entirely Inside the Browser via Microsoft OAuth and Teams

Blob URL Phishing (TL-2026-2430) is a medium-severity phishing campaign, first published 2026-09-10. It has no confirmed attribution, affects Microsoft Microsoft 365 / Entra ID OAuth authorization flow and, maps to 10 MITRE ATT&CK techniques (T1027, T1036, T1056), and is covered by 9 detection rules and 8 indicators of compromise.

Key facts for TL-2026-2430

Threat ID
TL-2026-2430
Severity
MEDIUM
Status
ACTIVE
Category
PHISHING
First published
2026-09-10
Last reviewed
2026-09-10
Attribution confidence
LOW
Motivation
UNKNOWN
Detection rules
9
Indicators of compromise
8

Malware and tooling in Blob URL Phishing

Malware and tooling: Unnamed managed phishing-as-a-service (PhaaS) backend

Barracuda researchers identified a phishing campaign that routes victims through genuine Microsoft OAuth and Teams infrastructure before assembling a fake login page inside the victim's browser using a blob URL rather than hosting the phishing content on a server. The page registers a service worker and runs logic in a sandboxed iframe, letting the attacker's backend send live instructions via browser messaging so the phishing content can change without a hardcoded redirect, leaving no persistent URL for security tools to detect or blocklist.

How Blob URL Phishing works

On 2026-09-09, Barracuda Networks Associate Threat Analyst Ashitosh Deshnur published research describing a phishing campaign that begins with a DocuSign-themed email carrying a calendar invite (.ics) attachment. The invite itself is not malicious; it embeds a crafted redirect parameter that points to a genuine Microsoft OAuth endpoint (login.microsoftonline.com), giving the message the appearance of a routine business meeting request rather than an obvious phishing lure.

From the legitimate OAuth endpoint, the crafted redirect routes the victim through Microsoft Teams, which is made to load an external resource hosted on cdn.bloom[.]io. The victim's browser converts this externally sourced content into a blob URL -- a temporary, browser-generated address that points to data held only in local memory rather than on a remote server. The fake Microsoft login page is assembled and rendered entirely from this in-memory blob object inside the victim's own browser session, so no static phishing webpage ever exists for a security tool to crawl, fingerprint, or add to a blocklist.

Once rendered, the page registers a service worker and runs its logic inside a sandboxed iframe; together these manage the phishing workflow and user navigation. Barracuda's analysis states the phishing page 'receives instructions from backend infrastructure using browser messaging mechanisms,' which lets the attacker push live updates to the page's content and behavior after it has already loaded, instead of relying on a hardcoded redirect chain that a defender could map and block in advance.

Because every step -- the OAuth endpoint, the Teams content loader, and the final rendering surface -- takes place inside domains and browser behaviors that are either genuinely Microsoft-owned or exist only transiently in the victim's memory, the technique removes most of the static indicators (a persistent phishing domain, a fixed URL, a stable HTML artifact) that automated detection and blocklisting traditionally depend on. Barracuda characterizes this as phishing evolving 'beyond fake websites and suspicious domains,' reframing the credential-theft page as an ephemeral, dynamically-controlled browser construct instead of a hosted asset. Coverage was syndicated within 24 hours by SecurityWeek, Help Net Security, and several trade/MSP-focused outlets, extending visibility of the technique to a broad enterprise-security and SMB audience. No CVE applies -- this is an abuse of legitimate OAuth/Teams redirect and browser platform behavior (blob URLs, service workers, iframes, postMessage), not a software vulnerability. No malware hash, second-stage payload, actor name, or targeted-sector/region breakdown was disclosed in any of the reviewed sources; a BeaconBeagle lookup on cdn.bloom.io returned zero indexed C2 correlations.

Barracuda's writeup also discloses that the page carries a 'hidden command-and-control configuration' and states the operation is 'not a simple stand-alone [page], but part of a managed platform' that can be centrally operated, updated, and steered across many victims at once -- i.e., the campaign is consistent with a phishing-as-a-service (PhaaS) delivery model rather than a one-off, hand-built kit, though no branded kit name was disclosed and follow-up searches confirm this is a distinct campaign from named kits such as LogoKit or Sneaky 2FA. Every observable behavior in the chain -- constructing the Blob object from the fetched cdn.bloom[.]io resource, registering the service worker, executing logic inside the sandboxed iframe, and handling the browser-messaging instructions from the backend -- is implemented and driven by JavaScript running client-side in the victim's browser session; Barracuda's own framing of the core defensive gap is blunt: 'There is no phishing page to block.' Analyst Ashitosh Deshnur is quoted across the syndicated coverage: 'This campaign demonstrates how phishing is evolving beyond fake websites and suspicious domains, removing many of the indicators that security teams have traditionally relied on for detection.'

MITRE ATT&CK techniques used in TL-2026-2430

Defense Evasion

T1027 Obfuscated Files or Information; T1036 Masquerading; T1684.001 Impersonation

Credential Access

T1056 Input Capture

Execution

T1059 Command and Scripting Interpreter; T1204 User Execution

Command and Control

T1071 Application Layer Protocol

Initial Access

T1566 Phishing

Resource Development

T1583 Acquire Infrastructure; T1608 Stage Capabilities

Affected products and versions in Blob URL Phishing

  • Microsoft — Microsoft 365 / Entra ID OAuth authorization flow and Microsoft Teams redirect handling (cloud service; abused as a trust-transfer mechanism, not a versioned vulnerability)

Remediation for Blob URL Phishing

Immediate actions

  • Monitor OAuth authorization flows and redirect chains for unexpected destinations, including redirects that traverse trusted Microsoft endpoints en route to a third-party resource
  • Inspect blob URL creation and usage occurring in login or authentication contexts within the browser
  • Flag service worker registrations tied to externally loaded, unrecognized content rather than the parent application's own origin

Workarounds

  • Train staff to question unexpected document-signing or calendar-invite requests even when the click path runs entirely through legitimate Microsoft infrastructure

Longer-term hardening

  • Deploy phishing-resistant MFA such as FIDO2 security keys or passkeys to reduce the value of a harvested credential
  • Adopt email security tooling that analyzes a link's entire click path (including OAuth/Teams redirect hops) rather than evaluating only the first-hop URL
  • Shift detection posture toward identity-based and behavioral controls rather than static URL/domain blocklisting, since this technique is designed to leave no persistent artifact to blocklist

Timeline of Blob URL Phishing

  • Barracuda Networks publishes the original research 'Email attacks evade detection by generating phishing pages directly inside the victim's browser,' authored by Associate Threat Analyst Ashitosh Deshnur, including the technical breakdown and defensive recommendations.
  • Barracuda threat analysts identify a phishing campaign chaining a DocuSign-themed email lure through genuine Microsoft OAuth and Teams infrastructure to a blob-URL-rendered, browser-only fake login page.
  • Threadlinqs HUNT phase ingests the Help Net Security article into the TL-2026-2430 threat skeleton for RESEARCH triage.
  • Trade and MSP-focused outlets (iTWire, SMBtech, ITBrief, CloudLinkTech, vmBlog) syndicate the Barracuda research, extending visibility of the technique to enterprise IT and managed-service-provider audiences.
  • SecurityWeek publishes independent coverage including the Barracuda quote that 'this campaign demonstrates how phishing is evolving beyond fake websites and suspicious domains.'
  • Help Net Security publishes coverage summarizing the Barracuda blob URL phishing findings for a broader security audience.

Sources cited for Blob URL Phishing

More in phishing

Detection coverage for TL-2026-2430

As of 2026-09-10, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-2430 across Splunk SPL, Microsoft KQL and Sigma, covering 8 indicator(s) of compromise. The whole corpus is readable without an account; a free account unlocks full detection query text in Splunk SPL, Microsoft KQL and Sigma; paid tiers add raw indicator values, correlation and the MCP server. Threadlinqs MCP server · View plans.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

[ 0 threats ] [ 0 det ] [ CRIT: 0 ] [ HIGH: 0 ]
// threat_feed
$ sort --newest
Showing all threats

Latest Threats