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
Suspicious Credential Dump via lsa.exe Debug Output
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
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.