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

Tower Administrative Services — February 2026 breach

Clustered 10 filings across 10 jurisdictions · filing window Jun 23, 2026 → Jun 29, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

248,940

First → last filing

Jun 23, 2026 → Jun 29, 2026

Merge confidence

100%

incident inc_a6684c61d9464774 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion Feb 3, 2026–Feb 4, 2026, discovered Feb 4, 2026 — the first regulatory filing landed 139 days later (flagged late). 248,940 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 6-day schedule across 10 filings beginning Jun 23, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
139days

Discovered → first regulatory filing

Discovery variance
105days

Range of discovered_at dates across filings

Filing span
6days

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 clocksCalifornia✗ CA 30-day late · 105dWashington✗ WA AG >90dOregon✗ OR AG >45dSouth Carolina✓ SC CRA notice dueTexas✓ TX CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 3, 2026breach begins
Feb 4, 2026discovered · members disagree
notification delay · 139 days
Jun 23, 2026first filing
Jun 29, 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. JUN 23NE AGNE AG noticefirst filing · no count statedday 0
  2. JUN 23IN AGIN AG noticestates nationwide total 248,940day 0
  3. JUN 25CA AGCA AG noticeno count stated+2d
  4. JUN 26SC AGSC AG notice3,427 SC residents+3d
  5. JUN 26MA AGMA AG notice2,124 MA residents+3d
  6. JUN 26TX AGTX AG noticestates nationwide total 248,940+3d
  7. JUN 26WA AGWA AG notice868 WA residents+3d
  8. JUN 26NH AGNH AG notice627 NH residents+3d
  9. JUN 26VT AGVT AG notice78 VT residents+3d
  10. JUN 29OR AGOR AG noticemost recent · states nationwide total 248,940+6d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 3, 2026
NE AG
Discovered
Feb 4, 2026NE AG + CA AG + SC AG +3May 20, 2026TX AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PCI
NE AG + CA AG + SC AG +5
Attack vector
Unauthorized Access
SC 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)

248,940

Sum of filed state slices

35,406· 14.2% of stated

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

US248,940
TX25,742
SC3,427
IN2,540
MA2,124
WA868
NH627
VT78

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

6 days

Cadence

~1 / 0.7d

vs. multi-state median

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