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

Zeroed-In Technologies, LLC — August 2023 breach

Clustered 12 filings across 11 jurisdictions · filing window Jan 1, 2023 → Jul 28, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

11

Affected · reported

1,977,486

First → last filing

Jan 1, 2023 → Jul 28, 2024

Merge confidence

100%

incident inc_6f8f58f2b86242c4 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. Intrusion Aug 7, 2023–Aug 8, 2023, discovered Aug 7, 2023. 1,977,486 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 574-day schedule across 12 filings beginning Jan 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
24days

Range of discovered_at dates across filings

Filing span
574days

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 clocksWashington✗ WA AG >90dCalifornia✗ CA 60-day late · 85dOregon✗ OR AG >45dMaine✗ ME AG >90d · 355dVermont✗ VT AG >45 bdayMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 7, 2023breach begins
Aug 7, 2023discovered · members disagree
Jan 1, 2023first filing
Jul 28, 2024most 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. NOV 27WA AGWA AG notice61,088 WA residents+330d
  3. NOV 27MA AGMA AG notice27,889 MA residents+330d
  4. NOV 27CA AGCA AG noticeno count stated+330d
  5. NOV 27OR AGOR AG noticestates nationwide total 1,977,486+330d
  6. NOV 27NH AGNH AG notice5,828 NH residents+330d
  7. NOV 27ME AGME AG noticestates nationwide total 1,977,486+330d
  8. NOV 27VT AGVT AG noticeno count stated+330d
  9. NOV 27MT AGMT AG notice5,049 MT residents+330d
  10. NOV 27DE AGDE AG noticeno count stated+330d
  11. NOV 28SC AGSC AG noticeno count stated+331d
  12. JUL 28ME AGME AG noticemost recent · no count stated+574d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 7, 2023 – Aug 8, 2023
WA AG
Discovered
Aug 7, 2023IL AGAug 8, 2023WA AG + CA AG + VT AG +4Aug 31, 2023OR AG + ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID
WA AG + CA AG + NH AG +6
Attack vector
Ransomware
WA 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)

1,977,486

Sum of filed state slices

106,888· 5.4% of stated

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

US1,977,486
WA61,088
MA27,889
ME7,034
NH5,828
MT5,049

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

574 days

Cadence

~1 / 52.2d

vs. multi-state median

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