Possible noPac sAMAccountName Spoofing via Machine Account Rename

PremiumReviewedSigma · Medium · v1
Product
windows
Service
security
Author
HuntRule
Published
2026-10-17
Updated
2026-10-17

ATT&CK techniques

Initial Access → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Execution

  4. Cred Access

  5. Discovery

  6. Lateral Movement

  7. Collection

  8. C2

  9. Exfiltration

  10. Impact

What it detects

This rule detects a computer account whose sAMAccountName is renamed away from its trailing dollar sign, the core step of the noPac privilege-escalation chain abusing CVE-2021-42278 and CVE-2021-42287. Renaming a machine account to impersonate a domain controller lets an attacker request Kerberos tickets that escalate to Domain Admin.

Related detections9 linkedT1068 — drag to rearrange
Possible macOS TCC Bypass via mdimport Loading Custom Spotlight Importer
Suspicious CLFS Base Log File Created in SkyPDF ProgramData Path during Zero-Day Exploitation (via file_event)
Malicious Cisco SD-WAN Tenant List Upload Script Execution (via process_creation)
Possible Cisco Catalyst SD-WAN Manager Tenant Upload Exploitation CVE-2026-20245 (via process_creation)
Suspicious Modification of CloudFiles BlockedApps Policy via registry_set
Suspicious Command Shell Spawned by lmadmin License Manager via process_creation
Suspicious Named Pipe TyphoonPWN Local Privilege Escalation Marker (via pipe_created)
Suspicious Dell DBUtilDrv2 Vulnerable Driver Load via driver_load
Malicious Potato Privilege Escalation Tooling Execution
Possible noPac sAMAccountName Spoofing via Machine Account Rename
Pivot detection · T1068 · 9 related

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