HOLLOWGRAPH: The Windows Malware That Turned Microsoft 365 Calendars Into a Secret Spy Network + Video

Listen to this Post

Featured ImageIntroduction: When Everyday Cloud Tools Become Cyber Weapons

For years, cybersecurity experts have warned that attackers are moving away from traditional malware techniques and increasingly abusing trusted platforms that organizations already rely on every day. Instead of creating suspicious servers, unusual network connections, or obvious malicious infrastructure, modern threat actors are learning how to disappear inside legitimate ecosystems.

A newly discovered Windows malware strain called HOLLOWGRAPH represents exactly this evolution. According to research from Group-IB, attackers have transformed Microsoft 365 calendar functionality into a hidden command-and-control (C2) system, allowing them to send instructions to infected machines and steal sensitive files without relying on traditional attacker-controlled servers.

The discovery highlights a growing cybersecurity challenge: the same cloud services designed to improve productivity are becoming attractive hiding places for espionage campaigns. Microsoft 365 calendars, Graph API communications, OAuth credentials, and DNS infrastructure have all been combined into a sophisticated malware ecosystem designed to blend into normal enterprise activity.

HOLLOWGRAPH Malware: A New Generation of Cloud-Based Espionage

Group-IB’s Threat Intelligence team recently uncovered HOLLOWGRAPH, a previously undocumented Windows malware implant that abuses Microsoft 365 services as a covert communication channel.

Unlike conventional malware that communicates with external command servers, HOLLOWGRAPH uses the Microsoft Graph API through a compromised Microsoft 365 account. This allows attackers to operate through legitimate Microsoft infrastructure, making detection significantly more difficult.

The malware has been linked with high confidence to the Cavern backdoor framework, a modular malware platform previously associated with Iranian-linked cyber operations. While researchers have not confirmed the exact threat actor behind the campaign, technical similarities suggest possible connections to groups operating in the Middle East region.

The attack demonstrates a major shift in cyber warfare: attackers no longer need to build suspicious infrastructure when they can simply abuse trusted business platforms.

Microsoft 365 Calendar Becomes a Hidden Command Channel

The most unusual feature of HOLLOWGRAPH is its abuse of Microsoft 365 calendar events as a two-way communication mechanism.

Instead of contacting an external server, the malware communicates through calendar entries inside a compromised mailbox.

The process works like a digital dead drop:

Attackers create calendar events containing hidden commands.

The infected system checks those events through Microsoft Graph API.

The malware executes the requested action.

Stolen files are uploaded back through new calendar events.

The calendar becomes a secret mailbox between attackers and malware operators.

This technique allows attackers to hide inside normal enterprise cloud traffic because Microsoft Graph API activity appears similar to legitimate business applications interacting with Microsoft 365.

Future-Dated Calendar Events Hide Malicious Activity

One of the cleverest elements of HOLLOWGRAPH is how it hides suspicious calendar activity.

Researchers discovered that malware-created events are scheduled far into the future, specifically:

13 May 2050

By placing events decades ahead, attackers avoid attracting attention from users reviewing current schedules.

The malware does not place stolen information directly into calendar descriptions. Instead, it hides encrypted files inside attachments.

The malware uses specific naming patterns:

File{n}.txt for stolen data chunks

Task IDs inside calendar subjects

Operator-controlled identifiers for tracking stolen information

This approach turns an ordinary productivity feature into a covert storage and communication platform.

Two Simple Commands With Dangerous Capabilities

Despite its advanced communication techniques, HOLLOWGRAPH itself is lightweight.

The malware primarily understands two commands:

get

The “get” command allows attackers to retrieve instructions from calendar events.

The malware searches for specific task identifiers in event subjects and extracts commands from attached data.

send

The “send” command allows infected systems to upload stolen information back to attackers.

Files are encrypted, divided into smaller pieces, and uploaded through calendar attachments.

The simplicity of the command structure suggests that HOLLOWGRAPH was designed as a specialized espionage tool rather than a widespread criminal malware family.

DNS Tunneling Keeps Attackers Connected

Although Microsoft 365 handles the main communication channel, HOLLOWGRAPH uses another hidden technique to maintain access.

The malware uses DNS tunneling to refresh authentication information required to access Microsoft Graph API.

Researchers discovered that the malware communicates with:

cloudlanecdn[.]com

