ATT&CK coverage › Technique

Develop Capabilities: Malware T1587.001

Adversaries may develop malware and malware components that can be used during targeting. Building malicious software can include the development of payloads, droppers, post-compromise tools, backdoors (including backdoored images), packers, C2 protocols, and the creation of infected removable media. Adversaries may develop malware to support their operations, creating a means for maintaining control of remote machines, evading defenses, and executing post-compromise behaviors.

Events covered

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

ProviderEvent IDTitle
Sysmon1Process creation
Sysmon11FileCreate
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
CommandLine3match 3accepteula, -i -s pwsh, -s -i powershell, \\\\127., -p
Image3ends_with 3, match 1\csexec.exe, \excel.exe, :\Program Files\Common Files\Microsoft Shared\ClickToRun\, :\Program Files\Microsoft Office\, \MicrosoftEdge.exe
TargetFilename2match 2, ends_with 1.xlt, .xlw, \Program Files, .vhd
Description1eq 1csexec

Top indicator values (62 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
CommandLinematchaccepteula33
CommandLinematch -i -s cmd22
CommandLinematch -s cmd22
CommandLinematch -s -i cmd22
CommandLinematch -i -s powershell22
CommandLinematch -s -i pwsh22
CommandLinematch -s powershell22
CommandLinematch -s pwsh22
CommandLinematchpaexec22
CommandLinematch -i -s pwsh22
CommandLinematch -s -i powershell22
CommandLinematchPsExec1
CommandLinematch\\\\localhost1
CommandLinematch \\\\18
CommandLinematch -u 14
CommandLinematch\\\\127.1
CommandLinematch -p 15
CommandLinematchpsexec1
Descriptioneqcsexec1
Imageends_with\csexec.exe1

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