DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SitePressState AGConfirmed9 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoneymessagehigh sensitivity
Merged incident · 9 filings

Insurance Agency Marketing Services, Inc — March 2024 breach

Clustered 9 filings across 8 jurisdictions · filing window May 16, 2024 → Oct 14, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

7

Affected · reported

71,295

First → last filing

May 16, 2024 → Oct 14, 2024

Merge confidence

100%

incident inc_a4571597bd23467f · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings, 1 press report and 1 unverified claim. The filings describe unauthorized access. Intrusion Mar 1, 2024–May 3, 2024, discovered Apr 26, 2024 — the first regulatory filing landed 42 days later (flagged late). 71,295 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Authentication, and 4 more. Notifications rolled out on a 164-day schedule across 7 filings beginning May 16, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
42days

Discovered → first regulatory filing

Discovery variance
77days

Range of discovered_at dates across filings

Leak precedence
21days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
164days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dOregon✗ OR AG >45dFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Mar 1, 2024breach begins
Apr 26, 2024discovered · members disagree
notification delay · 42 days
Jun 7, 2024first filing
Oct 14, 2024most 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 16Leak sitemoneymessage postfirst filing · attacker claim · unverifiedday 0
  2. JUN 7IN AGIN AG noticestates nationwide total 68,047+21d
  3. SEP 18CA AGCA AG noticeno count stated+124d
  4. SEP 18MT AGMT AG notice283 MT residents+124d
  5. SEP 18WA AGWA AG notice2,013 WA residents+124d
  6. SEP 20WI AGWI AG notice68,219 affected+126d
  7. SEP 25MA AGMA AG notice780 MA residents+131d
  8. OCT 14OR AGOR AG noticemost recent · no count stated+150d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 1, 2024
IN AG
Discovered
Apr 26, 2024WA AGMay 3, 2024MT AGJul 12, 2024OR AGfilings disagree on discovery
Data types
Authentication · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI
CA AG + MT AG + WA AG +2
Attack vector
Unauthorized Access
CA AG

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

Affected residents by state

per-state reported counts

US68,047
WI68,219
WA2,013
IN900
MA780
MT283

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

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report1 member

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing7 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 22, 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

164 days

Cadence

~1 / 20.5d

vs. multi-state median

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