Security

CaptiveCrunch Malware Campaign Targets Travelers

3 min read

Summary

Microsoft has disclosed CaptiveCrunch, an active campaign linked to Midnight Blizzard that hijacks traffic on hospitality and captive portal networks to steal credentials and deliver malware. The threat is especially relevant for organizations with frequent travelers because attackers are abusing Entra ID device code flows, fake update prompts, and adversary-in-the-middle phishing to compromise corporate accounts and endpoints.

Need help with Security?Talk to an Expert

Introduction

Microsoft Threat Intelligence has warned of a new campaign called CaptiveCrunch that targets travelers using hotel, conference, and other captive portal-based Wi-Fi networks. For IT and security teams, this matters because the activity combines network traffic manipulation, Microsoft Entra ID phishing, and malware delivery to compromise both user accounts and devices.

What’s new

Microsoft attributes CaptiveCrunch to Storm-2945, a sub-cluster of Midnight Blizzard, the Russia-linked threat actor also known as SVR.

Key findings include:

  • Attackers are manipulating DNS and HTTP traffic on hospitality-related networks served by captive portals.
  • Victims are redirected to actor-controlled infrastructure for adversary-in-the-middle phishing.
  • The campaign abuses device code and OAuth authentication flows in Microsoft Entra ID to capture credentials and gain access to Microsoft 365 data.
  • Threat actors are also delivering malware disguised as browser or operating system updates.
  • Microsoft observed AI-assisted operations supporting parts of the campaign.
  • In addition to Windows payloads, there are signs attackers may also be attempting to target Android devices with malicious APK downloads.

Malware details

A key malware family in this campaign is CornFlake, a Windows RAT written in Go.

According to Microsoft, CornFlake can:

  • Enumerate systems
  • Steal files, credentials, and session tokens
  • Log keystrokes
  • Enable audio and video surveillance
  • Monitor removable media
  • Provide remote shell access

The malware uses fake update or installer screens to distract users while it installs persistence mechanisms, including services, scheduled tasks, and registry keys.

Impact on IT administrators

This is a high-priority risk for organizations with executives, consultants, sales teams, and other frequent travelers. Even if your tenant is well secured, users connecting through compromised captive portals may be exposed to phishing and malware before they realize anything is wrong.

The campaign also reinforces the need to monitor Entra device registration, OAuth abuse, suspicious sign-ins, and anomalous Microsoft 365 access patterns.

IT and security teams should:

  • Remind users to avoid installing updates or apps prompted by public Wi-Fi portals
  • Enforce phishing-resistant MFA where possible
  • Review controls around device code flow and OAuth consent
  • Monitor Entra ID sign-in logs for suspicious device registrations and token abuse
  • Use Microsoft Defender detections and hunting guidance from Microsoft’s advisory
  • Strengthen endpoint protection for traveling users, especially on unmanaged or high-risk networks

Organizations with a mobile workforce should treat CaptiveCrunch as an active travel-related threat and update user guidance and detection rules accordingly.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

SecurityMidnight BlizzardEntra IDphishingmalware

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.