1200kmSECURITY RESEARCH

1200KM / sigma-rule

PUA - Sysinternal Tool Execution - Registry — Sigma Rule

Sigma rule 25ffa65d-76d8-4da5-a832-3f2b0136e133. PUA - Sysinternal Tool Execution - Registry — Sigma Rule. Detects the execution of a Sysinternals Tool via the creation of the "accepteula" registry key

Rule metadata and linked tags

Author: Markus Neis. Source status: test; severity: low. Source dates: 2017-08-28 / 2025-10-26.

{
  "product": "windows",
  "category": "registry_set"
}

Pinned original Sigma rule · Detection Rule License 1.1

Source SHA-256: ad933a28b409c87df9f947f9af6e7c928c3d648ccf689843271144011a735a1f

Detection logic

Original source YAML. Source-tag agreement is not proof of complete semantic coverage. This rule has not been compiled for a SIEM backend or validated against live telemetry here.

title: PUA - Sysinternal Tool Execution - Registry
id: 25ffa65d-76d8-4da5-a832-3f2b0136e133
status: test
description: Detects the execution of a Sysinternals Tool via the creation of the "accepteula" registry key
references:
    - https://twitter.com/Moti_B/status/1008587936735035392
author: Markus Neis
date: 2017-08-28
modified: 2025-10-26
tags:
    - attack.resource-development
    - attack.t1588.002
logsource:
    product: windows
    category: registry_set
detection:
    selection:
        TargetObject|endswith: '\EulaAccepted'
    condition: selection
falsepositives:
    - Legitimate use of SysInternals tools
    - Programs that use the same Registry Key
level: low
regression_tests_path: regression_data/rules/windows/registry/registry_set/registry_set_pua_sysinternals_execution_via_eula/info.yml

Original YAML and metadata in JSON

False positives

  • Legitimate use of SysInternals tools
  • Programs that use the same Registry Key

Source references

Connected ecosystem references

Exact source-tagged techniques

Telemetry review

Read the original logsource above, then inspect the linked detection workspaces for technique-level sensor context. No per-rule telemetry equivalence is inferred.

Pinned research references. No browser attack runner, live simulation result or validated detector is asserted. Source mappings and validation limits are preserved. ATT&CK / Atomic provenance · Detection provenance.