Researchers detailed how Windows ClickOnce applications can be abused through the normal deployment chain that begins when a user opens a .application file. In the documented flow, rundll32.exe invokes dfshim.dll through the ShOpenVerbApplication API, which identifies the deployment resources and redirects execution to the appropriate ClickOnce components inside the .NET Framework.
The analysis shows dfshim.dll locating and loading dfdll.dll with GetRequestedRuntimeInfo, then dynamically resolving dfdll!ActivateDeploymentW() to continue execution. That function validates parameters and initializes a COM server through InvokeServer(), using CoInitialize and CoCreateInstance with CLSID {20FD4E26-8E0F-4F73-A0E0-F27B8C57BE6F}; if COM server creation fails, the chain falls back to launching dfsvc.exe with CreateProcessW() to complete the ClickOnce deployment, highlighting multiple legitimate Windows components that could be leveraged to mask malicious activity.

Pull IOCs and campaign context straight into your stack.
1 reference tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.