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

PAN-AMERICAN LIFE INSURANCE GROUP, INC. — February 2021 breach

Clustered 11 filings across 8 jurisdictions · filing window Mar 11, 2021 → May 11, 2021. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

8

Affected · reported

78,874

First → last filing

Mar 11, 2021 → May 11, 2021

Merge confidence

100%

incident inc_2800cb8af1fe4ded · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. Intrusion Feb 16, 2021–Feb 19, 2021, discovered Feb 19, 2021 — the first regulatory filing landed 20 days later. 78,874 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 4 more. Notifications rolled out on a 61-day schedule across 11 filings beginning Mar 11, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
20days

Discovered → first regulatory filing

Discovery variance
18days

Range of discovered_at dates across filings

Filing span
61days

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 clocksMaine⏱ ME AG >30d · 47dWashington✓ WA AG ≤30dMassachusetts✓ MA credit monitoring dueCalifornia✓ CA 60-day OK · 20dOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Feb 16, 2021breach begins
Feb 19, 2021discovered · members disagree
notification delay · 20 days
Mar 11, 2021first filing
May 11, 2021most 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. MAR 11WA AGWA AG noticefirst filing · 599 WA residentsday 0
  2. MAR 11MA AGMA AG notice3 MA residentsday 0
  3. MAR 11CA AGCA AG noticeno count statedday 0
  4. MAR 11ME AGME AG noticestates nationwide total 78,193day 0
  5. MAR 11OR AGOR AG noticestates nationwide total 78,193day 0
  6. MAR 11IN AGIN AG noticestates nationwide total 78,874day 0
  7. MAR 15NH AGNH AG noticeno count stated+4d
  8. MAR 16SC AGSC AG notice105 SC residents+5d
  9. APR 7ME AGME AG noticestates nationwide total 240+27d
  10. APR 30ME AGME AG noticestates nationwide total 441+50d
  11. MAY 11NH AGNH AG noticemost recent · no count stated+61d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 16, 2021
CA AG
Discovered
Feb 19, 2021WA AG + CA AG + ME AG +2Mar 9, 2021SC AG + NH AGfilings disagree on discovery
Data types
Financial · Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI
WA AG + MA AG + NH AG +3
Attack vector
Phishing
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)

78,874

Sum of filed state slices

2,149· 2.7% of stated

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

US78,874
IN1,396
WA599
SC105
ME46
MA3

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

61 days

Cadence

~1 / 6.1d

vs. multi-state median

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