Networking Technology, Inc. — March 2026 breach
Clustered 17 filings across 12 jurisdictions · filing window May 29, 2026 → Oct 20, 2026 (dated filings only). View entity profile → Other incidents for this victim →
incident inc_fa789a0b04e0457d · merged by human · confidence 100%
Litigation Timing
SupplementalRange of discovered_at dates across filings
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.
Sensitive data
identity_governmentIncident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.
Member cascade — every filing about this breach
- MAY 1IL AGIL AG noticefiling day not on record · no count stated—
- MAY 28NE AGNE AG noticefiling day not on record · 5,645 NE residentsauto-linked—
- MAY 29HHS OCRHHS OCR noticefirst filing · states nationwide total 353,844auto-linkedday 0
- MAY 29SC AGSC AG notice11,442 SC residentsauto-linkedday 0
- MAY 29CA AGCA AG noticeno count statedauto-linkedday 0
- MAY 29TX AGTX AG noticestates nationwide total 65,795auto-linkedday 0
- MAY 29VT AGVT AG notice5 VT residentsauto-linkedday 0
- MAY 29OR AGOR AG noticestates nationwide total 7,794auto-linkedday 0
- MAY 29WA AGWA AG notice1,215 WA residentsauto-linkedday 0
- MAY 29WA AGWA AG notice5,671 WA residentsauto-linkedday 0
- MAY 29MA AGMA AG notice1,183 MA residentsauto-linkedday 0
- MAY 29MT AGMT AG notice3,120 MT residentsauto-linkedday 0
- MAY 29NH AGNH AG notice3,634 NH residentsauto-linkedday 0
- JUN 15VT AGVT AG notice8 VT residentsauto-linked+17d
- JUN 15CA AGCA AG noticeno count statedauto-linked+17d
- OCT 20VT AGVT AG notice14 VT residentsoperator-confirmed+144d
- OCT 20NH AGNH AG noticemost recent · 3,763 NH residentsoperator-confirmed+144d
- 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 +5May 1, 2026IL AG + TX AGfilings disagree on discovery
- Data types
- Health (basic) · Identity (basic) · Government ID · PHI IL AG + NE AG + HHS OCR +8
- 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
80,176· 22.7% of stated
77% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
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
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
Merge provenance
- Method
- human
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Reviewed
- operator-reviewed Oct 21, 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
144 days
Cadence
~1 / 10.3d
vs. multi-state median
24.0× 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.