DisclosureLens
State AGConfirmed4 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 4 filings

Accelerate Infrastructure Opportunities LLC — September 2025 breach

Clustered 4 filings across 4 jurisdictions · filed May 11, 2026. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

4 filings

States

4

Affected · reported

246

First → last filing

May 11, 2026

Merge confidence

100%

incident inc_68cd602a56dc4364 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe unauthorized access. Intrusion Sep 28, 2025–Oct 2, 2025, discovered Oct 1, 2025 — the first regulatory filing landed 222 days later. 246 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
222days

Discovered → first regulatory filing

Discovery variance
197days

Range of discovered_at dates across filings

Filing span
0days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delayno leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksMaine ME AG ≤30d · 25dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 28, 2025breach begins
Oct 1, 2025discovered · members disagree
notification delay · 222 days
May 11, 2026first filing
watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. MAY 11ME AGME AG noticefirst filing · states nationwide total 246day 0
  2. MAY 11NH AGNH AG notice1 NH residentsday 0
  3. MAY 11NE AGNE AG notice3 NE residentsday 0
  4. MAY 11MA AGMA AG noticemost recent · 2 MA residentsday 0
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 28, 2025Oct 2, 2025
ME AG
Discovered
Oct 1, 2025NH AG + NE AGApr 16, 2026ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PII
ME AG + NH AG + NE AG +1
Attack vector
Unauthorized Access
ME 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)

246

Sum of filed state slices

7· 2.8% of stated

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

US246
NE3
MA2
ME1
NH1

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 filing4 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
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
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

0 days

Cadence

~1 / 0d

vs. multi-state median

20.0× faster

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.