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

Elephant Insurance Services, LLC — September 2021 breach

Clustered 13 filings across 11 jurisdictions · filing window May 25, 2022 → Feb 27, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 filings

States

11

Affected · reported

2,762,687

First → last filing

May 25, 2022 → Feb 27, 2023

Merge confidence

100%

incident inc_9d8175d6096b421a · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 13 regulatory filings. The filings describe unauthorized access. Intrusion Sep 1, 2021–Apr 1, 2022, discovered Apr 1, 2022 — the first regulatory filing landed 54 days later (flagged late). 2,762,687 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 278-day schedule across 13 filings beginning May 25, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
54days

Discovered → first regulatory filing

Discovery variance
24days

Range of discovered_at dates across filings

Filing span
278days

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 clocksVermont✗ VT AG >45 bdayOregon✗ OR AG >45dMaine✓ ME AG ≤30d · 30dCalifornia✓ CA 60-day OK · 24dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 1, 2021breach begins
Apr 1, 2022discovered · members disagree
notification delay · 54 days
May 25, 2022first filing
Feb 27, 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. MAY 25WA AGWA AG noticefirst filing · 937 WA residentsday 0
  2. MAY 25ME AGME AG noticestates nationwide total 2,762,687day 0
  3. MAY 25MA AGMA AG notice402 MA residentsday 0
  4. MAY 25MT AGMT AG notice120 MT residentsday 0
  5. MAY 25CA AGCA AG noticeno count statedday 0
  6. MAY 25IN AGIN AG noticestates nationwide total 2,762,687day 0
  7. MAY 25DE AGDE AG noticeno count statedday 0
  8. MAY 25SC AGSC AG notice1,463 SC residentsday 0
  9. MAY 31NH AGNH AG notice101 NH residents+6d
  10. JAN 13VT AGVT AG noticeno count stated+233d
  11. JAN 13DE AGDE AG noticeno count stated+233d
  12. JAN 13CA AGCA AG noticeno count stated+233d
  13. FEB 27OR AGOR AG noticemost recent · states nationwide total 2,762,687+278d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 26, 2022 – Apr 1, 2022
WA AG
Discovered
Apr 1, 2022WA AG + MT AG + CA AG +4Apr 25, 2022ME AG + OR AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
WA AG + ME AG + MT AG +6
Attack vector
Unauthorized Access
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)

2,762,687

Sum of filed state slices

94,566· 3.4% of stated

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

US2,762,687
IN91,389
SC1,463
WA937
MA402
ME154
MT120
NH101

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

278 days

Cadence

~1 / 23.2d

vs. multi-state median

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