<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Clickonce on CuraSec</title><link>https://curasec.metacog.co.kr/tags/clickonce/</link><description>Recent content in Clickonce on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 11 Jul 2026 11:49:48 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/clickonce/index.xml" rel="self" type="application/rss+xml"/><item><title>CrowdStrike: ClickOnce Deployment Abuse — Part 1 Inner Workings</title><link>https://curasec.metacog.co.kr/insights/2026-07-11-new-abuse-of-the-clickonce-technology-part-1-the-inner-worki/</link><pubDate>Sat, 11 Jul 2026 11:49:48 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-11-new-abuse-of-the-clickonce-technology-part-1-the-inner-worki/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Part 1 is foundational research on how ClickOnce deployment can be weaponized as an initial-access vector; no patch or config action today, but engineers supporting Windows app delivery should understand the attack surface before Part 2 drops with exploitation specifics.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> Builds triage context for ClickOnce-based delivery chains; hold detection engineering work until Part 2, which is expected to cover observable behaviors and threat-actor abuse patterns.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>