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

Alexion Pharmaceuticals, Inc — February 2024 breach

Clustered 5 filings across 3 jurisdictions · filing window May 13, 2024 → May 20, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

5 filings

States

3

Affected · reported

not comparable

First → last filing

May 13, 2024 → May 20, 2024

Merge confidence

100%

incident inc_00188429fa1e459c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe hacking. Intrusion Feb 8, 2024, discovered Feb 12, 2024 — the first regulatory filing landed 91 days later. Data reported: Identity (basic), PII, Health (basic), and 1 more. Notifications rolled out on a 7-day schedule across 5 filings beginning May 13, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
91days

Discovered → first regulatory filing

Discovery variance
64days

Range of discovered_at dates across filings

Filing span
7days

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 >14 bdayFull clock table in Litigation Timeline

Incident timeline

Feb 8, 2024breach begins
Feb 12, 2024discovered · members disagree
notification delay · 91 days
May 13, 2024first filing
May 20, 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 13MT AGMT AG noticefirst filing · 2 MT residentsday 0
  2. MAY 14VT AGVT AG noticeno count stated+1d
  3. MAY 20VT AGVT AG noticeno count stated+7d
  4. MAY 20MT AGMT AG notice4 MT residents+7d
  5. MAY 20IN AGIN AG noticemost recent · 29 IN residents+7d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 8, 2024
MT AG
Discovered
Feb 12, 2024MT AGFeb 21, 2024MT AGApr 16, 2024VT AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · PHI · PII
MT AG + VT AG
Attack vector
Third-Party / Supply Chain
MT AG

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

7 days

Cadence

~1 / 1.8d

vs. multi-state median

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