American National Group, LLC — May 2023 breach

One linked filing — more sources may join as they report · filed Aug 9, 2023.

Determination

Confirmed

Members

1 filing

States

Affected · reported

—

First → last filing

Aug 9, 2023

incident inc_9440b48bf74a4774 · merged by deterministic

Part of the Progress Software Corporation supply-chain incident (2023) — at least 93 organizations filed notifications naming this third party.

Confirmed breach. Intrusion May 28, 2023, discovered May 31, 2023 — the first regulatory filing landed 70 days later.

Litigation Timing

Notification delay

70days

Discovered → first regulatory filing

Not recorded for this incident

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

Sensitive data

identity_government

Incident timeline

May 28, 2023breach begins

May 31, 2023discovered

notification delay · 70 days

Aug 9, 2023first & only filing

—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

AUG 9CA AGCA AG noticeonly filing · no count statedday 0

Roll-up facts — reconciled across members

Breach window: May 28, 2023
Discovered: May 31, 2023· 3d undetected
Data types: Identity (basic) · Government ID · PHI · Health (basic)
Attack vector: Third-Party / Supply Chain
Response: Took the application offline · Launched an investigation · Engaged third-party advisors and incident response professionals

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

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

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.