---
title: "Real-time phishing defeats codes when the session is the prize"
description: "Cisco Talos reports AI-assisted event lures used in real-time Google adversary-in-the-middle phishing. Defenders should prioritise phishing-resistant authentication and session controls over better-looking warning banners."
url: "https://devencelab.com/insights/2026/10/08/real-time-phishing-defeats-codes-when-the-session-is"
date: "2026-10-08"
section: "Insights"
tag: "AI Security"
author: "Devence Lab"
reading_time: "2 min read"
site: "Devence Lab"
license: "Readable and quotable with attribution to the canonical URL."
---

# Real-time phishing defeats codes when the session is the prize

Cisco Talos reports AI-assisted event lures used in real-time Google adversary-in-the-middle phishing. Defenders should prioritise phishing-resistant authentication and session controls over better-looking warning banners.

Cisco Talos has reported UAT-11985 using AI-assisted event-themed lures to deliver real-time Google adversary-in-the-middle phishing. The immediate news is real, but the deployment lesson is more demanding than the headline. A technology announcement or security warning only changes outcomes when teams can translate it into an owned control, an observable decision and a repeatable test.

The temptation is to treat AI-generated lures as a content-filtering problem. That interpretation misses the operational boundary. Procurement, adoption or awareness alone does not demonstrate that the resulting system is safe, effective or accountable under production conditions.

## The control that the headline leaves open

The attacker does not need to convince a filter that a message is benign forever. A convincing lure can route the victim through a relay that captures authentication flow material while the legitimate service appears to be involved. This is Devence Lab's operational assessment, not an additional finding attributed to the publisher.

The practical distinction matters because security and platform teams often inherit a capability after the buying or announcement decision. They then have to answer who owns its permissions, what an acceptable failure looks like, and how to reconstruct what happened when a control fails.

> A capability is operationally credible only when its authority, failure mode and evidence can be tested.

## Turn the announcement into an acceptance test

Require phishing-resistant authentication for sensitive roles, restrict token replay where the identity platform supports it and investigate suspicious session continuity. Correlate sign-ins, device context and application access instead of closing cases on a successful MFA event alone. These checks should be assigned to named owners and reviewed whenever integrations, identities or platform versions change.

A written policy is insufficient if the deployed configuration cannot produce evidence. Record the relevant configuration snapshot, the identity or service principal involved, and the event trail showing that the control worked. Where telemetry is absent, classify the gap explicitly rather than inferring protection from product documentation.

## What to do before the next rollout

Exercise a controlled phishing simulation that measures whether an intercepted login flow can complete, not merely whether a user clicks. Validate that conditional access, device binding and session revocation operate as expected. Capture both the expected result and the observed result, including exceptions. A failed exercise is useful evidence when it changes a rollout decision.

The review should include engineering, security and the business owner. Engineering can validate feasibility; security can assess privilege and detection; the business owner can determine which interruption or exposure is unacceptable. None of those judgements should be hidden inside a generic green status.

The underlying source establishes the announcement or reported threat. The control recommendations here are an independent interpretation for practitioners. Treat the source as a starting point for verification, then make adoption conditional on evidence from the actual environment.

Produced through Devence Lab's automated research and publishing workflow, without prepublication human review. Devence Lab retains editorial responsibility. Sources are linked; report factual errors to contact@devencelab.com.

## Sources

- [UAT-11985: AI-assisted event lures delivering real-time Google AitM phishing](https://blog.talosintelligence.com/uat-11985/) - Cisco Talos