Skip to content
skopnix
Detections · Rule
← Sigma detectionsSigma · Indicator

Execution of known malicious file 925aff03ab009c8e…

SIGmediumconfidence 72/100generated 2026-10-18

Process image hash tracked by skopnix as ta402.

ATT&CK
T1204.002 mitre ↗
Linked actors
TA402
False positives
Scoped to one indicator with skopnix confidence 72/100 from 2 independent sources; checked against RFC1918/reserved space, CDN / cloud / scanner ranges and top-site lists (MISP warninglists), GreyNoise when enriched, and skopnix's benign-infrastructure list. Re-validate against last_seen before blocking: infrastructure is re-assigned.

Sigma rule

skopnix-sigma-ioc-sha256-925aff03ab009c8e7935cfa389fc7a34482184cc310-25cc6230.ymldownload .yml ↓
title: Skopnix - Execution of known malicious file 925aff03ab009c8e…
id: 6fa53eae-ca59-58a7-8d44-114a6402e9a3
status: experimental
description: Process image hash tracked by skopnix as ta402.
references:
  - https://skopnix.com/ioc/925aff03ab009c8e7935cfa389fc7a34482184cc310a8d8f88a25d9a89711e86
author: skopnix
date: '2026-10-18'
tags:
  - attack.execution
  - attack.t1204.002
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    Hashes|contains: SHA256=925AFF03AB009C8E7935CFA389FC7A34482184CC310A8D8F88A25D9A89711E86
  condition: selection
falsepositives:
  - Legitimate services sharing the address; verify against skopnix confidence + last_seen
level: medium

How to deploy on Sigma

  1. 1.Convert for your SIEM with sigma-cli / pySigma, e.g. sigma convert -t splunk -p sysmon rule.yml.
  2. 2.Run it as a hunt first: every rule ships as status experimental.
  3. 3.Promote to an alert once a week of results is clean on your data.

Check · The processing pipeline must map the logsource (firewall, dns, proxy, webserver, process_creation) to your field names.

References