<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>C2-Abuse on CuraSec</title><link>https://curasec.metacog.co.kr/tags/c2-abuse/</link><description>Recent content in C2-Abuse on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 21 Jul 2026 12:43:35 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/c2-abuse/index.xml" rel="self" type="application/rss+xml"/><item><title>HollowGraph Malware Uses M365 Calendar Events Dated 2050 as C2 Channel</title><link>https://curasec.metacog.co.kr/insights/2026-07-21-hollowgraph-malware-hides-c2-and-stolen-files-in-microsoft-3/</link><pubDate>Tue, 21 Jul 2026 12:43:35 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-21-hollowgraph-malware-hides-c2-and-stolen-files-in-microsoft-3/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> Novel Graph API abuse using calendar write access highlights over-permissioned OAuth app risk. Audit which apps hold Microsoft Graph calendar read/write scopes and revoke unnecessary permissions this quarter.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Act:&lt;/strong> The year-2050 calendar event timestamp is a highly specific, huntable indicator — sweep M365 audit logs for calendar events created with 2050 dates and flag Graph API calls that write calendar entries with large attachments.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Espionage actors using legitimate Microsoft 365 infrastructure for C2 blurs the line between sanctioned SaaS activity and intrusion; useful context for understanding the M365-as-attack-surface risk but no immediate leadership action required.&lt;/li>
&lt;/ul></description></item></channel></rss>