Suspicious JumpCloud Password Brute Force Followed by Success

PremiumReviewedSigma · Medium · v1
Product
jumpcloud
Service
directory
Author
HuntRule
Published
2026-06-05
Updated
2026-08-28

ATT&CK techniques

Cred Access
  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

This rule detects a JumpCloud account accumulating ten or more failed login attempts within a short window, indicating password brute forcing. A burst of authentication failures against one identity signals credential guessing that may precede a successful takeover.

Related detections9 linkedT1110 — drag to rearrange
Malicious SQL Server - Brutforce Enumeration with Non Existing Users - Login (via application)
Malicious Brutforce Enumeration with Non Existing Users - Login (via security)
Malicious Brutforce Enumeration on Windows OpenSSH Server with Non Existing User (via security)
Malicious Brutforce on Windows OpenSSH Server with Valid Users (via security)
Malicious RDP Discovery Performed on Multiple Hosts (via rdp)
Possible SonicWall Credential Testing via userLogin Endpoint
Malicious Brutforce Enumeration with Unexisting Users - Kerberos (via security)
AWS CloudTrail ConsoleLogin Failed authentication
Bitbucket audit: User login failed authentication events
Suspicious JumpCloud Password Brute Force Followed by Success
Pivot detection · T1110 · 9 related

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