Suped

Forg365 phishing platform targets Microsoft 365 with device code attacks

News
Published 10 Jul 2026
Updated 12 Nov 2026
11 min read
Summarize with
Forg365 phishing platform targeting Microsoft 365 through device-code authentication.
Updated on 12 Nov 2026: We clarified device-code blocking, sign-in hunting, and token containment, and added steps for reporting suspicious code requests.
Forg365 is a Telegram-distributed phishing-as-a-service (PhaaS) platform targeting Microsoft 365 accounts through device-code phishing and adversary-in-the-middle (AiTM) attacks. ZeroBEC published its Forg365 research on July 9, 2026, linking a business-document email lure to token management and post-compromise mailbox operations.
ZeroBEC traced the delivered lure through legitimate email delivery and hosted-content infrastructure, then followed the campaign into Cloudflare-hosted landing pages, device-code phishing, AiTM routing, and session-persistence tooling. The delivery providers were infrastructure used in the campaign, not evidence that those providers were compromised.
Review device-code exposure
The July report documents an observed campaign, not a continuously verified list of active infrastructure. Check your tenant's current device-code controls. Microsoft's security defaults guidance states that security defaults block this flow, including for new tenants created since July 1, 2026. Tenants using Conditional Access need their own device-code policy.

What ZeroBEC found

ZeroBEC's research starts with a delivered lure and follows the chain into the operator platform. The lure used a business-document pretext, legitimate email delivery infrastructure, hosted image or tracking content, and redirect logic that sent the target toward either a device-code branch or an AiTM branch.
The observed panel exposed accounts, invitations, OAuth app setup, redirect links, SVG generation, campaign sending, SMTP profiles, SMTP rotation, AI-assisted lure generation, token vaulting, account intelligence, keyword listening, viewer links, and browser-extension support. July onboarding offered a five-day trial, $400 monthly access, and $3,800 annual access.

Component

Observed use

Defensive action

Telegram
Sales and support
Track operator patterns
Email delivery infrastructure
Mail delivery
Correlate headers
Hosted-content infrastructure
Hosted content
Inspect HTML
Cloudflare
Landing layer
Check redirects
Campaign delivery infrastructure
Campaign sending
Cluster artifacts
ForgCookie
SSO refresh
Revoke sessions and check token activity
Observed Forg365 components and immediate defensive meaning.
ZeroBEC's assessment does not establish common ownership with other phishing platforms. Use its campaign-linked domains and IP addresses as historical hunting pivots.
Forg365 device-code phishing chain linking an email lure to Microsoft Graph access and mailbox actions.
Forg365 device-code phishing chain linking an email lure to Microsoft Graph access and mailbox actions.

Why SPF, DKIM, and DMARC do not stop device-code phishing

The email side of Forg365 is a warning about trust boundaries. Legitimate delivery and hosting infrastructure can make malicious mail resemble normal SaaS traffic. A message can arrive through a familiar mail service, load hosted assets, pass through a wrapper, and still lead to identity compromise. Sending reputation alone is not enough when the downstream action authorizes Microsoft 365 access.
SPF authorizes a sending host for an SMTP identity, and DKIM verifies a domain signature over signed message content. DMARC checks whether a passing SPF or DKIM identity meets its domain-matching requirements for the visible From domain and publishes a handling policy. These checks do not establish safe intent. A phishing message sent through an authorized or compromised account can pass DMARC without a protocol bypass.
Authentication control reality
  1. SPF: Checks whether the sending host is authorized for the envelope-from or HELO identity.
  2. DKIM: Verifies a domain signature and detects changes to the signed portions of a message.
  3. DMARC: Passes when SPF or DKIM passes with the required domain match to the visible From domain.
  4. Intent: Requires analysis of content, URLs, identity events, and mailbox behavior.
Suped's product supports the sender-authentication part of the investigation. Suped's DMARC monitoring helps teams inventory services sending for their domains, find alignment failures, and separate approved mail paths from unknown sources. It does not stop device-code authorization, but cleaner authentication data gives investigators more reliable email evidence to correlate with Entra and mailbox events.
Suped DMARC dashboard showing email volume, authentication health, and source breakdown

How the device-code branch works

Device-code phishing abuses the legitimate OAuth 2.0 device authorization grant, which supports devices with limited input capabilities. The attacker-controlled client requests a device code and user code, then the target is told to enter the user code on a real Microsoft verification page. While the target signs in and completes any required MFA or consent, the client polls Microsoft's token endpoint. Successful authorization gives that client an access token and, when permitted and requested with offline_access, a refresh token. Access depends on the token audience, granted permissions, and the user's privileges; it is not automatically tenant-wide access.
ZeroBEC observed Microsoft Authentication Broker activity, device-code transfer method telemetry, non-interactive Graph activity, and device registrations carrying a Forg365 prefix. Hunt for related authorization, follow-on token use, Graph access, device registration, and mailbox operations without assuming every compromise produces every event in that order.
Device-code branch
  1. User step: Victim enters a code into a Microsoft authentication flow.
  2. Telemetry: Look for device code flow, Broker activity, Graph access, and new devices.
  3. Risk: MFA success can authorize the attacker's client and requested permissions.