through specially crafted IPv6 AAAA DNS queries.

These queries contain hidden information, including:

Microsoft Entra ID tenant information

Client identifiers

Client secrets

Mailbox details

The malware reconstructs this information and stores it locally inside a fake-looking configuration file:

logAzure.txt

The file name was designed to appear harmless, blending with normal system logging activity.

Deep Analysis: How HOLLOWGRAPH Operates

Attack Flow Overview

Victim Windows System

|
|
v

HOLLOWGRAPH Malware Implant

|
|

+-+

| |

v v

Microsoft Graph API DNS Tunnel

| |

| |

v v

Microsoft 365 Calendar cloudlanecdn[.]com

|
|
v

Encrypted Commands / Data Theft

Hunting for HOLLOWGRAPH Indicators

Security teams should search for unusual Microsoft 365 behavior.

Example Microsoft Graph activity investigation:

AuditLogs

| where Operation contains Create event

| where Application != Microsoft Outlook

| project TimeGenerated, UserId, Application, Operation

The goal is to identify applications creating calendar events unexpectedly.

Searching for Suspicious Calendar Dates

Security teams should investigate calendar events created with unusual future timestamps.

Example query logic:

EventDate == "2050-05-13"

Events with:

GUID-based subjects

Event ID:

Boss{ID}

File{number}.txt

should receive additional investigation.

Monitoring DNS Tunnel Activity

Organizations should monitor suspicious DNS behavior.

Example indicators:

AAAA DNS Requests

High-frequency queries

Long random subdomains

Unusual external domains

Security teams can use DNS analytics platforms to detect possible tunneling attempts.

Microsoft Entra Security Checks

Organizations should audit OAuth applications and client credentials.

Recommended checks:

Review Application Registrations

Monitor Client Secret Creation

Detect Abnormal Token Usage

Review Conditional Access Policies

Attackers increasingly target identity systems because stolen credentials provide long-term access.

Connection to Cavern Framework and Possible Lyceum Links

Group-IB researchers identified several similarities between HOLLOWGRAPH and the Cavern backdoor framework.

Shared characteristics include:

Similar command structures

Matching task formats

Plugin-based malware architecture

Debug logging control commands

Researchers also noted possible similarities with malware previously associated with Lyceum, a group connected by analysts to the broader OilRig threat ecosystem.

However, this connection remains low confidence.

The evidence suggests technical overlap, but attribution cannot yet be confirmed.

Cybersecurity researchers often avoid making direct accusations because malware tools can be shared, modified, or copied between different groups.

A Small Number of Victims Suggests Targeted Espionage

Unlike typical malware campaigns that infect thousands or millions of machines, HOLLOWGRAPH appears highly selective.

Group-IB identified:

At least 12 infected systems

Around 3 systems actively communicating with attackers

The earliest observed communication occurred on:

3 June 2026

The latest activity observed was:

9 July 2026

The limited victim count indicates that this operation was likely designed for intelligence gathering rather than financial crime.

The compromised Microsoft 365 mailbox belonged to an Israeli organization, and malware samples were also submitted from Israel.

This points toward a carefully planned regional espionage campaign.

Why HOLLOWGRAPH Represents a Dangerous Trend

The biggest lesson from HOLLOWGRAPH is not simply the malware itself.

The bigger issue is the abuse of trusted cloud ecosystems.

Traditional security models often focus on blocking:

Unknown domains

Suspicious servers

Malicious IP addresses

Unusual network traffic

But cloud-based malware challenges this approach.

An attacker using Microsoft Graph API does not necessarily look suspicious.

They are using:

Valid Microsoft infrastructure

Real authentication systems

Normal business protocols

The attack hides in the same environment employees use every day.

Defensive Recommendations for Organizations

Security teams should immediately review Microsoft 365 environments for abnormal behavior.

Recommended actions include:

Search for HOLLOWGRAPH indicators.

Investigate cloudlanecdn[.]com activity.

Check for logAzure.txt creation.

Review Microsoft Graph API usage.

Monitor automated calendar modifications.

Detect suspicious OAuth applications.

Rotate exposed credentials.

Enable Conditional Access policies.

Monitor DNS tunneling behavior.

Analyze abnormal application authentication patterns.

Organizations should assume that identity systems and cloud platforms are now primary cyberattack targets.

What Undercode Say:

