DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed14 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 14 filings

Networking Technology, Inc. — March 2026 breach

Clustered 14 filings across 11 jurisdictions · filing window May 1, 2026 → Jun 15, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

14 filings

States

11

Affected · reported

353,844

First → last filing

May 1, 2026 → Jun 15, 2026

Merge confidence

100%

incident inc_fa789a0b04e0457d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 14 regulatory filings. The filings describe unauthorized access. Intrusion Mar 1, 2026–Mar 3, 2026, discovered Mar 3, 2026 — the first regulatory filing landed 59 days later (flagged late). 353,844 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 1 more. Notifications rolled out on a 45-day schedule across 14 filings beginning May 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
59days

Discovered → first regulatory filing

Discovery variance
59days

Range of discovered_at dates across filings

Filing span
45days

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 · 59dOregon✗ OR AG >45dMassachusetts⏱ MA AG >30dHIPAA✓ HHS notifiedSouth Carolina✓ SC CRA notice dueTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 1, 2026breach begins
Mar 3, 2026discovered · members disagree
notification delay · 59 days
May 1, 2026first filing
Jun 15, 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. MAY 1IL AGIL AG noticefirst filing · no count statedday 0
  2. MAY 28NE AGNE AG notice5,645 NE residents+27d
  3. MAY 29HHS OCRHHS OCR noticestates nationwide total 353,844+28d
  4. MAY 29SC AGSC AG notice11,442 SC residents+28d
  5. MAY 29CA AGCA AG noticeno count stated+28d
  6. MAY 29TX AGTX AG noticestates nationwide total 65,795+28d
  7. MAY 29VT AGVT AG notice5 VT residents+28d
  8. MAY 29WA AGWA AG notice5,671 WA residents+28d
  9. MAY 29MA AGMA AG notice1,183 MA residents+28d
  10. MAY 29NH AGNH AG notice3,634 NH residents+28d
  11. MAY 29OR AGOR AG noticestates nationwide total 7,794+28d
  12. MAY 29WA AGWA AG notice1,215 WA residents+28d
  13. JUN 15CA AGCA AG noticeno count stated+45d
  14. JUN 15VT AGVT AG noticemost recent · 8 VT residents+45d
  15. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 1, 2026 – Mar 3, 2026
NE AG
Discovered
Mar 3, 2026NE AG + SC AG + CA AG +4May 1, 2026IL AG + TX AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI
IL AG + NE AG + HHS OCR +7
Attack vector
Unauthorized Access
NE 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)

353,844

Sum of filed state slices

76,921· 21.7% of stated

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

US353,844
TX49,338
SC11,442
WA5,671
NE5,645
NH3,634
MA1,183
VT8

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

45 days

Cadence

~1 / 3.5d

vs. multi-state median

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