Confirmed breach. Intrusion Sep 28, 2025–Oct 2, 2025, discovered Apr 16, 2026 — the first regulatory filing landed 15 days later. 246 individuals reported across the linked filings.
incident inc_68cd602a56dc4364 · merge_method human · confidence 100%
Litigation Timing
Notification delay
15days
Discovered → first regulatory filing
Filing span
10days
Time between earliest and latest filing
Not recorded for this incident
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 · 25dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
246
Data types
3
Identity (basic) · Government ID · Financial account
Jurisdictions
2
MA ME
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Sep 28, 2025 → Oct 2, 2025
When the intrusion reportedly occurred, per the linked filings
Accelerate Infrastructure Opportunities LLC notified Massachusetts residents of a cybersecurity incident involving personal information. The company engaged federal law enforcement and offered 24 months of credit monitoring via Cyberscout/TransUnion. Specific attack details were withheld due to Massachusetts law requirements.
🦞Maine State AGMost recentlinked via operator-confirmed · 100%
Accelerate Infrastructure Opportunities LLC reported an external system breach (hacking) occurring between September 28 and October 2, 2025, discovered on April 16, 2026. The incident affected 246 individuals, including one Maine resident. The company provided written notification and offered 12 months of identity theft and credit monitoring services through Transunion.
Affected (this filing): 246
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.