DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed9 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmazehigh sensitivity
Merged incident · 9 filings

Collabera — May 2020 breach

Clustered 9 filings across 9 jurisdictions · filing window Jun 8, 2020 → Jul 21, 2020. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

8

Affected · reported

72,594

First → last filing

Jun 8, 2020 → Jul 21, 2020

Merge confidence

100%

incident inc_e277174d05024be9 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 1 unverified claim. The filings describe a ransomware attack. Intrusion May 24, 2020–Jun 8, 2020, discovered Jun 8, 2020 — the first regulatory filing landed 31 days later. 72,594 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 43-day schedule across 8 filings beginning Jun 8, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
31days

Discovered → first regulatory filing

Discovery variance
2days

Range of discovered_at dates across filings

Leak precedence
31days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
43days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 24, 2020breach begins
Jun 8, 2020discovered · members disagree
notification delay · 31 days
Jul 9, 2020first filing
Jul 21, 2020most 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. JUN 8Leak sitemaze postfirst filing · attacker claim · unverifiedday 0
  2. JUL 9MT AGMT AG notice14 MT residents+31d
  3. JUL 9WA AGWA AG noticeno count stated+31d
  4. JUL 10IN AGIN AG noticestates nationwide total 72,594+32d
  5. JUL 10DE AGDE AG noticeno count stated+32d
  6. JUL 17NH AGNH AG notice129 NH residents+39d
  7. JUL 21MA AGMA AG notice1,201 MA residents+43d
  8. JUL 21CA AGCA AG noticeno count stated+43d
  9. JUL 21OR AGOR AG noticemost recent · states nationwide total 72,594+43d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 24, 2020 – Jun 8, 2020
WA AG
Discovered
Jun 8, 2020MT AG + WA AG + DE AG +2Jun 10, 2020OR AGfilings disagree on discovery
Data types
Employment · Identity (basic) · Government ID · PII
MT AG + WA AG + DE AG +3
Attack vector
Ransomware
MT 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)

72,594

Sum of filed state slices

1,704· 2.3% of stated

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

US72,594
MA1,201
IN360
NH129
MT14

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing8 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 Aug 22, 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

43 days

Cadence

~1 / 5.4d

vs. multi-state median

4.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.