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

Execution of known malicious file c38c21120d8c1768…

SIGmediumconfidence 77/100generated 2026-10-18

Process image hash tracked by skopnix as Kinsing.

ATT&CK
T1204.002 mitre ↗
Linked actors
Kinsing
False positives
Scoped to one indicator with skopnix confidence 77/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-c38c21120d8c17688f9aeb2af5bdafb6b75e1d2673b-00072353.ymldownload .yml ↓
title: Skopnix - Execution of known malicious file c38c21120d8c1768…
id: eaae3b99-156f-5df0-be14-ab0d24e803e2
status: experimental
description: Process image hash tracked by skopnix as Kinsing.
references:
  - https://skopnix.com/ioc/c38c21120d8c17688f9aeb2af5bdafb6b75e1d2673b025b720e50232f888808a
author: skopnix
date: '2026-10-18'
tags:
  - attack.execution
  - attack.t1204.002
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    Hashes|contains: SHA256=C38C21120D8C17688F9AEB2AF5BDAFB6B75E1D2673B025B720E50232F888808A
  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