Back to Intelligence

BigBear 2.0 Evilginx2 PhaaS Campaign: AiTM Microsoft 365 Credential Theft — OTX Detection Pack

SA
Security Arsenal Team
September 8, 2026
11 min read

A newly rebranded phishing-as-a-service (PhaaS) operation tracked as BigBear 2.0 is actively harvesting Microsoft 365 credentials and session tokens at global scale. Built on the well-known Evilginx2 adversary-in-the-middle (AiTM) framework and operated by a threat actor identifying as 'General Boss', the campaign targets organizations across Technology, Energy, Healthcare, Finance, and Government sectors, with victims observed in France, Germany, India, New Zealand, Saudi Arabia, and the British Indian Ocean Territory.

This briefing synthesizes live OTX pulse data into detection engineering content your SOC can deploy today.

Threat Summary

In June 2026, researchers uncovered BigBear 2.0 as a rebrand and operational evolution of Evilginx2-based phishing infrastructure. The campaign's objective is unambiguous: theft of Microsoft 365 credentials and, critically, authenticated session cookies — enabling the operator and downstream customers to bypass multi-factor authentication entirely.

The attack chain follows the mature AiTM PhaaS playbook:

  1. Lure delivery — Phishing emails directing victims to attacker-controlled proxy domains impersonating Microsoft 365 login portals.
  2. AiTM proxy interception — BigBear 2.0 nodes, using the 'offy' phishlet configuration, transparently proxy the genuine Microsoft login flow. Victims see a legitimate-looking, fully functional Microsoft 365 sign-in page because they are, in effect, interacting with the real site through the attacker's relay.
  3. Credential + session capture — Usernames, passwords, and post-authentication session tokens (including MFA-satisfied sessions) are harvested in real time.
  4. Account takeover — Captured session cookies are replayed to access mailboxes, SharePoint, and Teams, typically enabling business email compromise (BEC), internal phishing pivots, and data exfiltration.

The operation runs on 42 VPS nodes hosted primarily on Vultr infrastructure, with geo-matched residential proxying used to make login attempts appear to originate from plausible victim geographies — defeating naive impossible-travel and geo-velocity detections.

Threat Actor / Malware Profile

Operator: General Boss Platform: BigBear 2.0 (rebranded Evilginx2-based PhaaS) Business model: Phishing-as-a-Service — infrastructure and phishlets are rented to criminal customers, meaning victimology is broad and lure themes vary by renter.

Distribution method: Email-delivered lures (credential harvesting themes, document sharing, HR/finance pretexts) embedding links to attacker domains. The observed indicator domains — including dronalms.com, ccpipharma.com, knowncontractor.com, and hnospascualfadon.com — suggest sector-tailored lure branding (pharmaceutical, contractor/vendor, and hospital-themed naming consistent with Healthcare and Finance targeting).

Payload behavior: BigBear 2.0 is not endpoint malware — there is no dropped binary. The 'payload' is a reverse-proxy phishing node that:

  • Proxies the genuine Microsoft 365 authentication flow in real time (AiTM)
  • Captures credentials and authenticated session cookies mid-transaction
  • Uses the 'offy' phishlet configuration tuned for Microsoft 365
  • Routes captured sessions through geo-matched residential proxies for replay

C2 / infrastructure communication: The 42-node VPS fleet (predominantly Vultr-hosted, with observed IPs in the 130.94.x.x and 38.54.x.x ranges) serves phishing pages over HTTPS with valid TLS certificates. Observed nodes communicate captured session data back to operator-controlled panels within the PhaaS platform.

Persistence mechanism: Persistence is achieved inside the victim's cloud tenant, not on the endpoint — via replayed session cookies, and frequently via attacker-added MFA methods, mailbox forwarding rules, and OAuth consent grants after initial access.

Anti-analysis techniques: Geo-matched residential proxy egress, bot/scanner filtering on phishing pages (security vendor IP ranges and sandboxes are served benign content), short-lived redirect chains, and valid TLS certificates to defeat URL-reputation-only controls.

IOC Analysis

The pulse contains 33 indicators across two primary types:

  • Domains (e.g., dronalms.com, ccpipharma.com, knowncontractor.com, hnospascualfadon.com): AiTM proxy nodes hosting the phishing pages. These should be blocked at the DNS layer, secure web gateway, and email gateway. Critically, hunt for any user who resolved or browsed to these domains in the last 90 days — a visit almost certainly means a credential was entered.
  • IPv4 addresses (e.g., 130.94.113.184, 130.94.82.180, 130.94.82.230, 38.54.124.58): VPS hosting infrastructure. Block at egress firewall/proxy and hunt in network, proxy, and DNS telemetry for historical connections.

