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

> 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.

- **Published:** 2026-09-10T00:00:00Z
- **Last reviewed:** 2026-09-10T00:00:00Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-2430
- **Card image:** https://intel.threadlinqs.com/og/threat/threat-intel-blob-url-phishing-technique-tl-2026-2430.webp?v=9f5bca62 (Threadlinqs threat intel: Blob URL Phishing via Microsoft OAuth: Detection & IOCs (TL-2026-2430) — Medium severity, 8 IOCs, 9 detection rules.)
- **ID:** TL-2026-2430
- **Severity:** MEDIUM
- **Category:** PHISHING
- **Status:** ACTIVE
- **Detections:** 9 (1 shown free below) · **IOCs:** 8 (2 shown free below)

## Description

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

- T1583 Acquire Infrastructure
- T1608 Stage Capabilities
- T1566 Phishing
- T1204 User Execution
- T1059 Command and Scripting Interpreter
- T1027 Obfuscated Files or Information
- T1036 Masquerading
- T1684.001 Impersonation
- T1056 Input Capture
- T1071 Application Layer Protocol

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**DocuSign-Themed Calendar Invite With Crafted Microsoft OAuth Redirect (SPL)** (`TL-2026-2430-SPL-001`)

Detects an email impersonating DocuSign that carries a .ics calendar-invite attachment whose embedded link abuses the legitimate Microsoft OAuth authorization endpoint (login.microsoftonline.com) via a crafted redirect_uri parameter pointing outside sanctioned Teams/SharePoint destinations. This is the initial-access lure step of the Barracuda-documented blob URL phishing chain, where a genuine OAuth endpoint is used to transfer trust before the victim is routed to an attacker-influenced resource.

- **Languages:** Splunk SPL, Microsoft KQL, Sigma
- **ATT&CK:** T1583.001, T1608.005, T1566.001, T1204.001
- **Data sources:** o365_message_trace, email_gateway_logs, m365_defender_emailevents, m365_defender_urlclickevents, m365_defender_emailattachmentinfo
- **Severity:** high
- **Confidence:** medium

### Splunk SPL

```spl
index=email_security (sourcetype="o365:management:activity" OR sourcetype="proofpoint:messages" OR sourcetype="mimecast:message")
  attachment_extension=".ics"
| eval sender_impersonates_docusign=if(match(lower(from_display_name), "docusign") AND NOT match(lower(from_domain), "docusign\.(com|net)$"), 1, 0)
| where sender_impersonates_docusign=1
| rex field=body_urls "redirect_uri=(?<redirect_target>[^&\s\"]+)"
| where like(url, "%login.microsoftonline.com%") AND isnotnull(redirect_target)
| eval redirect_target_decoded=urldecode(redirect_target)
| where NOT match(redirect_target_decoded, "^https://(teams\.microsoft\.com|.*\.sharepoint\.com)/")
| table _time, from_address, from_display_name, to_address, subject, attachment_name, url, redirect_target_decoded, message_id
| sort - _time
```

### Microsoft KQL

```kql
EmailAttachmentInfo
| where FileType =~ "ics"
| join kind=inner (
    EmailEvents
    | where SenderDisplayName has "DocuSign" and SenderFromDomain !endswith "docusign.com" and SenderFromDomain !endswith "docusign.net"
    | where Timestamp > ago(24h)
) on NetworkMessageId
| join kind=inner (
    UrlClickEvents
    | where Url has "login.microsoftonline.com" and Url has "redirect_uri="
    | extend RedirectTarget = extract(@"redirect_uri=([^&]+)", 1, Url)
    | where isnotempty(RedirectTarget) and RedirectTarget !has "teams.microsoft.com" and RedirectTarget !has "sharepoint.com"
    | where Timestamp > ago(24h)
) on NetworkMessageId
| project Timestamp, SenderFromAddress, SenderDisplayName, RecipientEmailAddress, Subject, FileName, Url, RedirectTarget, NetworkMessageId
| order by Timestamp desc
```

### Sigma

