Windows Security: Suspicious SAMTHEADMIN-* Computer/Account Names Ending with $

Alerts on Windows Security events with computer account names starting SAMTHEADMIN- and ending with $.

FreeReviewedSigma · Critical · v2
Product
windows
Service
security
Author
elhoim (SigmaHQ), DRL 1.1
Published
2022-09-09
Updated
2026-07-31

ATT&CK techniques

Initial Access → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags Windows Security events where a computer or related account name starts with "SAMTHEADMIN-" and ends with "$". Such naming patterns can indicate automated or hacktool-generated account creation, which attackers may use for initial access, persistence, privilege escalation, or stealth. It relies on telemetry fields that include SamAccountName and TargetUserName from Windows Security logging.

Related detections9 linkedT1078 — drag to rearrange
Possible Next.js Middleware Auth Bypass via X-Middleware-Subrequest Header (CVE-2025-29927)
Suspicious Brutforce with Denied Access Due to Account Restrictions Policies (via security)
Suspicious Success Login Attempt on a Windows OpenSSH Server (via security)
Suspicious SQL Server - Connection Attempt Using a Disabled Account (via application)
Suspicious Lateral Movement Detection - Based on "special Groups" Feature (via security)
Suspicious Snowflake Anomalous Client Application Associated With UNC5537 (via cloud)
Malicious Network Login Performed to Multiple Targets (via security)
Malicious RDP Reconnaissance with Valid Credentials Performed on Multiple Hosts (via security)
Malicious Local Administrator Added by Atera RMM Agent
Windows Security: Suspicious SAMTHEADMIN-* Computer/Account Names Ending with $
Pivot detection · T1078 · 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.