DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed6 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcactushigh sensitivity
Merged incident · 6 filings

American Meteorological Society, Inc. — April 2023 breach

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

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

5

Affected · reported

557

First → last filing

Jul 20, 2023 → Dec 15, 2023

Merge confidence

100%

incident inc_15aa0eed7a1740a3 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Apr 1, 2023–Aug 9, 2023, discovered Apr 1, 2023 — the first regulatory filing landed 257 days later (flagged late). 557 individuals reported across the linked filings. Data reported: Government ID, Financial account, PII, and 1 more. Notifications rolled out on a 148-day schedule across 5 filings beginning Jul 20, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
257days

Discovered → first regulatory filing

Discovery variance
248days

Range of discovered_at dates across filings

Leak precedence
147days 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
148days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 128dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 1, 2023breach begins
Apr 1, 2023discovered · members disagree
notification delay · 257 days
Dec 14, 2023first filing
Dec 15, 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 20Leak sitecactus postfirst filing · attacker claim · unverifiedday 0
  2. DEC 14MA AGMA AG notice231 MA residents+147d
  3. DEC 14VT AGVT AG noticeno count stated+147d
  4. DEC 14NH AGNH AG notice18 NH residents+147d
  5. DEC 14MT AGMT AG notice2 MT residents+147d
  6. DEC 15ME AGME AG noticemost recent · states nationwide total 557+148d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 20, 2023
NH AG
Discovered
Apr 1, 2023VT AGApr 24, 2023NH AGAug 9, 2023ME AGDec 5, 2023MT AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
MA AG + ME AG + VT AG +2
Attack vector
Unauthorized Access
VT 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)

557

Sum of filed state slices

256· 46.0% of stated

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

US557
MA231
NH18
ME5
MT2

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 report

No press coverage linked yet.

State AG / regulator filing5 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 Aug 23, 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

148 days

Cadence

~1 / 29.6d

vs. multi-state median

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