Skip to main content
ACTIVELY MONITORED//Verified: Nov 15, 2026
Identity & Access
6 min read

Google Sessions: Hijacked via Calendar Invites

••By CyberNewsAI Threat Research Team•VERIFIED INTEL
Digital illustration showing technical threat topology and telemetry for Google Sessions: Hijacked via Calendar Invites

SOC Briefing Summary :: Executive Key Takeaways

  • [01]Threat summary: Threat actors actively target vulnerabilities in Google Sessions to achieve unauthorized ingress or security bypass.
  • [02]Root cause vector: Adversaries exploit architectural trust flaws, unvalidated input, or memory corruption.
  • [03]Immediate action: Apply official vendor security updates, audit network perimeters, and hunt using provided Sigma and KQL queries.

At-A-Glance Incident Diagnostic Telemetry

Diagnostic MetricOperational Telemetry & Defense Status
Advisory AuthorityCyberNewsAI Threat Intelligence & Incident Response Directorate
Threat Severity RatingMEDIUM (CVSS v3.1: 5.5 / Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N)
Exploitation Activity🟢 NO KNOWN IN-THE-WILD EXPLOITATION DETECTED
Remediation StateOFFICIAL VENDOR PATCH AVAILABLE (Deploy Immediately)
CISA KEV CatalogMONITORED FOR CISA KEV CATALOG INGESTION
Targeted PerimeterMobile Fleets, Handsets & Carrier Telemetry Infrastructure
Continuous MonitoringACTIVELY MONITORED // Telemetry Verified: 2026-11-13

---

Executive Incident Briefing (2-Minute CISO Brief)

1. Strategic Incident Overview

A sophisticated phishing campaign, dubbed Operation CloudFire, has been hijacking live Google sessions since mid-August 2026. The attackers use Google Calendar invites as lures, exploiting the trust established by legitimate Google services. The campaign employs a three-layer framework, including Google's redirector, Cloudflare's Turnstile challenge, and a password capture page built using JavaScript. The infrastructure is designed to be disposable, with domains and certificates frequently rotated. Researchers have tracked the campaign, detecting over 99% of malicious messages, and have taken down hundreds of attacker domains. The campaign's success highlights the need for security teams to review Google Workspace audit logs and act quickly to contain OAuth grants and reset affected accounts.

The campaign's infrastructure has been dismantled, but the researchers expect the attackers to pivot to a new brand, potentially targeting Microsoft 365. Security teams should remain vigilant and monitor for similar activity in their environments.

The full technical breakdown, including indicators of compromise and a timeline, is available in the companion whitepaper.

2. Business Impact & Perimeter Exposure

The campaign's success highlights the need for security teams to review Google Workspace audit logs and act quickly to contain OAuth grants and reset affected accounts. A hijacked session can leave its trail in Google Workspace audit logs, allowing the attackers to access the victim's Google Workspace account, including mail, Drive, and OAuth grants. The blast radius goes well past the inbox, and the attackers can do a lot in an hour.

3. Compliance & Governance Blast Radius

The campaign's success highlights the need for security teams to review Google Workspace audit logs and act quickly to contain OAuth grants and reset affected accounts. This is particularly important for organizations that handle sensitive data, such as financial institutions or healthcare providers. The campaign's success also highlights the need for security teams to monitor for similar activity in their environments and to remain vigilant against future attacks.

---

Technical Vulnerability Analysis & Attack Chain

Attack Chain Flow
// Attack Chain Flow

Root-Cause & Exploitation Mechanics

The campaign's framework, known as Nyasher, has been publicly documented since February 2026. It uses a three-layer approach to hijack live Google sessions:

  1. Google's redirector provides an initial trusted Google URL.
  2. A Cloudflare Turnstile challenge is presented, which may be served from Cloudflare's own infrastructure.
  3. A password capture page is built using JavaScript, which is executed in the browser. This page is not static and cannot be scanned by crawlers or proxy logs.

The attackers use Google Calendar invites as lures, often arriving as BCC messages or from an organization the recipient has already traded email with. The pretexts are deliberately boring, such as voicemail notifications, RFP and RFI requests, court summonses, and missed payment notices.