Operationalization guidance:

  • Load all 33 IOCs into your TI platform (MISP, ThreatConnect, Sentinel Watchlists) with a high-confidence, block action and a 90-day retrohunt window.
  • Because AiTM phishing produces no endpoint artifact, prioritize network-layer hunting (DNS queries, web proxy logs, TLS SNI) and identity-layer hunting (Entra ID sign-in logs showing session anomalies, unfamiliar ASN/session token reuse).
  • Tools: dnstwist for monitoring typosquat variants of your own M365 federation domains; MISP/OTX integrations for indicator sync; Sentinel watchlists for correlation; greynoise/shodan to fingerprint sibling nodes on the same Vultr netblocks.

Detection Engineering

YAML
---
title: Outbound Connection to BigBear 2.0 Evilginx2 AiTM Phishing Infrastructure
id: 7c3f1a2e-9b4d-4e1f-a8c6-2d5b7f0e9a11
status: experimental
description: Detects DNS resolution or network connections to known BigBear 2.0 / Evilginx2 adversary-in-the-middle phishing proxy domains and hosting IPs observed in the 'General Boss' PhaaS campaign targeting Microsoft 365 credentials.
references:
    - https://www.cloudsek.com/blog/tracking-bigbear-2-0-evilginx2-phishing-campaign
author: Security Arsenal Threat Intelligence
date: 2026/09/08
tags:
    - attack.credential_access
    - attack.t1557
    - attack.t1557.002
    - attack.t1566
    - attack.t1566.002
logsource:
    category: dns
product: windows
selection:
    QueryName|contains:
        - 'dronalms.com'
        - 'ccpipharma.com'
        - 'knowncontractor.com'
        - 'hnospascualfadon.com'
condition: selection
falsepositives:
    - Threat intelligence platform enrichment lookups
level: high
---
title: Microsoft 365 Sign-In From Anonymous or Proxy ASN Following Session Token Issuance
id: 8d4e2b3f-0c5e-5f2a-b9d7-3e6c8a1f0b22
status: experimental
description: Detects Entra ID sign-in patterns consistent with AiTM session token replay - successful authentication from hosting provider or proxy ASNs (e.g., Vultr/Choopa, Constant) with new device or unfamiliar session characteristics, indicative of Evilginx2/BigBear 2.0 credential theft and MFA bypass via stolen cookies.
references:
    - https://www.cloudsek.com/blog/tracking-bigbear-2-0-evilginx2-phishing-campaign
author: Security Arsenal Threat Intelligence
date: 2026/09/08
tags:
    - attack.credential_access
    - attack.t1557.002
    - attack.t1539
    - attack.t1078
    - attack.t1078.004
logsource:
    product: azure
    service: signinlogs
selection:
    network_asn|contains:
        - 'CHOOPLA'
        - 'AS20473'
        - 'Vultr'
        - 'Constant Company'
    status: 'Success'
condition: selection
falsepositives:
    - Users legitimately working from VPN providers or corporate egress hosted on VPS infrastructure
    - IT administrator testing from cloud hosts
level: high
---
title: Suspicious Inbox Forwarding Rule Creation Following Suspected AiTM Compromise
id: 9e5f3c4a-1d6f-6a3b-c0e8-4f7d9b2a1c33
status: experimental
description: Detects creation of mailbox inbox rules that forward, redirect, or delete messages - a common post-compromise action after BigBear 2.0/Evilginx2 session theft enables BEC and internal phishing pivots from the hijacked mailbox.
references:
    - https://www.cloudsek.com/blog/tracking-bigbear-2-0-evilginx2-phishing-campaign
author: Security Arsenal Threat Intelligence
date: 2026/09/08
tags:
    - attack.collection
    - attack.t1114
    - attack.t1114.003
    - attack.persistence
    - attack.t1098
logsource:
    product: office365
    service: exchange
selection:
    Operation:
        - 'New-InboxRule'
        - 'Set-InboxRule'
    Parameters|contains:
        - 'ForwardTo'
        - 'RedirectTo'
        - 'ForwardAsAttachmentTo'
        - 'DeleteMessage'
condition: selection
falsepositives:
    - Legitimate user-created forwarding rules for approved business workflows
level: medium
KQL — Microsoft Sentinel / Defender
// BigBear 2.0 / Evilginx2 AiTM Phishing Infrastructure Hunt — Microsoft Sentinel
// Hunts endpoint network events and DNS for known campaign IOCs, then pivots to identity impact
let PhishDomains = dynamic(["dronalms.com","ccpipharma.com","knowncontractor.com","hnospascualfadon.com"]);
let PhishIPs = dynamic(["130.94.113.184","130.94.82.180","130.94.82.230","38.54.124.58"]);
let NetHits =
    DeviceNetworkEvents
    | where TimeGenerated > ago(90d)
    | where RemoteUrl has_any (PhishDomains) or RemoteIP in (PhishIPs)
    | project TimeGenerated, DeviceName, InitiatingProcessAccountName, InitiatingProcessFileName,
              InitiatingProcessCommandLine, RemoteUrl, RemoteIP, ActionType;
