Confirmed breach. Intrusion Jan 17, 2026, discovered Mar 26, 2026 — the first regulatory filing landed 70 days later. 1 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksMaine⏱ ME AG >30d · 70dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Affected (total reported)
1
Data types
1
Identity (basic)
Jurisdictions
1
ME
Linked filings
1
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jan 17, 2026
When the intrusion reportedly occurred, per the linked filings
Asplundh Engineering Services, LLC reported an external system breach (hacking) occurring on January 17, 2026, discovered on March 26, 2026. The incident affected 1 Maine resident. The company provided written notification on June 4, 2026, and offered 12 months of credit monitoring and identity protection services through TransUnion.
Affected (this filing): 1
ME AG >30d · 70dME resident >60d · 70d
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.