Confirmed breach. Intrusion Jun 1, 2022, discovered Jun 21, 2022 — the first regulatory filing landed 23 days later. 32 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksMaine✓ ME AG ≤30d · 23dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
32
Data types
2
Identity (basic) · Government ID
Jurisdictions
2
ME NH
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jun 1, 2022
When the intrusion reportedly occurred, per the linked filings
Johnson O'Hare Company, Inc. experienced an external system breach discovered on June 21, 2022. The incident, which occurred on June 1, 2022, compromised the names and Social Security numbers of 798 individuals, including 32 Maine residents. The company offered affected individuals 24 months of identity theft protection services through IDX.
Affected (this filing): 32
ME AG ≤30d · 23d
⛰️New Hampshire State AGMost recentlinked via multistate filing link · 100%
State of New Hampshire Attorney General breach notification filed by Johnson OHare Company, Inc. on July 16, 2022. The provided source document contains only page markers and no substantive breach details, incident description, or data types affected.
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.