let DnsHits =
    DeviceEvents
    | where TimeGenerated > ago(90d)
    | where ActionType == "DnsQueryResponse"
    | extend AdditionalFields = parse_json(AdditionalFields)
    | extend DnsQuery = tostring(AdditionalFields.DnsQueryString)
    | where DnsQuery has_any (PhishDomains)
    | project TimeGenerated, DeviceName, DnsQuery;
let ImbibedUsers = NetHits | distinct InitiatingProcessAccountName;
NetHits
| union DnsHits
| order by TimeGenerated desc;
// Pivot: check whether users who hit the phishing infra show anomalous M365 sign-ins
SigninLogs
| where TimeGenerated > ago(90d)
| where UserPrincipalName has_any (ImbibedUsers)
| where ResultType == 0
| extend NetworkDetails = tostring(parse_json(NetworkLocationDetails))
| where NetworkDetails has_any ("Choopa","Vultr","AS20473","Constant")
   or IPAddress in (PhishIPs)
| project TimeGenerated, UserPrincipalName, IPAddress, Location, AppDisplayName,
          DeviceDetail, NetworkDetails, AuthenticationRequirement, SessionId
| order by TimeGenerated desc
PowerShell
<#
.SYNOPSIS
    BigBear 2.0 / Evilginx2 AiTM Phishing IOC & Exposure Hunt Script
.DESCRIPTION
    Hunts Windows endpoints for evidence of user interaction with known BigBear 2.0
    phishing infrastructure (General Boss PhaaS campaign, OTX pulse 2026-09-08).
    Checks DNS client cache, browser history artifacts, proxy/network connections,
    and flags users requiring immediate credential + session revocation.
    Run elevated on suspect endpoints, or deploy fleet-wide via your EDR/remote shell.
#>

$PhishDomains = @('dronalms.com','ccpipharma.com','knowncontractor.com','hnospascualfadon.com')
$PhishIPs     = @('130.94.113.184','130.94.82.180','130.94.82.230','38.54.124.58')
$findings = @()

Write-Host "[*] BigBear 2.0 AiTM Phishing Hunt — $(Get-Date -Format 'yyyy-MM-dd HH:mm:ss')" -ForegroundColor Cyan

# --- 1. DNS client cache for phishing domain resolution ---
Write-Host "[*] Checking DNS client cache..." -ForegroundColor Yellow
try {
    $dns = Get-DnsClientCache -ErrorAction Stop
    foreach ($d in $PhishDomains) {
        $hits = $dns | Where-Object { $_.Entry -like "*$d*" }
        if ($hits) {
            $findings += [pscustomobject]@{Check='DNS Cache'; Indicator=$d; Detail=($hits | Select-Object -First 1 | Out-String).Trim(); Risk='HIGH'}
            Write-Host "  [!] DNS cache hit: $d" -ForegroundColor Red
        }
    }
} catch { Write-Host "  [-] DNS cache query failed: $_" -ForegroundColor DarkGray }

# --- 2. Active/historical TCP connections to phishing IPs ---
Write-Host "[*] Checking network connections to phishing IPs..." -ForegroundColor Yellow
$conns = Get-NetTCPConnection -ErrorAction SilentlyContinue | Where-Object { $PhishIPs -contains $_.RemoteAddress }
if ($conns) {
    foreach ($c in $conns) {
        $proc = Get-Process -Id $c.OwningProcess -ErrorAction SilentlyContinue
        $findings += [pscustomobject]@{Check='Net Connection'; Indicator=$c.RemoteAddress; Detail="PID $($c.OwningProcess) ($($proc.ProcessName)) state $($c.State)"; Risk='CRITICAL'}
        Write-Host "  [!!] Active connection to $($c.RemoteAddress) by $($proc.ProcessName)" -ForegroundColor Red
    }
}