```yaml
title: DocuSign-Themed Calendar Invite With Crafted Microsoft OAuth Redirect Parameter
id: 7c4e2b1a-3f9d-4e6a-8b2c-5a1d9e3f6c72
status: experimental
description: Detects an email carrying a DocuSign-impersonating sender with an .ics calendar-invite attachment whose embedded link abuses the legitimate Microsoft OAuth authorization endpoint (login.microsoftonline.com) via a crafted redirect_uri parameter pointing outside sanctioned Teams/SharePoint destinations, consistent with the Barracuda-documented blob URL phishing chain.
references:
    - https://blog.barracuda.com/2026/09/09/browser-based-phishing-blob-urls-microsoft-redirects
author: Threadlinqs Team
date: 2026/09/10
tags:
    - attack.resource-development
    - attack.t1583.001
    - attack.t1608.005
    - attack.initial-access
    - attack.t1566.001
    - attack.execution
    - attack.t1204.001
logsource:
    category: mail_delivery
    product: m365
detection:
    selection_attachment:
        FileExtension: '.ics'
    selection_display_name:
        SenderDisplayName|contains: 'DocuSign'
    selection_redirect:
        Url|contains:
            - 'login.microsoftonline.com'
            - 'redirect_uri='
    filter_legit_domain:
        SenderFromDomain|endswith:
            - 'docusign.com'
            - 'docusign.net'
    condition: selection_attachment and selection_display_name and selection_redirect and not filter_legit_domain
falsepositives:
    - Legitimate DocuSign calendar invites sent from correctly authenticated docusign.com/docusign.net domains
    - Internal meeting-scheduling automation that legitimately chains through Microsoft OAuth for calendar provisioning
level: high
```

**Known false positives:**

- Legitimate DocuSign calendar invites sent from correctly authenticated docusign.com/docusign.net domains
- Internal scheduling automation that legitimately routes through Microsoft OAuth for calendar/meeting provisioning

**Tuning notes:** Maintain an allowlist of sanctioned redirect_uri destinations (internal apps, verified partner SSO) to reduce noise; extend the DocuSign-impersonation check to other frequently spoofed e-signature/collab brands (Adobe Sign, Dropbox Sign) since this campaign class is not brand-exclusive.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- DocuSign-Themed Calendar Invite With Crafted Microsoft OAuth Redirect (KQL) (locked: unlock with TL Creds)
- External CDN Resource Fetch and CSP Blob-URI Violation Consistent With In-Browser Phishing Page Construction (KQL) (locked: unlock with TL Creds)
- Low-Jitter postMessage-Style Polling to [indicator] Correlated With OAuth Credential Submission (KQL) (locked: unlock with TL Creds)
- DocuSign-Themed Calendar Invite With Crafted Microsoft OAuth Redirect (Sigma) (locked: unlock with TL Creds)
- External CDN Resource Fetch and CSP Blob-URI Violation Consistent With In-Browser Phishing Page Construction (Sigma) (locked: unlock with TL Creds)
- Low-Jitter postMessage-Style Polling to [indicator] Correlated With OAuth Credential Submission (Sigma) (locked: unlock with TL Creds)
- External CDN Resource Fetch and CSP Blob-URI Violation Consistent With In-Browser Phishing Page Construction (SPL) (locked: unlock with TL Creds)
- Low-Jitter postMessage-Style Polling to [indicator] Correlated With OAuth Credential Submission (SPL) (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sample indicators (2 of 8)

Defanged, TLP:CLEAR.

- Domain: `cdn[.]bloom[.]io`
- Domain: `login[.]microsoftonline[.]com`

Full set of 8 indicators unlocks with TL Creds: https://threadlinqs.com/tl-creds

## Sources

- [Email attacks evade detection by generating phishing pages directly inside the victim's browser](https://blog.barracuda.com/2026/09/09/browser-based-phishing-blob-urls-microsoft-redirects)
- [Cybercriminals are building phishing pages that exist only inside victims' browsers](https://www.helpnetsecurity.com/2026/09/10/browser-based-phishing-blob-urls-microsoft-oauth/)
- [New Phishing Attack Creates Malicious Pages Inside the Victim's Browser](https://www.securityweek.com/new-phishing-attack-creates-malicious-pages-inside-the-victims-browser/)
- [Barracuda Research Finds Phishing Attack That Builds Fake Login Pages Inside The Victim's Browser, Leaving No Trail For Security Tools](https://smbtech.au/news/barracuda-research-finds-phishing-attack-that-builds-fake-login-pages-inside-the-victims-browser-leaving-no-trail-for-security-tools/)
- [Email attacks evade detection by generating phishing pages directly inside the victim's browser, Barracuda research finds](https://itwire.com/business-it-news/security/email-attacks-evade-detection-by-generating-phishing-pages-directly-inside-the-victims-browser-barracuda-research-finds)
- [Phishing Hides Pages in Browser via Blob URLs, Teams Lure](https://www.cloudlinktech.com/news/phishing-hides-pages-browser-blob-urls-teams-docusign/)
- [Barracuda spots blob URL phishing in Microsoft browser](https://itbrief.asia/story/barracuda-spots-blob-url-phishing-in-microsoft-browser)
- [Barracuda Releases New Research: Email attacks evade detection by generating phishing pages directly inside the victim's browser](https://vmblog.com/news/barracuda-releases-new-research-email-attacks-evade-detection-by-generating-phishing-pages-directly-inside-the-victims-browser/)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-2430
