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

Alaska Air Group Federal Credit Union — March 2026 breach

Clustered 9 filings across 9 jurisdictions · filing window Apr 16, 2026 → Apr 17, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

10,705

First → last filing

Apr 16, 2026 → Apr 17, 2026

Merge confidence

100%

incident inc_6e1ce24548504091 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe a third-party compromise. Intrusion Mar 5, 2026–Mar 9, 2026, discovered Mar 5, 2026 — the first regulatory filing landed 42 days later. 10,705 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
42days

Discovered → first regulatory filing

Discovery variance
4days

Range of discovered_at dates across filings

Filing span
1days

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 clocksMaine⏱ ME AG >30d · 39dWashington⏱ WA AG >30dOregon✓ OR AG ≤45dCalifornia✓ CA AG copy ≤15d · 1dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 5, 2026breach begins
Mar 5, 2026discovered · members disagree
notification delay · 42 days
Apr 16, 2026first filing
Apr 17, 2026most 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. APR 16IN AGIN AG noticefirst filing · states nationwide total 10,705day 0
  2. APR 16MT AGMT AG notice86 MT residentsday 0
  3. APR 16NH AGNH AG notice4 NH residentsday 0
  4. APR 17VT AGVT AG notice1 VT residents+1d
  5. APR 17ME AGME AG noticestates nationwide total 10,705+1d
  6. APR 17OR AGOR AG noticestates nationwide total 10,705+1d
  7. APR 17WA AGWA AG notice5,092 WA residents+1d
  8. APR 17MA AGMA AG notice22 MA residents+1d
  9. APR 17CA AGCA AG noticemost recent · no count stated+1d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 5, 2026
IN AG
Discovered
Mar 5, 2026OR AG + WA AGMar 9, 2026ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PCI · PII
MT AG + NH AG + VT AG +4
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.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

10,705

Sum of filed state slices

5,232· 48.9% of stated

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

US10,705
WA5,092
MT86
MA22
IN19
ME8
NH4
VT1

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

1 days

Cadence

~1 / 0.1d

vs. multi-state median

8.0× faster

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.