Comparing BigBear to other PaaS platforms
BigBear is the latest in a series of phishing-as-a-service platforms discovered since 2022. Each iteration improves stealth and reliability.
| Platform | Discovered | Notable features | Affected accounts |
|---|
| EvilProxy | 2022 | First major AitM PaaS | Thousands |
| Caffeine | 2024 | Microsoft 365 + Google Workspace focus | 5,000+ |
| NakedPages | 2024 | Microsoft 365 session hijacking | 500+ |
| Tycoon 2FA | 2024 | Open-source, customizable | 1,000+ |
| BigBear | 2026 | Microsoft 365 focused, broad targeting | 258 (confirmed) |
Source: CrowdStrike AitM phishing analysis, 2026; BleepingComputer PaaS tracker, September 2026; Mandiant phishing service database, 2026.
Indicators of BigBear compromise
Three Microsoft 365 audit log patterns indicate possible BigBear compromise. Detection lag is typically days to weeks.
| Indicator | Log location | Detection method |
|---|
| Impossible-travel sign-ins | Microsoft Entra ID sign-in logs | Geographic anomaly detection |
| Session token reuse across multiple IPs | Microsoft 365 unified audit log | Token correlation analysis |
| New inbox rules forwarding email externally | Microsoft 365 unified audit log | Mailbox rule auditing |
| OAuth consent grants to unknown apps | Microsoft Entra ID audit logs | Consent grant monitoring |
Source: Microsoft Security Response Center AitM defense guidance, September 2026; BleepingComputer detection rules, September 2026.
Defense-in-depth strategy for organizations
Six layered controls reduce BigBear risk even if user credentials are compromised. The defense assumes some users will be phished.
| Control | Effectiveness | Implementation effort |
|---|
| Migrate to FIDO2/passkey MFA | Highest | Medium (3-6 months for large orgs) |
| Microsoft 365 Conditional Access with compliant device requirement | High | Medium |
| Browser-level phishing protection (Microsoft Edge SmartScreen, etc.) | Medium | Low |
| Disable legacy authentication protocols | Medium | Low |
| Session token revocation policies | Medium | Low |
| User phishing awareness training (Pareto) | Low for AitM | Low |
Source: Microsoft Security Response Center defense-in-depth, 2026; CrowdStrike AitM mitigation guide, 2026.
Microsoft's response and recommended migration path
Microsoft has accelerated its push toward phishing-resistant MFA and number matching in Microsoft Authenticator. The 2026 BigBear campaign is the latest evidence that SMS and TOTP are no longer adequate.
Microsoft announced in August 2026 that all Entra ID tenants will be required to use number matching for Microsoft Authenticator push notifications by year-end. Number matching requires the user to type a number from the sign-in screen into the authenticator app, preventing AitM proxies from simply forwarding the push. Microsoft also recommends deploying FIDO2 keys for all privileged accounts (Entra ID admins, Exchange admins, security admins) by Q2 2027. The combined posture of number matching plus FIDO2 keys for high-privilege accounts raises the bar significantly against BigBear-style AitM attacks (Microsoft Security Response Center, September 2026; Entra ID roadmap, August 2026).
FAQs
The questions above cover what BigBear is, how it bypasses MFA, which 258 organizations were affected, how it compares to other PaaS platforms, which MFA methods protect against AitM, and what organizations should do to defend themselves.