HOLLOWGRAPH represents a new chapter in the evolution of cyber espionage.

The malware itself is not revolutionary because of complex code or advanced exploitation techniques.

Its power comes from deception.

Attackers understood that Microsoft 365 is trusted by millions of organizations. Instead of fighting against enterprise security systems, they decided to hide inside them.

The calendar attack method is especially concerning because many companies rarely monitor calendar activity from an application-security perspective.

Most security teams analyze:

Emails

Login attempts

Endpoint behavior

Network connections

But calendars are usually considered harmless productivity data.

That assumption is becoming dangerous.

Modern attackers are expanding their battlefield into every digital service organizations depend on.

Cloud platforms have created enormous business advantages, but they have also created new hiding places for attackers.

The HOLLOWGRAPH campaign demonstrates several important cybersecurity trends:

Malware developers are prioritizing stealth over destruction.

Cloud abuse is replacing traditional command servers.

Identity systems are becoming more valuable than individual computers.

OAuth credentials are becoming a major attack target.

Legitimate APIs are increasingly weaponized.

Security monitoring must expand beyond endpoints.

SaaS applications require the same protection level as servers.

Attackers are designing malware specifically for enterprise environments.

Small targeted campaigns can represent greater national security risks than mass malware outbreaks.

Future cyber conflicts will increasingly involve cloud infrastructure.

The HOLLOWGRAPH operation also shows why organizations need behavioral detection instead of simple signature-based security.

A malicious file can be blocked.

A suspicious domain can be removed.

But a legitimate Microsoft account performing unusual actions is much harder to detect.

The future of cybersecurity will depend on understanding context.

A calendar event created by an employee is normal.

A calendar event created automatically by an unknown application, scheduled for 2050, containing encrypted attachments, is not.

Security teams must learn to identify these differences.

✅ Confirmed: HOLLOWGRAPH malware was identified by Group-IB as a Windows implant abusing Microsoft 365 services.
The research describes calendar-based command-and-control communication through Microsoft Graph API.

✅ Confirmed: The malware uses DNS tunneling for credential refresh operations.
Researchers documented DNS-based communication used to retrieve authentication-related information.

❌ Not confirmed: The exact threat actor behind HOLLOWGRAPH remains unknown.
Although links to Cavern, Lyceum, and Iranian-related activity were discussed, attribution is not definitive.

Prediction

(+1) Cloud-based malware operations will continue growing as attackers increasingly abuse trusted platforms.
Future malware campaigns will likely target Microsoft 365, Google Workspace, Slack, and other enterprise collaboration systems because they provide built-in trust.

(+1) Security tools will evolve toward AI-powered behavioral monitoring.
Organizations will increasingly rely on artificial intelligence to detect unusual cloud activity rather than searching only for known malware signatures.

(-1) Traditional security strategies focused only on endpoint protection will become less effective.
Attackers hiding inside legitimate services can bypass many conventional defenses.

(-1) Identity compromise will remain one of the biggest enterprise security threats.
As cloud environments expand, stolen tokens, OAuth credentials, and application permissions will become valuable targets.

(+1) Organizations that improve cloud auditing and access controls will significantly reduce risk.
Proper monitoring of Graph API activity, application permissions, and authentication patterns can expose attacks before major damage occurs.

▶️ Related Video (80% Match):

🕵️‍📝Let’s dive deep and fact‑check.

🎓 Live Courses & Certifications:

Join Undercode Academy for Verified Certifications

🚀 Request a Custom Project:

Secure, high-velocity infrastructure and disruptive technological engineering. Contact our engineering team for high-tier development and proprietary systems:
[email protected]
💎 Smart Architecture | 🛡️ Secure by Design | ⭐ Trusted by Thousands

References:

Reported By: www.itsecurityguru.org
Extra Source Hub (Possible Sources for article):
https://www.facebook.com
Wikipedia
OpenAi & Undercode AI

Image Source:

Unsplash
Undercode AI DI v2

🔐JOIN OUR CYBER WORLD [ CVE News • HackMonitor • UndercodeNews ]

💬 Whatsapp | 💬 Telegram

📢 Follow UndercodeNews & Stay Tuned:

𝕏 formerly Twitter 🐦 | @ Threads | 🔗 Linkedin | 🦋BlueSky | 🐘Mastodon | 📺Youtube