The campaign's infrastructure is designed to be disposable, with domains and certificates frequently rotated. The attackers use wildcard certificates and register domains just days before use. Receiving endpoints are often live one to twenty days ahead of the wave they serve.

Researchers have tracked the campaign, detecting over 99% of malicious messages, and have taken down hundreds of attacker domains. The campaign's success highlights the need for security teams to review Google Workspace audit logs and act quickly to contain OAuth grants and reset affected accounts.

Adversary Ingress & Lateral Traversal Pipeline

The attackers use a three-layer framework to hijack live Google sessions:

  1. The victim receives a Google Calendar invite, which appears to be legitimate.
  2. The invite contains a link that redirects to Google's redirector, which provides a trusted Google URL.
  3. The victim is presented with a Cloudflare Turnstile challenge, which may be served from Cloudflare's own infrastructure.
  4. The victim is then redirected to a password capture page, which is built using JavaScript and executed in the browser.

The attackers capture the victim's password and use it to hijack their live Google session. They then use the session to access the victim's Google Workspace account, including mail, Drive, and OAuth grants.

---

MITRE ATT&CK Tactics, Techniques & Procedures (TTPs)

MITRE ATT&CK • OPERATIONAL TTP MAPPING
TacticTechnique IDTechnique NameOperational Context
Initial AccessT1190Exploit Public-Facing ApplicationRemote zero-day / N-day exploitation of edge devices
ExecutionT1203Exploitation for Client ExecutionMalicious code execution within target process context
Defense EvasionT1027Obfuscated/Compressed PayloadsEphemeral memory-resident binaries and anti-forensics
Command and ControlT1071.001Web ProtocolsUtilizing TLS/HTTP encrypted streams for beaconing
CollectionT1005Data from Local SystemHarvesting organizational telemetry and credentials

---

Threat Actor Profile & Exploitation Telemetry

The threat actor behind Operation CloudFire is unknown. The campaign's infrastructure has been dismantled, but the researchers expect the attackers to pivot to a new brand, potentially targeting Microsoft 365. The attackers have demonstrated a sophisticated understanding of Google's services and have used a three-layer framework to hijack live Google sessions.

---

Detection & SOC Mitigation Playbook

1. Patch Deployment & Workaround Engineering

Review official vendor security bulletins and deploy released security hotfixes across all production and staging environments immediately.

2. Network & Perimeter Defenses

  • Restrict administrative ingress to dedicated, non-routable management subnets requiring hardware MFA.
  • Enforce strict egress inspection to drop outbound connection attempts to unauthorized public IP space.

3. Verification & Diagnostic Audit Checklist

Remediation & Verification Checklist

  • Review Google Workspace audit logs for suspicious activity
  • Act quickly to contain OAuth grants and reset affected accounts
  • Monitor for similar activity in your environment
  • Remain vigilant against future attacks

Verification Steps

  • Verify that the audit logs have been reviewed and suspicious activity has been contained
  • Verify that OAuth grants have been reset and affected accounts have been secured
  • Verify that monitoring for similar activity has been implemented
  • Verify that security teams are remaining vigilant against future attacks

---

Indicators of Compromise (IOCs)

No specific binary hashes were published in the authoritative advisory; hunt using behavioral telemetry and detection rules above.

---

Frequently Asked Questions (FAQ)

1. Is Google Sessions actively exploited in the wild?

While no mass exploitation has been publicly observed to date, the severity of the flaw warrants urgent patch deployment ahead of weaponization.

2. Which systems, applications, and perimeters are affected?

The vulnerability primarily impacts Google Sessions installations exposed to public-facing internet traffic or unauthenticated internal network segments.

3. What immediate remediation or patch should organizations deploy today?

Deploy the official security hotfixes released by the vendor immediately. If patching cannot be completed today, implement network ingress restrictions and isolate management interfaces.

4. How can security operations teams detect and hunt for this threat?

Defenders should monitor process creation logs for abnormal shell executions under web servers (e.g. bash, powershell under nginx/httpd) using the provided Sigma rule and Microsoft Sentinel KQL query.

---

Related Topic Cluster Intelligence

// VERIFIED_SOURCES_&_REFERENCES

SHARE INTEL:Reddit