Arrowhead Regional Computing Consortium — February 2023 breach
Clustered 4 filings across 4 jurisdictions · filing window Jan 11, 2024 → Jan 17, 2024. View entity profile → Other incidents for this victim →
incident inc_31e8e457ce284a77 · merged by deterministic · confidence 100%
Litigation Timing
Discovered → first regulatory filing
Range of discovered_at dates across filings
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
Sensitive data
identity_governmentIncident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- JAN 11IN AGIN AG noticefirst filing · states nationwide total 65,010auto-linkedday 0
- JAN 11VT AGVT AG noticeno count statedauto-linkedday 0
- JAN 11ME AGME AG noticestates nationwide total 65,010day 0
- JAN 17NH AGNH AG noticemost recent · 25 NH residentsauto-linked+6d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Feb 6, 2023 IN AG
- Discovered
- Feb 6, 2023NH AGDec 7, 2023ME AGfilings disagree on discovery
- Data types
- Financial account · Identity (basic) · Government ID VT AG + ME AG + NH AG
- Attack vector
- Unauthorized Access VT AG
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Count reconciliation
per-state reported counts
Nationwide (stated in a filing)
65,010
Sum of filed state slices
126· 0.2% of stated
100% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.
Evidence ladder — rungs this incident occupies
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
Merge provenance
- Method
- deterministic
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Audit
- Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).
Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.
Filing velocity
Spread
6 days
Cadence
~1 / 2d
vs. multi-state median
1.5× faster
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.