MICROSOFT CORPORATION — November 2023 breach
Clustered 2 filings across 1 jurisdiction · filing window Jan 19, 2024 → Mar 8, 2024. View entity profile → Other incidents for this victim →
incident inc_be1747af8c9340a9 · merged by llm · confidence 63%
Litigation Timing
SupplementalDiscovered → first regulatory filing
Discovery to SEC materiality determination
Materiality determination to SEC 8-K filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence — no leak-site claim in this cluster; needs two dated filings.
Incident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- JAN 19SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
- MAR 8SEC 8-KSEC 8-K noticemost recent · no count stated+49d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Nov 1, 2023 SEC 8-K
- Discovered
- Jan 12, 2024· 72d undetected SEC 8-K
- Data types
- Credentials · IP / system · Metadata · Other SEC 8-K
- Attack vector
- Unauthorized Access· Midnight Blizzard SEC 8-K
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Evidence ladder — rungs this incident occupies
No leak-site claim on record for this incident.
No press coverage linked yet.
No regulator filing linked yet.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Merge provenance
- Method
- llm
- Confidence
- 0.63 · below the 0.85 auto-merge floor
- Audit
- Every link edge records its method, confidence and model + prompt versions (63% is the strongest edge).
Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.
Filing velocity
Spread
49 days
vs. multi-state median
8.2× slower
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.
The weekly clock on records like this one
The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.
Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.