ATT&CK coverage › Technique

User Execution: Malicious Copy and Paste T1204.004

An adversary may rely upon a user copying and pasting code in order to gain execution. Users may be subjected to social engineering to get them to copy and paste code directly into a Command and Scripting Interpreter. One such strategy is "ClickFix," in which adversaries present users with seemingly helpful solutions—such as prompts to fix errors or complete CAPTCHAs—that instead instruct the user to copy and paste malicious code.

Events covered

3 catalog events are tagged with this technique by at least one rule.

ProviderEvent IDTitle
Sysmon1Process creation
Sysmon13RegistryEvent (Value Set)
Security-Auditing4688A new process has been created.

Authoring guide

Patterns shared across the 6 rules above: which fields they filter on, what specific values they look for, and what they exclude. Field names are normalized across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.

Fields filtered most (4 distinct)

The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.

FieldRulesHowSample values
Details3match 3            ,             ,             , account, validation
TargetObject3ends_with 2, match 1\Software\Microsoft\Windows\CurrentVersion\Explorer\Typed..., \Software\Microsoft\Windows\CurrentVersion\Explorer\RunMRU\
CommandLine3match 3fraud, anti-bot, botcheck,             ,             
ParentImage3ends_with 3\explorer.exe, \chrome.exe, \msedge.exe, \firefox.exe

Top indicator values (96 distinct)

Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique.

FieldKindValueRules (here)Corpus reach
Detailsmatch#33
CommandLinematch#33
TargetObjectends_with\Software\Microsoft\Windows\CurrentVersion\Explorer\TypedPaths\url122
CommandLinematchverify22
CommandLinematchbotcheck22
CommandLinematchvalidation22
CommandLinematchconfirmation22
CommandLinematchidentification22
CommandLinematchchallenge22
CommandLinematchidentificator22
CommandLinematchverification22
ParentImageends_with\explorer.exe211
CommandLinematchrobot22
CommandLinematchanti-bot22
CommandLinematchidentity22
CommandLinematchaccount22
CommandLinematchhuman22
CommandLinematchfraud22
CommandLinematchcaptcha22
Detailsmatch            22

Rules under this technique

Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.

Sigma 6 rules