Confirmed breach. Intrusion Feb 25, 2026, discovered Feb 25, 2026 — the first regulatory filing landed 126 days later. 3 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 clocksLeak gap⏱ Leak >90dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
3
Data types
—
Jurisdictions
2
NH VT
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Feb 25, 2026
When the intrusion reportedly occurred, per the linked filings
Phoenix Environmental Laboratories, Inc. reported a data breach to the Vermont Attorney General. The breach was reported to the AGO on 2026-07-01. The reporting organization type is Other Commercial. 1 Vermont residents were affected. Categories of data breached: Social Security Numbers, Health Records.
Leak >90d
⛰️New Hampshire State AGMost recentlinked via multistate filing link · 100%
Phoenix Environmental Laboratories, Inc. notified the New Hampshire Attorney General of a data event affecting 3 NH residents. Unauthorized access to files occurred on February 25, 2026, exposing names, SSNs, and insurance info. Notification was sent July 1, 2026, offering 12 months of credit monitoring.
Affected (this filing): 3
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.