DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed11 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 11 filings

GardaWorld Cash U.S. — October 2023 breach

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

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

39,928

First → last filing

Mar 1, 2024 → Mar 28, 2024

Merge confidence

100%

incident inc_5b47fc4cbb2f4463 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Oct 30, 2023–Nov 16, 2023, discovered Nov 16, 2023 — the first regulatory filing landed 106 days later (flagged late). 39,928 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 1 more. Notifications rolled out on a 27-day schedule across 11 filings beginning Mar 1, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
106days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
27days

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 clocksMaine✗ ME AG >90d · 127dCalifornia✗ CA 60-day late · 120dVermont✗ VT AG >45 bdayWashington✗ WA AG >90dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 30, 2023breach begins
Nov 16, 2023discovered
notification delay · 106 days
Mar 1, 2024first filing
Mar 28, 2024most 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. MAR 1IL AGIL AG noticefirst filing · no count statedday 0
  2. MAR 22MA AGMA AG notice1,136 MA residents+21d
  3. MAR 22ME AGME AG noticestates nationwide total 39,928+21d
  4. MAR 22CA AGCA AG noticeno count stated+21d
  5. MAR 22VT AGVT AG noticeno count stated+21d
  6. MAR 22OR AGOR AG noticestates nationwide total 39,928+21d
  7. MAR 22WA AGWA AG notice684 WA residents+21d
  8. MAR 22DE AGDE AG noticeno count stated+21d
  9. MAR 22IN AGIN AG noticestates nationwide total 39,928+21d
  10. MAR 22MT AGMT AG notice212 MT residents+21d
  11. MAR 28NH AGNH AG noticemost recent · 189 NH residents+27d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 30, 2023 – Nov 16, 2023
ME AG
Discovered
Nov 16, 2023· 17d undetected
IL AG + ME AG + CA AG +5
Data types
Health (basic) · Identity (basic) · Government ID · PHI
MA AG + ME AG + CA AG +5
Attack vector
Unauthorized Access
ME 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)

39,928

Sum of filed state slices

3,276· 8.2% of stated

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

US39,928
MA1,136
IN1,042
WA684
MT212
NH189
ME13

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 filing11 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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 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

27 days

Cadence

~1 / 2.7d

vs. multi-state median

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