Windows File Access to Cryptocurrency Wallet Keystores by Uncommon Processes

Alerts on access to Ethereum/Bitcoin-style wallet files from non-standard processes on Windows.

FreeReviewedSigma · Medium · v2
Product
windows
Category
file_access
Author
X__Junior (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2024-07-29
Updated
2026-07-31

ATT&CK techniques

Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags file access events where the accessed path matches common cryptocurrency wallet storage locations in the Windows user profile (e.g., Ethereum/Monero keystores and Bitcoin-derived wallet.dat files). Such activity can indicate attempts to steal or tamper with cryptocurrency credentials and keys from local wallet files. It relies on Windows file access telemetry (Kernel File ETW) capturing the FileName and the initiating process Image, with exclusions for System and common Windows/Defender binaries to reduce benign matches.

Related detections9 linkedT1003 — drag to rearrange
Malicious Wdigest Authentication Enabled - Reg via Command (via process_creation)
Malicious Diskshadow Command Abuse to Expose VSS Backup (via process_creation)
Malicious IIS Application Pool Credential Dumping (via process_creation)
Malicious Wdigest Authentication Enabled - Registry (via registry_set)
Suspicious Veeam Backup Credential Harvesting via PowerShell (via ps_script)
Suspicious Network Provider Registration for Credential Interception via NPPSpy
Malicious Mimikatz Malicious Security Package (SSP) Exfiltrates Cleartext Passwords in File (via file_event)
Malicious WDigest UseLogonCredential Enablement For Credential Theft
Linux: Detect changes to fs.suid_dumpable enabling core dumps for SUID processes
Windows File Access to Cryptocurrency Wallet Keystores by Uncommon Processes
Pivot detection · T1003 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.