1-minute read of a 5 min report

Huntress kills a ClickFix Run chain before retrieved text executes

By

1-minute read

What a defender needs to know

A Windows user pasted the same ClickFix command into Run six times. Huntress says its Attack Disruption agent killed every attempt. In a detailed attempt, four processes were spawned and terminated within 1.25 seconds; the shell needed to execute text retrieved by finger.exe had already been terminated. The first accelerated SOC signal arrived roughly 70 seconds after the first kill. These timings are from Huntress’s case study of its own service, not a guarantee for other endpoints.

The lure hid a command behind the visible end of the Run field. It contacted finger[.]linkeders[.]net, an attacker-controlled host in this case, and used a shell loop to consume returned text. Preserve the pasted command and its process lineage for the first investigation step. Huntress says an earlier rule could kill a launcher while a detached child continued; a second rule now targets the live child using the parent’s command line. New variants may still evade the current ruleset.

For covered Windows endpoints, confirm Attack Disruption is in enforce mode, then inspect termination events and explorer.exe → cmd.exe lineage. Follow any detached child and finger.exe activity through to exit; compare the timeline with command-line and DNS or network telemetry for finger[.]linkeders[.]net. Audit mode signals without a kill. For another EDR, test local enforcement on a representative endpoint with the vendor and verify that no retrieval process leaves a surviving shell to execute returned text. Investigate any chain that outlived the kill even if a later SOC alert arrived.

Primary sources