AiTM branch
  1. User step: Victim reaches a Microsoft-styled sign-in path controlled by the operator.
  2. Telemetry: Look for route tokens, session cookies, redirects, and decoy behavior.
  3. Risk: The proxy can capture session cookies after sign-in; traffic classification can hide the real page from scanners.
The split matters because a clean password reset alone is too narrow. If an attacker has refresh-token material, a registered device, or mailbox-level access paths, the response needs to revoke sessions and inspect identity and mailbox state together.

How to recognize and report a device-code lure

A document-sharing request that asks you to copy a code into a Microsoft sign-in page needs a separate check. Microsoft's device-code research explains that the page can be legitimate while the code authorizes an attacker-controlled session. A successful MFA check does not validate the reason for the request.
  1. Enter a device code only when you initiated an approved device or application setup. Treat codes supplied in unexpected email as suspicious.
  2. Check an unexpected document request with the sender through a known contact method. Do not use contact details supplied only in that message.
  3. Report the original message using your organization's reporting process. Preserve headers and the time of the request for investigation.
  4. If you already entered the code and approved sign-in, contact incident response immediately, even if you never typed a password. Provide the account and approximate approval time.

What to hunt in Entra and Microsoft 365

Start with Entra interactive and non-interactive sign-in logs and audit logs, then connect them to mailbox activity. A device-code sign-in deserves attention when it is followed by Microsoft Graph access from an unfamiliar IP, device registration, mailbox search, forwarding, or new OAuth grants. Begin with the flow indicators before narrowing by application name or user agent.
KQL: direct and protocol-tracked device-code sign-inskusto
union withsource=LogTable SigninLogs, AADNonInteractiveUserSignInLogs | where TimeGenerated >= ago(7d) | where AuthenticationProtocol =~ "deviceCode" or OriginalTransferMethod =~ "deviceCodeFlow" | project TimeGenerated, LogTable, UserPrincipalName, IPAddress, AppDisplayName, ResourceDisplayName, AuthenticationProtocol, OriginalTransferMethod, UserAgent, ResultType, OriginalRequestId | order by TimeGenerated asc
Run this candidate query in a workspace receiving both sign-in log categories and adjust the seven-day window to available retention. It lists events for correlation; it does not establish compromise. Microsoft's protocol-tracking guidance explains why later token refreshes can retain deviceCodeFlow even when the current authentication protocol differs. Compare the account, time, request identifiers, resource, and IP across events, then inspect device-registration audit records and mailbox changes.
  1. Flow fields: Use Authentication protocol for the direct event and Original transfer method for protocol-tracked follow-on sessions.
  2. Client signal: Review Microsoft Authentication Broker and mobile or desktop client activity as supporting evidence, not mandatory filters.
  3. Graph use: Review ResourceDisplayName for Microsoft Graph and investigate unusual access or node-style user agents after a device-code event.
  4. Device names: Search for new devices with Forg365-prefixed names or unfamiliar patterns.
  5. IP change: Compare successful sign-ins with the user's normal networks. Residential addresses can be attacker-controlled; geography alone does not establish compromise.
  6. Historical pivots: Search the relevant July log window for xoday[.]sbs, 139[.]28[.]38[.]129, and Forg365-prefixed device names reported by ZeroBEC. Correlate matches with identity and mailbox events.
Response priority for related signals
Treat combinations of identity and mailbox events as higher risk than isolated events.
Monitor
Single weak signal
Known user, known device, expected application, no mailbox change.
Investigate
Identity anomaly
Device-code sign-in appears for a user without a known need.
Contain
Token risk
Unexplained device-code authorization is followed by Graph access from an unfamiliar IP.
Confirm and contain
Account takeover
Suspicious mailbox changes, device registration, or OAuth grants are confirmed unauthorized.

How to block device-code phishing and contain compromise

