Last updated: August 19, 2026 at 1:47 AM UTC
All 741 Vulnerability 286 Breach 129 Threat 319 Defense 7
Tag: m365 (6 articles)Clear

HollowGraph hides commands and stolen files in Microsoft 365 calendar events

Group-IB detailed HollowGraph, a Windows implant that uses the calendar of a compromised Microsoft 365 mailbox as a two-way dead drop rather than contacting an attacker-owned server. Authenticating to the Microsoft Graph API with hard-coded tenant, client, and secret values stored in a file named to look like a log, it reads tasking from attachments on calendar events buried at a date in 2050, and exfiltrates by creating its own far-future events with encrypted attachments. A separate DNS tunnel refreshes its credentials. Because the traffic is genuine Graph activity, there is no vulnerability to patch and network controls keyed to attacker infrastructure see nothing.

Check
Hunt Microsoft 365 audit logs for calendar events dated far in the future and for automated calendar and attachment access by service principals rather than interactive users.
Affected
Microsoft 365 organizations where an account or registered application is compromised; the implant blends command and control into legitimate Graph API traffic, so perimeter controls and destination-based blocking do not see it.
Fix
Restrict and audit which client-credential applications can reach Graph, alert on newly created client secrets, monitor mailbox audit logs for anomalous calendar operations, and watch endpoints for the campaign's known artifacts.

Exposed server unmasks three Evilginx phishing crews stealing Microsoft 365 sessions

A phishing operator left a Python web server exposed with directory listing on, letting researchers at Lexfo lift the entire toolkit and pivot to two more operators running three Microsoft 365 phishing campaigns. Each used a custom fork of the open-source Evilginx proxy to steal live session cookies and tokens, defeating multi-factor authentication by relaying the real login. The largest campaign ran over a year, logging 218 captured accounts, mostly corporate mailboxes, and a token file left in a public repository held 97 live Microsoft tokens. The report stresses two different MFA-bypass methods appeared, one proxying the real login and one abusing the device-code flow, which require different defenses to stop.

Check
Assess your Microsoft 365 defenses against both adversary-in-the-middle proxying and device-code abuse, hunt for suspicious token use and session reuse from unusual locations, and review Conditional Access coverage of the device-code flow.
Affected
Microsoft 365 organizations, especially corporate mailboxes; Evilginx-style proxies steal live session tokens to bypass MFA, and passkeys stop the proxy method but not the separate device-code abuse technique.
Fix
Enforce phishing-resistant authentication like passkeys against proxy phishing, use Conditional Access to block or limit the device-code flow, revoke suspicious sessions and tokens, and monitor sign-in logs for token reuse across locations.

Forg365 phishing service uses AI to steal Microsoft 365 accounts and stay in

A new phishing-as-a-service platform called Forg365 is built to steal Microsoft 365 accounts, combining adversary-in-the-middle and device-code phishing with AI-generated lures created directly in its control panel. Researchers at ZeroBEC found the panel lets operators build campaigns, configure malicious OAuth apps, generate and refine phishing emails with AI, and monitor compromised mailboxes for keywords, all in one place. It also ships a browser extension that silently refreshes session cookies through an OAuth flow, giving attackers ongoing access without re-authenticating. The operators deliver lures posing as business documents, using legitimate email-sending infrastructure to slip past filters. The researchers note AI is lowering the cost of both writing phishing content and building phishing platforms.

Check
Hunt for adversary-in-the-middle and device-code phishing against Microsoft 365, review OAuth app consents and unexpected browser extensions, and check for mailbox rules or session tokens giving attackers persistent access.
Affected
Microsoft 365 users targeted by business-document lures; Forg365 captures session tokens to bypass multi-factor authentication and uses a browser extension to keep access alive even after passwords or sessions are reset.
Fix
Enforce phishing-resistant methods like passkeys, apply Conditional Access to limit device-code and token sign-ins, review and restrict OAuth app consents and browser extensions, and monitor for anomalous token use.

Attackers phone Microsoft 365 users to walk them through fake passkey setup

Okta warns of a campaign that phones Microsoft 365 users and talks them through what looks like setting up a passkey, but is actually a phishing kit that hands their account to the attacker. Active since April, the operators register passkey-themed domains and call targets, exploiting unfamiliarity with how passkeys really work. The kit mimics Microsoft's passkey enrollment without registering a real passkey, and pushes the victim to "save a recovery key" that the attacker controls, capturing the access needed to take over the account. The campaign, aimed at extortion, notably targets the passkey adoption process itself, turning a security upgrade into a social-engineering opening.

Check
Tell staff that Microsoft passkey setup happens through a device system prompt, not a phone call or web form, and that anyone calling to walk them through passkey registration is suspicious.
Affected
Microsoft 365 users unfamiliar with passkey enrollment; a convincing phone call plus a look-alike registration page can trick them into handing over the access an attacker needs to take over the account.
Fix
Train users on the genuine passkey enrollment flow, restrict who can register new authentication methods and recovery keys, monitor Entra for unexpected authentication-method changes, and verify unsolicited passkey calls internally.

ARToken phishing service steals Microsoft 365 tokens and survives password resets

Cisco Talos detailed ARToken, a phishing-as-a-service platform tied to the EvilTokens operation that is built to compromise Microsoft 365. It abuses Microsoft's device-code sign-in flow to capture authentication tokens rather than passwords, bypassing multi-factor authentication, then upgrades to a Primary Refresh Token so access survives even after the victim resets their password. Its panel exposed more than eighty API endpoints for mailbox takeover, SharePoint and OneDrive theft, and automated business email compromise, including hidden inbox rules and multi-mailbox monitoring. The lures are targeted, abusing real vendor invoice relationships and pointing to look-alike SharePoint tenants on legitimate Microsoft infrastructure so the emails are harder to flag.

Check
Hunt for unexpected device-code authentication prompts during normal work, unusual device registrations, and new inbox forwarding or hiding rules, and audit which accounts hold Primary Refresh Tokens or long-lived sessions.
Affected
Microsoft 365 organizations, especially finance and accounts-payable staff hit by vendor-invoice lures; captured tokens bypass MFA and Primary Refresh Token persistence keeps attackers in even after a password reset.
Fix
Restrict or monitor the device-code authentication flow with Conditional Access, revoke sessions and Primary Refresh Tokens on suspicion, enforce phishing-resistant methods like passkeys, and train staff to treat unexpected device-code prompts warily.

Azure CLI password spray compromises 78 Microsoft accounts by bypassing MFA

Huntress is tracking a large automated password-spray campaign against Microsoft 365 that has made more than 81 million login attempts through the Azure CLI in two weeks and broken into 78 accounts across 64 organizations. The attackers replay old username and password pairs from breach data against an authentication flow that sends credentials straight to the token endpoint without triggering interactive multi-factor authentication, so weak or reused passwords give them direct access. Several victims had MFA, but it was scoped only to admins, only to certain apps, or only to untrusted locations, and so did not cover this path. The traffic comes from infrastructure whose address ranges trace back to China.

Check
Review whether your multi-factor authentication and Conditional Access policies cover every sign-in path, including the Azure CLI and token-endpoint flows, not just web portals and admin accounts, and hunt for password-spray bursts.
Affected
Microsoft 365 organizations with weak or reused passwords, incomplete MFA, or Conditional Access gaps; attackers use a credential flow that skips interactive MFA to break in through the Azure CLI.
Fix
Enforce phishing-resistant MFA across all users, apps, and authentication flows, block legacy and password-based credential grants, apply Conditional Access to CLI access, and monitor sign-in logs for spray patterns and suspicious networks.