DisclosureLens
State AGConfirmed6 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 6 filings

THE PRUDENTIAL INSURANCE COMPANY OF AMERICA — May 2023 breach

Clustered 6 filings across 6 jurisdictions · filing window Jul 27, 2023 Jul 31, 2023. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

6 filings

States

6

Affected · reported

360,615

First → last filing

Jul 27, 2023 Jul 31, 2023

Merge confidence

100%

incident inc_5b2703d542124a85 · merged by deterministic · confidence 100%

Part of the Pension Benefit Information, LLC supply-chain incident (2023)at least 31 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 6 regulatory filings. The filings describe a third-party compromise. Intrusion May 29, 2023–Jun 2, 2023, discovered May 31, 2023 — the first regulatory filing landed 57 days later. 360,615 individuals reported across the linked filings. Data reported: Government ID, Financial account, Financial credentials, and 4 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
57days

Discovered → first regulatory filing

Discovery variance
27days

Range of discovered_at dates across filings

Filing span
4days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delayno leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksWashington WA AG >30dMaine ME AG >30d · 34dOregon OR AG ≤45dMassachusetts MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

May 29, 2023breach begins
May 31, 2023discovered · members disagree
notification delay · 57 days
Jul 27, 2023first filing
Jul 31, 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 27WA AGWA AG noticefirst filing · 39,674 WA residentsday 0
  2. JUL 31OR AGOR AG noticestates nationwide total 320,840+4d
  3. JUL 31ME AGME AG notice320,840 affected+4d
  4. JUL 31IN AGIN AG noticestates nationwide total 242,464+4d
  5. JUL 31MA AGMA AG notice101 MA residents+4d
  6. JUL 31CA AGCA AG noticemost recent · no count stated+4d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 29, 2023May 30, 2023
WA AG
Discovered
May 31, 2023WA AG + CA AGJun 27, 2023OR AG + ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI · PII
WA AG + CA AG + ME AG +1
Attack vector
Third-Party / Supply Chain
WA 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)

320,840

Sum of filed state slices

40,149· 12.5% of stated

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

US320,840
WA39,674
IN374
MA101

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

4 days

Cadence

~1 / 0.8d

vs. multi-state median

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