DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed11 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedqilinhigh sensitivity
Merged incident · 11 filings

Ahtna Incorporated — April 2025 breach

Clustered 11 filings across 9 jurisdictions · filing window Jul 28, 2025 → Feb 20, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

8

Affected · reported

8,631

First → last filing

Jul 28, 2025 → Feb 20, 2026

Merge confidence

100%

incident inc_ade72258e90445ac · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Apr 20, 2025–Jun 1, 2025, discovered Jul 28, 2025 — the first regulatory filing landed 116 days later (flagged late). 8,631 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 207-day schedule across 9 filings beginning Jul 28, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
116days

Discovered → first regulatory filing

Discovery variance
86days

Range of discovered_at dates across filings

Leak precedence
116days 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
207days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMaine✗ ME AG >90d · 116dVermont✗ VT AG >45 bdayCalifornia✗ CA 60-day late · 176dTexas✗ TX AG >30dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 20, 2025breach begins
Jul 28, 2025discovered · members disagree
notification delay · 116 days
Nov 21, 2025first filing
Feb 20, 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. JUL 28Leak siteqilin postfirst filing · attacker claim · unverifiedday 0
  2. AUG 12Leak siteqilin postattacker claim · unverified+15d
  3. NOV 21ME AGME AG noticestates nationwide total 8,341+116d
  4. NOV 21IN AGIN AG noticestates nationwide total 8,341+116d
  5. NOV 21NE AGNE AG notice3 NE residents+116d
  6. NOV 21MA AGMA AG notice32 MA residents+116d
  7. NOV 21VT AGVT AG noticeno count stated+116d
  8. NOV 21CA AGCA AG noticeno count stated+116d
  9. NOV 21NH AGNH AG notice2 NH residents+116d
  10. FEB 19CA AGCA AG noticeno count stated+206d
  11. FEB 20TX AGTX AG noticemost recent · states nationwide total 8,631+207d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 20, 2025 – Jun 1, 2025
ME AG
Discovered
Jul 28, 2025ME AG + NE AG + VT AG +2Oct 22, 2025TX AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
ME AG + NE AG + VT AG +4
Attack vector
Unauthorized Access
ME 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)

8,631

Sum of filed state slices

1,902· 22.0% of stated

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

US8,631
TX1,855
MA32
IN9
NE3
NH2
ME1

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

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

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

207 days

Cadence

~1 / 20.7d

vs. multi-state median

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