hunting-anomalous-authentication-patterns
Hunts for anomalous authentication such as password spraying, brute force, and
v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/hunting-anomalous-authentication-patternsWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package26bef801…c9c94f20
26bef8014e3e…cf3cc9c94f204 files · 3.2 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/hunting-anomalous-authentication-patterns@da7600a
On this page
When to Use
- You have Windows logon success (4624) and failure (4625) events and want to detect password spraying (one password across many accounts), brute force (many failures per account), and suspicious source concentration.
- You are investigating credential-access attempts against accounts.
Do not use this for a single failed logon — it relies on aggregation across accounts/sources to find patterns, not individual events.
Prerequisites
- Logon events with account, source IP/host, status, and timestamp.
Workflow
Step 1: Aggregate auth outcomes
python scripts/analyst.py hunt logons.csvComputes failures per account, distinct accounts targeted per source (spray signal), and failure→success transitions per account (possible compromise).
Step 2: Surface patterns
- Spray: one source failing against many distinct accounts.
- Brute force: many failures against one account from a source.
- Breakthrough: a burst of failures followed by a success.
Step 3: Confirm
Correlate sources with known infrastructure; check whether successes are legitimate.
Step 4: Operationalize
Set thresholds and write a detection (e.g., source touching ≥ N accounts within a window).
Validation
- Spray detection keys on distinct-account breadth per source, not raw failure count.
- Brute force keys on per-account failure concentration.
- Failure-then-success transitions are reported for follow-up.
Pitfalls
- Service accounts/misconfigured apps generating benign failure storms.
- NAT/proxy collapsing many users behind one source IP, mimicking spray.
- Time-window choice: too wide hides bursts, too narrow misses slow sprays.
References
- See
references/api-reference.mdfor the hunter. - ATT&CK T1110.003 and Event 4625/4624 docs (linked in frontmatter).
Files in this version
references/11.3 KB
- api-reference.md1.3 KB
scripts/13.5 KB
- analyst.py3.5 KB
- LICENSE340 B
- SKILL.md2.8 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumFile · Executable script shipped with the skillscripts/analyst.py
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v1.0.0 | Nov 13, 2026 | da7600a | 26bef801 | Signed | – |
More from meltedinhex
All from this publisher- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
More in DFIR and threat hunting
See the category- hunting-for-command-and-control-beaconingmukul975/hunting-for-command-and-control-beaconing5
- audit-context-buildingtrailofbits/audit-context-building4
- incident-response-forensicssecurityskills/incident-response-forensics3
- extracting-credentials-from-memory-dumpmukul975/extracting-credentials-from-memory-dump3
- analyzing-browser-forensics-with-hindsightmukul975/analyzing-browser-forensics-with-hindsight3
- forensics-ctfaeondave/forensics-ctf3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login