Windows WCE wceaux.dll File Access via Security Event 4656/4663

Identifies Windows Security event activity involving access to the wceaux.dll library file.

FreeReviewedSigma · Critical · v2
Product
windows
Service
security
Author
Thomas Patzke (SigmaHQ), DRL 1.1
Published
2017-06-14
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 access to the Windows component file wceaux.dll by matching Windows Security auditing events 4656 and 4663 for objects whose name ends with \wceaux.dll. File access to specific DLLs can be indicative of tools or payloads being loaded or interacted with during remote execution workflows. Detection relies on Security log telemetry that includes the file object name and access-related event IDs.

Related detections9 linkedT1003 — drag to rearrange
Malicious NTDS Credential Dump via Ntdsutil IFM Snapshot (via process_creation)
Suspicious Mimilite Credential Dumper Execution Writing KB-Named Output
Malicious InternalMonologue NTLM Downgrade Execution via process_creation
Suspicious Modification of msDS-KeyCredentialLink for Shadow Credential Abuse
Possible OxideHarvest Stealer Execution via Combined Short Flag Set
Suspicious Credential Dump Attempt via Task Manager (via process_creation)
Suspicious Ivanti EPMM Database Dump via mysqldump with .mifpp Credentials (via process_creation)
Suspicious Credential Dump via lsa.exe Debug Output
Malicious Wdigest Authentication Enabled - Reg via Command (via process_creation)
Windows WCE wceaux.dll File Access via Security Event 4656/4663
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.