Incident: Failed logon burst followed by successful authentication (+1 related finding)

Case
CASE-001
Generated
2026-09-26 11:07:33 UTC
Status
complete
Severity
CRITICAL
Grouping confidence
medium (how strongly findings are linked, not whether an intrusion occurred)
Hosts
WS-2138, WS-9673
Accounts
acct-2520
Window
2026-08-01 08:00:00 -> 08:06:00 UTC (360s)
Telemetry
generated_auth_execution

This report was produced by an automated investigation. It presents evidence-backed findings for analyst review and does not authorise or perform any response action.

Verdict

Disposition
Malicious
Decided by
deterministic triage of the seed findings
Engine
deterministic
Profile
operational-v6
Model
none (deterministic engine)
Evidence basis
30 typed observation(s) checked against recorded telemetry; 0 claim(s) rejected by verification; 3 specialist step(s) run (endpoint, identity, attack); 8 tool call(s) served, 0 refused.
Supporting event ids
none cited by the concluding explanations

This system does not compute a confidence score for its verdict. The evidence basis is a count of what was checked, not a measure of how likely the verdict is.

Investigation Tree

Reasoning Summary

No model-written reasoning: this run used no model. Its reasoning is the specialist trace in the investigation tree and the findings below.

Executive Summary

This report covers CASE-001, correlating 2 detection finding(s) across 2 host(s) (WS-2138, WS-9673) and 1 account(s) (acct-2520) between 08:00:00 and 08:06:00 UTC on 2026-08-01. The evidence is consistent with activity spanning 4 MITRE ATT&CK tactic(s): Execution -> Persistence -> Credential Access -> Lateral Movement. Each mapping is an interpretation of observed behaviour against a public taxonomy, not a determination that an intrusion occurred. 30 statement(s) below are directly established by telemetry, 11 are evidence-supported inferences, and 0 are explicitly unverified hypotheses requiring analyst confirmation. This report does not authorise or perform any response action. All recommendations below require human review before action is taken.

Attack Timeline

TimeRuleSeverityUserHost / MovementATT&CKEvents
08:00:00ATH-005CRITICALacct-2520WS-9673T1078, T1110.0010cb61159ea3d69dcc87a, d92873fb243f9f0bcb0d, 3bdd60cc3a5a97b84519, a068ff51cd2cb23d2f8d, 2108af7a380995a548b5, 6e10a5cc29314bc6a964, +7 more
08:06:00ATH-007HIGHacct-2520WS-9673T1021.002, T1569.002c1aa4d45ddf2102946f7

Findings

Confirmed (FACT) (30)

Assessed (INFERENCE) (11)

Unconfirmed Hypotheses (0)

Recommended Next Steps

Investigative recommendations for a human analyst. No response action has been taken or is authorised by this report.

  1. Retrieve email gateway or web-proxy logs to establish the initial access vector.
    Rationale: No detection in this case targets initial access, so the delivery mechanism (e.g. a phishing attachment) is inferred from process lineage rather than confirmed from delivery telemetry.
    Based on: MITRE ATT&CK tactic coverage gap: Initial Access
  2. Independently verify account activity on all hosts in scope (WS-2138, WS-9673) rather than relying solely on the correlated case, in case related activity exists that current detections did not flag.
    Rationale: This case spans multiple hosts, which increases the possible blast radius.
    Based on: case.is_multi_host
  3. Escalate to a human analyst for validation before any remediation action is taken.
    Rationale: This system performs read-only investigation only. It has no capability to disable accounts, isolate hosts, or otherwise remediate, and this report is not authorisation to do so.
    Based on: system design constraint

Limitations & Scope

Investigation Trace

Agents run: endpoint, identity, attack; tool calls made: 8

Evidence Appendix

All 28 telemetry events underlying this report, chronologically.

