Enforced3 records · 1 stateUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 3 records

University of Massachusetts Amherst

Clustered 3 records across 2 jurisdictions: 2 filings and 1 enforcement record · filing window Jun 5, 2013 → Jun 10, 2013. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Enforced

Members

3 records

States

Affected · reported

1,670

First → last filing

Jun 5, 2013 → Jun 10, 2013

Merge confidence

100%

incident inc_4365931d152645d9 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings and 1 enforcement record. The filing describes unauthorized access. 1,670 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Filing span

5days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

? — ?breach window unknown

Jun 5, 2013first filing

Jun 10, 2013most recent filing

No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge.

Member cascade — every filing and enforcement record in this incident

JUN 5HHS OCRHHS OCR noticefirst filing · states nationwide total 1,670day 0
JUN 10MA AGMA AG notice1,472 MA residentsauto-linked+5d
NOV 22HHS OCR enforcementHHS OCR enforcement noticemost recent · no count statedoperator-confirmed+1266d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: —
Discovered: —
Data types: Financial account · Health (basic) · Identity (basic) · Government ID · PCI
Attack vector: Unauthorized Access

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)

1,670

Sum of filed state slices

1,472· 88.1% of stated

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

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 filing3 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 24, 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

5 days

vs. multi-state median

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