Execution of known malicious file 007a67bfa732084b…
SIGmediumconfidence 72/100generated 2026-10-18
Process image hash tracked by skopnix as romcom.
- Linked actors
- RomCom
- 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-md5-007a67bfa732084b3f8278b302bef49e-f03aea5b.ymldownload .yml ↓title: Skopnix - Execution of known malicious file 007a67bfa732084b…
id: 270d0747-ba35-5978-818e-d6dcec77ae24
status: experimental
description: Process image hash tracked by skopnix as romcom.
references:
- https://skopnix.com/ioc/007a67bfa732084b3f8278b302bef49e
author: skopnix
date: '2026-10-18'
tags:
- attack.execution
- attack.t1204.002
logsource:
category: process_creation
product: windows
detection:
selection:
Hashes|contains: MD5=007A67BFA732084B3F8278B302BEF49E
condition: selection
falsepositives:
- Legitimate services sharing the address; verify against skopnix confidence + last_seen
level: medium
How to deploy on Sigma
- 1.Convert for your SIEM with sigma-cli / pySigma, e.g. sigma convert -t splunk -p sysmon rule.yml.
- 2.Run it as a hunt first: every rule ships as status experimental.
- 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.