In practice2 min read

Fake AI events solicit work sign-ins: review device-code requests

Push Security reported an AI-event phishing campaign. Small businesses should verify invitations separately and ask an administrator to audit device code flow.

Prepared by the NADALI editorial team using AI

AI illustration: an envelope with a gift symbol, a red warning barrier and a key representing a work account.
Nadali editorial illustration created with OpenAI gpt-image-2-2026-04-21 · Original AI-generated editorial illustration created for Nadali; use subject to applicable OpenAI terms; no exclusive copyright claim; no third-party input images used. · 1440 × 960

Author: Nadali. Prepared using AI.

On November 5, 2026, Push Security reported fake AI events offering rewards for work sign-ins, based on late-October observations. Researchers said approving a code on Microsoft’s real page delivered tokens to the attacker; the Google route used a sign-in proxy.

This is a security vendor’s report, not an independent Nadali test or evidence that every multifactor authentication method is equally vulnerable.

Who it helps and what to do

Small-business owners and marketing managers whose teams register for training and presentations with work accounts. The takeaway: check not only the sign-in address, but also who receives access and why.

Our recommended review:

  1. Verify the event on the organizer’s official website, opened separately from the invitation. A promised reward is not a reason to authorize work-account access.
  2. If an unfamiliar registration asks you to copy a device code and approve a sign-in, stop and refer the request to your IT contact.
  3. Ask an administrator whether the business needs device code flow. Microsoft recommends auditing usage first and blocking it through Conditional Access when unnecessary. Its guide calls for Report-only mode before enforcement and emergency-access exclusions to prevent administrator lockout.
  4. If someone already approved a suspicious request, immediately give IT the event time and invitation address so access can be investigated. This is response advice, not a claim of a confirmed breach.

Availability and limits

The Conditional Access setting applies to Microsoft Entra, not Google; an administrator must check tenant availability and licensing. Do not change company-wide policies blindly. We have not tested the attack, a tenant or a security product, and do not claim the reported pages remain active.

Sources read on November 8, 2026. Microsoft’s guidance describes an existing defensive measure, not a new release. The cover is a conceptual AI illustration, not a real interface or incident photograph. 

Sources and verification

  1. Push Security — Analyzing a fake event campaign combining AiTM and device code phishing payloads (November 5, 2026) ↗
    Source checked: 2026-11-08
  2. Microsoft Learn — Block authentication flows with Conditional Access policy ↗
    Source checked: 2026-11-08