<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Medusa on CuraSec</title><link>https://curasec.metacog.co.kr/tags/medusa/</link><description>Recent content in Medusa on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 11 Aug 2026 11:54:43 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/medusa/index.xml" rel="self" type="application/rss+xml"/><item><title>StormEncryptor ransomware deployed by ex-Medusa affiliate</title><link>https://curasec.metacog.co.kr/insights/2026-08-11-new-stormencryptor-ransomware-used-by-former-medusa-affiliat/</link><pubDate>Tue, 11 Aug 2026 11:54:43 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-11-new-stormencryptor-ransomware-used-by-former-medusa-affiliat/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> A new ransomware strain from a Medusa affiliate signals an active threat actor pivoting to new tooling, but the thin summary provides no specific vulnerability, attack vector, or affected software to patch or harden against today.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> Tracking a Medusa-lineage actor rebranding to StormEncryptor is useful triage context, but no IOCs, TTPs, or ATT&amp;amp;CK mappings are provided — file for actor awareness until a fuller technical report with detection surface emerges.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>