DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed10 records · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedblack_bastahigh sensitivity
Merged incident · 10 records

Alliance Solutions Group LLC — May 2022 breach

Clustered 10 records across 9 jurisdictions: 9 filings and 1 leak-site claim · filed Mar 1, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 records

States

9

Affected · reported

119,261

First → last dated filing

Mar 1, 2024

Merge confidence

100%

incident inc_a8906acf44c14963 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. Intrusion May 31, 2022–May 31, 2023, discovered May 31, 2023 — the first regulatory filing landed 275 days later (flagged late). 119,261 individuals reported across the linked filings. Data reported: Government ID, PII, PHI, and 4 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
275days

Discovered → first regulatory filing

Discovery variance
247days

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 delay — no SEC 8-K in this cluster.

Regulatory clocksCalifornia✗ CA 60-day late · 275dVermont✗ VT AG >45 bdayWashington✗ WA AG >90dDate basis✓ Clock withheld · confirmation dateMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 28dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 31, 2022breach begins
May 31, 2023discovered · members disagree
notification delay · 275 days
Mar 1, 2024first dated filing
—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. AUG 17Leak siteblack_basta postfirst record · attacker claim · unverifiedday 0
  2. MAR 1MT AGMT AG notice20 MT residents+197d
  3. MAR 1IN AGIN AG noticestates nationwide total 119,261+197d
  4. MAR 1OR AGOR AG noticestates nationwide total 119,261+197d
  5. MAR 1IL AGIL AG noticefiling day not on record · no count stated—
  6. MAR 1CA AGCA AG noticeno count stated+197d
  7. MAR 1MA AGMA AG notice515 MA residents+197d
  8. MAR 1ME AGME AG noticestates nationwide total 119,261+197d
  9. MAR 1VT AGVT AG noticeno count stated+197d
  10. MAR 1WA AGWA AG noticemost recent · 569 WA residents+197d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 30, 2023
IN AG
Discovered
May 31, 2023MT AG + IL AG + CA AG +2Feb 2, 2024OR AG + ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
MT AG + CA AG + VT AG +3
Attack vector
Unauthorized Access
MT 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)

119,261

Sum of filed state slices

15,607· 13.1% of stated

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

US119,261
ME14,051
WA569
MA515
IN452
MT20

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing9 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 23, 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.