huntrule

Windows Security Log: Metasploit SMB NTLM Logon (4624/4625, 4776)

Detects Metasploit-linked NTLM SMB authentication activity using Windows 4624/4625 and 4776 with 16-char workstation names.

FreeReviewedSigma · High · v2
Product
windows
Service
security
Author
Chakib Gzenayi (@Chak092), Hosni Mribah (SigmaHQ), DRL 1.1
Published
2020-05-06
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Lateral Movement

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

Identifies failed (4625) and successful (4624) network logons using NTLM over SMB associated with 16-character alphanumeric workstation names, alongside corresponding 4776 authentication attempts. This matters because Metasploit-style SMB authentication activity can be part of lateral movement. The rule relies on Windows Security events 4624/4625 with LogonType 3 and AuthenticationPackageName=NTLM, and 4776 entries that share matching workstation naming patterns.

Reporting behind it

Related detections9 linkedT1021.002 — drag to rearrange
Suspicious Access to Citrix Session Evidence Registry Keys
Suspicious Ransomware Fan-Out Deployment via PsExec Spread (Qilin)
Suspicious Impacket smbexec Command Execution Pattern
Malicious Impacket Wmiexec Remote Command Execution Pattern
Suspicious Remote Admin Share Execution via Conhost
Malicious Network Share Manipulation via Commandline (via process_creation)
Suspicious Number of Oustanding SMB Requests Increased (via process_creation)
Suspicious SMB Insecure Guest Authentication Activated - Native (via security)
Suspicious PSexec Execution Over SMB Share (via security)
Windows Security Log: Metasploit SMB NTLM Logon (4624/4625, 4776)
Pivot detection · T1021.002 · 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.