Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/hunting-anomalous-authentication-patternsDFIR and threat hunting

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-patterns

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
3nYtcmLpeq…eufWZ6Dw==The CLI checks the SHA-256 and the signature before it writes a file.
Package26bef801…c9c94f20
26bef8014e3e…cf3cc9c94f204 files · ⁦3.2 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/hunting-anomalous-authentication-patterns@da7600a

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

bash
python scripts/analyst.py hunt logons.csv

Computes 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.md for the hunter.
  • ATT&CK T1110.003 and Event 4625/4624 docs (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600a26bef801Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login