All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed3 filings · 3 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 3 filings

Pennsylvania Higher Education Assistance Agency — December 2022 breach

Clustered 3 filings across 3 jurisdictions · filing window Jul 1, 2024 → Jul 10, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

Affected · reported

281

First → last filing

Jul 1, 2024 → Jul 10, 2024

Merge confidence

100%

incident inc_db6421363139498a · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filing describes a third-party compromise. Intrusion Dec 4, 2022–May 30, 2023, discovered Jul 10, 2024. 281 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Education. Notifications rolled out on a 9-day schedule across 3 filings beginning Jul 1, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Filing span

9days

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 clocksMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 4, 2022breach begins

Jul 10, 2024discovered

Jul 1, 2024first filing

Jul 10, 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

JUL 1ME AGME AG noticefirst filing · states nationwide total 281day 0
JUL 2MA AGMA AG notice5 MA residentsauto-linked+1d
JUL 10IN AGIN AG noticemost recent · states nationwide total 281auto-linked+9d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Dec 4, 2022 – May 30, 2023
Discovered: Jul 10, 2024· 584d undetected
Data types: Education · Identity (basic) · Government ID
Attack vector: Third-Party / Supply Chain

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)

281

Sum of filed state slices

10· 3.6% of stated

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

US281

MA5

IN4

ME1

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

9 days

Cadence

~1 / 4.5d

vs. multi-state median

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