Check whether security defaults already block device-code flow. Microsoft's security defaults documentation states that the block applies when those defaults are enabled; new tenants have included it since July 1, 2026. Security defaults have no per-account exceptions. Organizations that need exceptions should use Conditional Access, which requires Microsoft Entra ID P1 or higher, and replace the other security-default protections when migrating.
For tenants using Conditional Access, block device-code flow unless there is a documented business requirement. Inventory direct events with Authentication protocol set to Device code and protocol-tracked sessions with Original transfer method set to Device code flow. Follow Microsoft's policy steps: target the intended users and resources, select Conditions > Authentication flows > Device code flow, and set Grant to Block access. Test in report-only mode before enabling. Keep emergency access accounts excluded and limit business exceptions to approved accounts with named owners and regular reviews. For Teams devices, use specific device resource accounts.
Do not rely on a compliant-device or device-state grant control for this flow. Microsoft documents that the device-code OAuth flow cannot provide the authenticating device's state to the device requesting the code. Tenants that require device-code registration and target all resources must exclude the Device Registration Service resource before enforcement. Keep that exclusion limited to the documented registration requirement.
Compromise response checklist
  1. Block: Block new sign-ins for the affected account while containment is underway.
  2. Revoke: Revoke sessions and refresh tokens after suspected device-code compromise.
  3. Reset: Reset credentials as part of containment and review registered authentication methods before restoring access.
  4. Review: Check consent grants, hidden inbox rules, mailbox-level forwarding, sent items, and deleted items. Investigate suspicious message access and financial conversations for business email compromise (BEC).
  5. Remove: Disable suspicious devices and remove app grants linked to the event.
  6. Correlate: Join email headers, redirects, Entra logs, and mailbox audit data.
Session revocation invalidates refresh tokens, but existing access tokens and application-issued session cookies are not guaranteed to stop immediately. Microsoft's revocation guidance explains that expiry and application enforcement determine when access ends; continuous access evaluation accelerates enforcement for supported sessions. Verify that suspicious activity stops, remove unauthorized mailbox changes, and keep the account blocked until the investigation supports restoring access.
ForgCookie changes the response model. ZeroBEC describes it as an operator-side browser extension designed to refresh Microsoft SSO sessions. That means defenders should not expect to find it installed on the victim's managed browser. Hunt for its effects in tenant telemetry: repeated silent SSO refreshes, non-interactive Microsoft Graph activity, and sessions that survive simple password resets.

How sender trust teams should react

Email security and deliverability teams should treat Forg365 as a reminder that authentication, reputation, and content review work together. SPF, DKIM, and DMARC reduce spoofing and domain abuse. They do not classify a Microsoft 365 device-code authorization request as safe or unsafe by themselves.
Use Suped's email tester with a controlled test message when you need to inspect headers and authentication results. Preserve the original lure for incident response rather than forwarding a live phishing message into a test workflow. Suped's domain health check can help separate DNS and authentication weaknesses from identity-specific signals that belong in Entra and mailbox logs.

Email tester

Send a real email to this address. Suped shows a results button when the test is ready.

?/43tests passed
Suped's product brings DMARC reporting, SPF and DKIM issue detection, and blocklist monitoring into a sender-authentication workflow. MSPs can use the multi-tenant dashboard to review domain authentication and sending services, then investigate device-code and mailbox indicators in the relevant Microsoft tenant logs.
Use blocklist and blacklist checks as a reputation signal, not a verdict. A domain or IP that is clean on a blocklist (blacklist) can still be part of a harmful chain if the message sends a user into device-code authorization. A listing can also reflect abuse elsewhere and needs triage alongside authentication and identity telemetry.

Immediate actions for Microsoft 365 teams

Prioritize controls against the Microsoft 365 account-takeover path documented in the July Forg365 research.
  1. Prevent: Block device-code flow by default and maintain narrow, monitored account exceptions.
  2. Detect: Alert on direct or protocol-tracked device-code sessions followed by Graph access or device registration.
  3. Respond: Block sign-in, revoke sessions, disable suspicious devices, and audit mailbox changes.
  4. Verify: Keep DMARC, SPF, DKIM, and sender inventory clean so email evidence is clear.

Frequently asked questions

Forg365 device-code phishing does not establish a DMARC bypass. DMARC passes when SPF or DKIM passes with the required domain match to the visible From domain. It does not establish safe intent or prevent an authorized account from sending a phishing message.

The victim can authenticate on a real Microsoft page and complete MFA while authorizing an attacker-controlled client. That shifts the key evidence into Entra sign-in logs, token activity, and Graph access.

Tenants without a documented business requirement should block it. Security defaults block device-code flow when enabled. Tenants that need exceptions should use Conditional Access, test in report-only mode, preserve emergency access exclusions, and monitor both direct device-code events and protocol-tracked sessions.

Start with Device code in the Authentication protocol field, Device code flow in Original transfer method, Microsoft Authentication Broker activity, Graph access from new IPs, device registrations, mailbox rules, forwarding, OAuth grants, sent items, and deleted items.

ZeroBEC describes ForgCookie as an operator-side browser extension for Microsoft SSO session refresh. Hunt for its effects in tenant logs. Its absence from the victim's managed browser does not rule out compromise.

A password reset alone does not prove containment. Block sign-in, revoke sessions, disable unauthorized devices, remove malicious consent grants and mailbox changes, and verify that access stops. Existing access tokens or application sessions can remain usable until expiry or supported revocation enforcement.
DMARC monitoring

Start monitoring your DMARC reports today

Suped DMARC platform dashboard
What you'll get with Suped
Real-time DMARC report monitoring and analysis
Automated alerts for authentication failures
Clear recommendations to improve email deliverability
Protection against phishing and domain spoofing