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

Teachers Insurance and Annuity Association of America — May 2023 breach

Clustered 10 filings across 9 jurisdictions · filing window Jul 14, 2023 → Aug 17, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

9

Affected · reported

2,373,076

First → last filing

Jul 14, 2023 → Aug 17, 2023

Merge confidence

100%

incident inc_9ecdc1e131254995 · merged by deterministic · confidence 100%

Part of the Progress Software Corporation supply-chain incident (2023) — at least 97 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe a third-party compromise. Intrusion May 29, 2023–May 30, 2023, discovered May 31, 2023 — the first regulatory filing landed 44 days later. 2,373,076 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 34-day schedule across 10 filings beginning Jul 14, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
44days

Discovered → first regulatory filing

Discovery variance
28days

Range of discovered_at dates across filings

Filing span
34days

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 clocksWashington⏱ WA AG >30dMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 26dHawaii✓ HI CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 29, 2023breach begins
May 31, 2023discovered · members disagree
notification delay · 44 days
Jul 14, 2023first filing
Aug 17, 2023most 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. JUL 14IN AGIN AG noticefirst filing · states nationwide total 2,373,076day 0
  2. JUL 14DE AGDE AG noticeno count statedday 0
  3. JUL 21MA AGMA AG notice105,508 MA residents+7d
  4. JUL 21MT AGMT AG notice5,977 MT residents+7d
  5. JUL 21CA AGCA AG noticeno count stated+7d
  6. JUL 24CA AGCA AG noticeno count stated+10d
  7. JUL 24ME AGME AG noticestates nationwide total 2,373,076+10d
  8. JUL 27WA AGWA AG notice56,331 WA residents+13d
  9. JUL 27HI AGHI AG notice10,322 HI residents+13d
  10. AUG 17NH AGNH AG noticemost recent · no count stated+34d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 29, 2023
IN AG
Discovered
May 31, 2023CA AG + NH AGJun 9, 2023WA AGJun 28, 2023ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
DE AG + MT AG + CA AG +5
Attack vector
Third-Party / Supply Chain
DE 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)

2,373,076

Sum of filed state slices

243,709· 10.3% of stated

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

US2,373,076
MA105,508
WA56,331
IN47,931
ME17,640
HI10,322
MT5,977

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

34 days

Cadence

~1 / 3.8d

vs. multi-state median

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