DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed28 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlockbit_3critical sensitivity
Merged incident · 28 filings

INFOSYS MCCAMISH SYSTEMS, LLC — October 2023 breach

Clustered 28 filings across 9 jurisdictions · filing window Feb 1, 2024 → Mar 21, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

28 filings

States

9

Affected · reported

6,078,263

First → last filing

Feb 1, 2024 → Mar 21, 2025

Merge confidence

100%

incident inc_a7d13eb999f34918 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 28 regulatory filings. Intrusion Oct 29, 2023–Nov 3, 2023, discovered Oct 30, 2023 — the first regulatory filing landed 94 days later (flagged late). 6,078,263 individuals reported across the linked filings. Data reported: Government ID, Biometric, Identity (basic), and 7 more. Notifications rolled out on a 414-day schedule across 28 filings beginning Feb 1, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
94days

Discovered → first regulatory filing

Discovery variance
106days

Range of discovered_at dates across filings

Filing span
414days

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.

Regulatory clocksWashington✗ WA AG >90dCalifornia✗ CA 60-day late · 208dOregon✗ OR AG >45dVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 238dFull clock table in Litigation Timeline

Sensitive data

authenticationbiometricidentity_government

Incident timeline

Oct 29, 2023breach begins
Oct 30, 2023discovered · members disagree
notification delay · 94 days
Feb 1, 2024first filing
Mar 21, 2025most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. FEB 1DE AGDE AG noticefirst filing · no count statedday 0
  2. FEB 2WA AGWA AG notice857 WA residents+1d
  3. FEB 2CA AGCA AG noticeno count stated+1d
  4. FEB 2OR AGOR AG noticestates nationwide total 57,028+1d
  5. FEB 23NH AGNH AG notice100 NH residents+22d
  6. MAR 1OR AGOR AG noticestates nationwide total 28,268+29d
  7. JUN 7NH AGNH AG notice3,352 NH residents+127d
  8. JUN 27WA AGWA AG notice43,393 WA residents+147d
  9. JUN 27VT AGVT AG noticeno count stated+147d
  10. JUN 27MT AGMT AG notice5,426 MT residents+147d
  11. JUN 27IN AGIN AG noticestates nationwide total 6,078,263+147d
  12. JUN 27DE AGDE AG notice10,609 DE residents+147d
  13. JUN 27OR AGOR AG noticestates nationwide total 6,078,263+147d
  14. JUN 27ME AGME AG noticestates nationwide total 6,078,263+147d
  15. JUN 28CA AGCA AG noticestates nationwide total 2,424+148d
  16. JUL 19CA AGCA AG noticeno count stated+169d
  17. AUG 13ME AGME AG noticestates nationwide total 6,078,263+194d
  18. AUG 15CA AGCA AG noticestates nationwide total 2,424+196d
  19. SEP 9NH AGNH AG noticeno count stated+221d
  20. SEP 9CA AGCA AG noticestates nationwide total 2,424+221d
  21. SEP 9ME AGME AG noticestates nationwide total 6,078,263+221d
  22. OCT 17NH AGNH AG notice101 NH residents+259d
  23. OCT 21CA AGCA AG noticestates nationwide total 2,424+263d
  24. OCT 21ME AGME AG noticestates nationwide total 6,078,263+263d
  25. NOV 15MT AGMT AG notice189 MT residents+288d
  26. DEC 10CA AGCA AG noticestates nationwide total 2,424+313d
  27. MAR 21ME AGME AG noticestates nationwide total 6,078,263+414d
  28. MAR 21CA AGCA AG noticemost recent · states nationwide total 2,424+414d
  29. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 3, 2023
DE AG
Discovered
Oct 30, 2023WA AG + OR AGNov 2, 2023NH AG + WA AG + VT AG +4Nov 3, 2023CA AGFeb 13, 2024OR AGfilings disagree on discovery
Data types
Authentication · Biometric · Credentials · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
DE AG + WA AG + CA AG +4
Attack vector
Unauthorized Access
DE 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)

6,078,263

Sum of filed state slices

131,415· 2.2% of stated

98% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US6,078,263
IN56,769
WA43,393
ME11,866
DE10,609
MT5,426
NH3,352

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

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing28 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 10, 2026 · at least one link edge was human-adjudicated
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

414 days

Cadence

~1 / 15.3d

vs. multi-state median

51.8× 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.