DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed8 records · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmontihigh sensitivity
Merged incident · 8 records

Cambridge College — February 2023 breach

Clustered 8 records across 7 jurisdictions: 7 filings and 1 leak-site claim · filing window Aug 4, 2023 → Aug 11, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 records

States

7

Affected · reported

30,368

First → last filing

Aug 4, 2023 → Aug 11, 2023

Merge confidence

100%

incident inc_fc7d207ba7b44c57 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Feb 20, 2023–Mar 2, 2023, discovered Mar 2, 2023 — the first regulatory filing landed 155 days later. 30,368 individuals reported across the linked filings. Data reported: Government ID, Financial account, PCI, and 4 more. Notifications rolled out on a 7-day schedule across 7 filings beginning Aug 4, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
155days

Discovered → first regulatory filing

Discovery variance
126days

Range of discovered_at dates across filings

Leak precedence
142days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
7days

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 >90dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Feb 20, 2023breach begins
Mar 2, 2023discovered · members disagree
notification delay · 155 days
Aug 4, 2023first filing
Aug 11, 2023most recent filing

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

Member cascade — every filing and leak-site claim in this incident

  1. MAR 15Leak sitemonti postfirst record · attacker claim · unverifiedday 0
  2. AUG 4MA AGMA AG notice18,778 MA residents+142d
  3. AUG 4MT AGMT AG notice3 MT residents+142d
  4. AUG 4CA AGCA AG noticeno count stated+142d
  5. AUG 4ME AGME AG noticestates nationwide total 30,368+142d
  6. AUG 4VT AGVT AG noticeno count stated+142d
  7. AUG 4IN AGIN AG noticestates nationwide total 30,368+142d
  8. AUG 11NH AGNH AG noticemost recent · 429 NH residents+149d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 20, 2023 – Mar 2, 2023
MT AG
Discovered
Mar 2, 2023MT AGJul 6, 2023ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PCI · PII
MA AG + MT AG + CA AG +3
Attack vector
Unauthorized Access
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)

30,368

Sum of filed state slices

19,318· 63.6% of stated

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

US30,368
MA18,778
NH429
ME96
IN12
MT3

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 filing7 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 Sep 28, 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

7 days

Cadence

~1 / 1.2d

vs. multi-state median

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