<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Payload on CuraSec</title><link>https://curasec.metacog.co.kr/tags/payload/</link><description>Recent content in Payload on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 10 Sep 2026 14:58:06 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/payload/index.xml" rel="self" type="application/rss+xml"/><item><title>Redtail Malware Payload Analysis — SANS ISC Guest Diary</title><link>https://curasec.metacog.co.kr/insights/2026-09-10-redtail-payload-analysis-x5b-guest-diary-x5d-wed-sep-9th/</link><pubDate>Thu, 10 Sep 2026 14:58:06 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-10-redtail-payload-analysis-x5b-guest-diary-x5d-wed-sep-9th/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> A hands-on payload breakdown may surface indicators or techniques relevant to endpoint/workload defenses, but no enrichment signals (KEV/EPSS/PoC) and a very thin summary mean no immediate action is warranted.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> If the full diary contains IOCs or ATT&amp;amp;CK-mappable TTPs for Redtail, it could inform detection tuning, but the summary exposes no actionable content — read the full entry before queuing any hunt work.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>