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

Execution of known malicious file 69b3d913a3967153…

SIGmediumconfidence 72/100generated 2026-10-18

Process image hash tracked by skopnix as rhysida.

ATT&CK
T1204.002 mitre ↗
Linked actors
rhysida
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-sha1-69b3d913a3967153d1e91ba1a31ebed839b297ed-4fc282e2.ymldownload .yml ↓
title: Skopnix - Execution of known malicious file 69b3d913a3967153…
id: da091dfa-16d0-5a8d-b315-0f90850a495c
status: experimental
description: Process image hash tracked by skopnix as rhysida.
references:
  - https://skopnix.com/ioc/69b3d913a3967153d1e91ba1a31ebed839b297ed
author: skopnix
date: '2026-10-18'
tags:
  - attack.execution
  - attack.t1204.002
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    Hashes|contains: SHA1=69B3D913A3967153D1E91BA1A31EBED839B297ED
  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