Event IDTimeDeviceUserSummary
0cb61159ea3d69dcc87a08:00:00WS-9673acct-2520failure logon [Network (SMB / share access)] from 10.10.2.8 reason=bad_password
98c80712635dec2f373808:00:00WS-9673acct-2520wininit.exe -> services.exe | services.exe
0ce208dd57c057228f5508:00:00OFFICE-01acct-2520success logon [Interactive (console)] from 10.10.1.5
d92873fb243f9f0bcb0d08:00:20WS-9673acct-2520failure logon [Network (SMB / share access)] from 10.10.2.8 reason=bad_password
8144033a5e9cd2c19c3808:00:29OFFICE-01acct-2520success logon [Interactive (console)] from 10.10.1.5
3bdd60cc3a5a97b8451908:00:40WS-9673acct-2520failure logon [Network (SMB / share access)] from 10.10.2.8 reason=bad_password
78274bf69ec1ff50809308:00:58OFFICE-01acct-2520success logon [Interactive (console)] from 10.10.1.5
a068ff51cd2cb23d2f8d08:01:00WS-9673acct-2520failure logon [Network (SMB / share access)] from 10.10.2.8 reason=bad_password
2108af7a380995a548b508:01:20WS-9673acct-2520failure logon [Network (SMB / share access)] from 10.10.2.8 reason=bad_password
c532eb018e1154acca2e08:01:27OFFICE-01acct-2520success logon [Interactive (console)] from 10.10.1.5
6e10a5cc29314bc6a96408:01:40WS-9673acct-2520failure logon [Network (SMB / share access)] from 10.10.2.8 reason=bad_password
7c156d83425329cf030a08:01:56OFFICE-01acct-2520success logon [Interactive (console)] from 10.10.1.5
a3bf61cc981c8d0cdd5d08:02:00WS-9673acct-2520failure logon [Network (SMB / share access)] from 10.10.2.8 reason=bad_password
f6497a719ee487d49e5a08:02:20WS-9673acct-2520failure logon [Network (SMB / share access)] from 10.10.2.8 reason=bad_password
0d4ac76c0560bdbb704b08:02:25OFFICE-01acct-2520success logon [Interactive (console)] from 10.10.1.5
0cc680d6694f1f8615a108:02:40WS-9673acct-2520failure logon [Network (SMB / share access)] from 10.10.2.8 reason=bad_password
dfd20d6fe31907ff2b8608:02:54OFFICE-01acct-2520success logon [Interactive (console)] from 10.10.1.5
8407329aafd15d9c0a9e08:03:00WS-9673acct-2520failure logon [Network (SMB / share access)] from 10.10.2.8 reason=bad_password
0adbb9ef85b9188c868308:03:20WS-9673acct-2520failure logon [Network (SMB / share access)] from 10.10.2.8 reason=bad_password
fbe91286e9d9acc93b9e08:03:23OFFICE-01acct-2520success logon [Interactive (console)] from 10.10.1.5
bc5bc87bcd4bf982780708:03:40WS-9673acct-2520failure logon [Network (SMB / share access)] from 10.10.2.8 reason=bad_password
e5a3cce5c1c4a821f59d08:03:52OFFICE-01acct-2520success logon [Interactive (console)] from 10.10.1.5
9ad22469dab49a3df6fc08:04:21OFFICE-01acct-2520success logon [Interactive (console)] from 10.10.1.5
5c0abbbce84e1b2a43fa08:04:50OFFICE-01acct-2520success logon [Interactive (console)] from 10.10.1.5
67a9f5bfab28871757dd08:05:00WS-9673acct-2520success logon [Network (SMB / share access)] from 10.10.2.8
9b73d640145c27f1eddb08:05:19OFFICE-01acct-2520success logon [Interactive (console)] from 10.10.1.5
c1aa4d45ddf2102946f708:06:00WS-9673acct-2520services.exe -> cmd.exe | cmd.exe /Q /c job.cmd 1> \\127.0.0.1\ADMIN$\job.log 2>&1
0b092d00f3798939dd0008:06:05WS-9673acct-2520cmd.exe -> dism.exe | dism.exe /Online /Cleanup-Image /ScanHealth