Skip to content
Threat Feed
high advisory

Threat Actors Abuse Microsoft ClickOnce for Stealthy Malware Delivery and Persistence

Threat actors are actively abusing Microsoft's ClickOnce deployment technology to deliver and persist malware by exploiting its user-friendly installation, lack of user awareness, and built-in update mechanism, enabling stealthy execution within legitimate Windows processes and bypassing traditional security controls to maintain remote access and facilitate further malicious activities.

Triage facts

Revision 2
Applicability
ClickOnce
Evidence
Unknown
Severity
High
Sources
1 public source
Freshness
Revision 2Jun 21, 07:02 UTC
Detection
2 rules
Revision history 1 entry · Revision 2
  1. Revision 2

    Repaired a legacy canonical identity collision

    Changed: slug

Threat actors are increasingly weaponizing Microsoft's ClickOnce technology to facilitate the stealthy delivery and persistence of malware on target systems. This technique leverages ClickOnce's features, such as simplified user interaction for installation (requiring only one or two clicks), the ability to deploy applications without elevated administrative privileges, and its built-in update mechanism. Attackers exploit a general lack of awareness among users and security tools regarding .application files, allowing malicious payloads to bypass typical email filtering and security scrutiny. The legitimate nature of ClickOnce execution, often involving processes like dfsvc.exe and rundll32.exe, provides a powerful defense evasion mechanism. This approach enables adversaries to establish persistent remote access, update their malware, and conduct further malicious activities without raising immediate suspicion.

Attack Chain

  1. Initial Access / User Execution: Threat actor convinces the target user to click a malicious link or button, often distributed via phishing, leading to the download of a .application file.
  2. Deployment: The user interaction triggers the ClickOnce deployment mechanism, installing the application without requiring administrator privileges.
  3. Payload Execution (Initial): The initial malicious payload executes as part of the ClickOnce application deployment, often within legitimate Microsoft process trees like dfsvc.exe or rundll32.exe.
  4. Persistence Establishment: A shortcut file (.appref-ms) is dropped into the user's Start Menu (%Users\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\) by the ClickOnce mechanism, configured to automatically check for updates.
  5. Malicious Update: The threat actor, controlling the deployment server, pushes a malicious update for the ClickOnce application.
  6. Update Execution / Code Download: The next time the user launches the application via the .appref-ms shortcut, the ClickOnce components fetch the malicious update from the server.
  7. Payload Execution (Updated): The newly downloaded malicious components are executed without further user prompts, enabling remote access, C2 communication, lateral movement, or other attacker objectives.
  8. Impact: The attacker maintains persistent access, updates their tooling, exfiltrates data, or deploys additional malware (e.g., ransomware) leveraging the established foothold.

Impact

The abuse of ClickOnce technology allows threat actors to establish a stealthy and persistent presence within victim environments. By executing within legitimate Microsoft processes, the malicious activity can evade traditional security controls that might scrutinize known malware executables. Organizations across various sectors are vulnerable, as this technique exploits a fundamental, legitimate Windows feature. Successful attacks can lead to sustained remote access, data exfiltration, deployment of ransomware, and lateral movement across the network, ultimately compromising the integrity and confidentiality of critical systems and data. The widespread nature of Windows environments makes this a significant threat vector.

Recommendation

  • Deploy the Sigma rules in this brief to your SIEM and tune for your environment, specifically prioritizing process_creation events involving dfsvc.exe and rundll32.exe.
  • Enable Sysmon process_creation and file_event logging to activate the rules above and gain visibility into ClickOnce application behavior.
  • Implement application control policies to restrict the execution of unsigned or untrusted ClickOnce applications, particularly those originating from untrusted internet sources.
  • Monitor network connections originating from dfsvc.exe or rundll32.exe to unexpected external IP addresses or non-standard ports.
  • Educate users about the risks of clicking on untrusted links or downloading software from unverified sources, even if it appears to be a legitimate application installer.

Detection coverage 2

Detect Suspicious Child Process of ClickOnce Deployment Service

high

Detects `dfsvc.exe`, the ClickOnce Deployment Services Client, spawning suspicious child processes like common scripting or shell interpreters, which can indicate malicious payload execution or C2 activity leveraging legitimate ClickOnce processes.

sigma tactics: defense_evasion, execution techniques: T1036.003, T1059 sources: process_creation, windows

Detect Suspicious Rundll32.exe Activity from ClickOnce Context

high

Detects `rundll32.exe`, when launched in a ClickOnce context (e.g., as a child of `dfsvc.exe`), executing suspicious commands or loading unusual DLLs, indicating potential malicious payload execution or defense evasion.

sigma tactics: defense_evasion, execution techniques: T1036.003, T1218 sources: process_creation, windows

Detection queries are available on the platform. Get full rules →