# --- 3. Browser history artifacts (Chrome/Edge) for phishing domain visits ---
Write-Host "[*] Checking browser history artifacts..." -ForegroundColor Yellow
$histPaths = @(
    "$env:LOCALAPPDATA\Google\Chrome\User Data\Default\History",
    "$env:LOCALAPPDATA\Microsoft\Edge\User Data\Default\History"
)
foreach ($hp in $histPaths) {
    if (Test-Path $hp) {
        $tmp = Join-Path $env:TEMP ("hist_" + [guid]::NewGuid().ToString('N') + ".db")
        Copy-Item $hp $tmp -Force -ErrorAction SilentlyContinue
        foreach ($d in $PhishDomains) {
            if ((Get-Content $tmp -Raw -ErrorAction SilentlyContinue) -match [regex]::Escape($d)) {
                $findings += [pscustomobject]@{Check='Browser History'; Indicator=$d; Detail="Found in $hp"; Risk='HIGH'}
                Write-Host "  [!] Browser history artifact: $d in $hp" -ForegroundColor Red
            }
        }
        Remove-Item $tmp -Force -ErrorAction SilentlyContinue
    }
}

# --- 4. Proxy auto-config / system proxy tampering check ---
Write-Host "[*] Checking for proxy tampering..." -ForegroundColor Yellow
$proxyKey = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings'
$proxy = Get-ItemProperty -Path $proxyKey -ErrorAction SilentlyContinue
if ($proxy.ProxyEnable -eq 1 -and $proxy.ProxyServer -notmatch '^(localhost|127\.)' -and -not $proxy.ProxyServer.StartsWith($env:USERDOMAIN)) {
    $findings += [pscustomobject]@{Check='Proxy Config'; Indicator=$proxy.ProxyServer; Detail='Non-standard user proxy configured - validate legitimacy'; Risk='MEDIUM'}
}

# --- 5. Recent logon events indicating possible session misuse (local side) ---
Write-Host "[*] Pulling recent successful logons for correlation with Entra ID..." -ForegroundColor Yellow
$logons = Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4624; StartTime=(Get-Date).AddDays(-14)} -MaxEvents 500 -ErrorAction SilentlyContinue |
    Where-Object { $_.Message -match 'Logon Type:\s+10' } | Select-Object -First 20
if ($logons) { Write-Host "  [i] $($logons.Count) remote logons in last 14 days — correlate with Entra sign-in logs" -ForegroundColor Cyan }

# --- Summary ---
Write-Host "`n===== HUNT RESULTS =====" -ForegroundColor Cyan
if ($findings.Count -gt 0) {
    $findings | Format-Table -AutoSize
    $findings | Export-Csv -Path ".\BigBear2_Hunt_$(Get-Date -Format 'yyyyMMdd_HHmmss').csv" -NoTypeInformation
    Write-Host "[!] $($findings.Count) finding(s) exported. ESCALATE: revoke user sessions + reset credentials immediately." -ForegroundColor Red
} else {
    Write-Host "[+] No BigBear 2.0 indicators found on this endpoint." -ForegroundColor Green
}

Response Priorities

Immediate (0–4 hours):

  • Block all 33 OTX indicators (domains + IPs) at DNS, secure web gateway, email gateway, and egress firewall. Enable TLS SNI-based blocking since nodes use valid certificates.
  • Run the KQL hunt and PowerShell sweep for any user who resolved or visited phishing infrastructure in the past 90 days.
  • For every user with a hit: treat as compromised — revoke all Entra ID refresh tokens and active sessions (Revoke-MgUserSignInSession / "Require re-register MFA"), force password reset, and invalidate session cookies.

24 Hours:

  • Audit compromised accounts' Entra ID sign-in logs for anomalous sessions from hosting-provider ASNs (Vultr/Choopa, AS20473) or unfamiliar geographies — session replay is the primary post-exploitation path.
  • Review mailbox rules (Get-InboxRule), OAuth consent grants, added MFA methods, and sent items for BEC or internal phishing pivots.
  • Search mail flow for other recipients of the same lure campaigns and expand the compromised-user list accordingly.
  • Notify affected business units; if Finance mailboxes were accessed, initiate out-of-band verification of any pending payment changes.

1 Week:

  • Deploy phishing-resistant MFA (FIDO2 passkeys / certificate-based auth) for privileged and high-risk users — AiTM proxying defeats OTP and push-based MFA by design.
  • Enforce Conditional Access policies requiring compliant/hybrid-joined devices and token protection so stolen session cookies cannot be replayed from attacker infrastructure.
  • Enable continuous access evaluation (CAE) and tighten session lifetimes; configure anomaly-based sign-in alerting for ASN/device mismatches.
  • Add AiTM-phishing-specific content to security awareness training — emphasize that a "working, padlocked Microsoft login page" can still be a proxy, and mandate URL verification before credential entry.
  • Deploy the Sigma rules above across your SIEM coverage and tune ASN-based sign-in detections against your known corporate egress ranges.

Related Resources

Security Arsenal Incident Response Managed SOC & MDR Services AlertMonitor Threat Detection From The Dark Side Intel Hub

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.