<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ttp-Analysis on CuraSec</title><link>https://curasec.metacog.co.kr/tags/ttp-analysis/</link><description>Recent content in Ttp-Analysis on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 25 Sep 2026 15:49:12 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/ttp-analysis/index.xml" rel="self" type="application/rss+xml"/><item><title>Storm-2570 ransomware affiliate: consistent tradecraft across Qilin, DragonForce, Anubis, BERT</title><link>https://curasec.metacog.co.kr/insights/2026-09-25-beyond-the-ransomware-tracking-storm-2570-s-consistent-trade/</link><pubDate>Fri, 25 Sep 2026 15:49:12 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-25-beyond-the-ransomware-tracking-storm-2570-s-consistent-trade/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> No exploitable vulnerability or patchable component here — this is post-compromise TTP analysis. Worth reviewing to understand how Storm-2570 stages before detonation, which could inform detection-oriented hardening of endpoint configs or logging.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Act:&lt;/strong> Microsoft documents Storm-2570&amp;rsquo;s reusable pre-ransomware toolchain across four active ransomware families with defender detection guidance — review the full blog post, map identified TTPs to ATT&amp;amp;CK, and tune or create SIEM/EDR rules against the common tradecraft patterns before the next deployment hits.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> A single-source threat-actor profile with no confirmed incident or sector-specific targeting disclosed; useful background for briefing on ransomware affiliate sophistication and the multi-group risk model, but no same-week action needed.&lt;/li>
&lt;/ul></description></item></channel></rss>