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

Alogent — May 2023 breach

Clustered 10 records across 8 jurisdictions: 9 filings and 1 leak-site claim · filing window Jul 12, 2023 → Sep 26, 2023 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

10 records

States

8

Affected · reported

4,548,250

First → last dated filing

Jul 12, 2023 → Sep 26, 2023

Merge confidence

100%

incident inc_a644c475efb64b42 · merged by human · confidence 100%

Part of the Progress Software Corporation supply-chain incident (2023) — at least 96 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. The filings describe hacking. Intrusion May 30, 2023–Jun 15, 2023, discovered May 31, 2023. 4,548,250 individuals reported across the linked filings. Data reported: PII, Financial account, Identity (basic), and 1 more. Notifications rolled out on a 76-day schedule across 8 dated filings beginning Jul 12, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
0days

Range of discovered_at dates across filings

Filing span
76days

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 clocksMaine✗ ME AG >90d · 92dOregon✗ OR AG >45dWashington⏱ WA AG >30dLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

May 30, 2023breach begins
May 31, 2023discovered
Jul 12, 2023first dated filing
Sep 26, 2023most recent dated filing

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. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JUL 12DE AGDE AG noticefirst filing · no count statedday 0
  3. JUL 26Leak sitecl0p postattacker claim · unverified+14d
  4. AUG 14IN AGIN AG noticestates nationwide total 4,543,850+33d
  5. AUG 18MT AGMT AG notice400 MT residents+37d
  6. AUG 22WA AGWA AG notice4,000 WA residents+41d
  7. AUG 29ME AGME AG notice4,543,850 affected+48d
  8. AUG 31ME AGME AG notice4,543,850 affected+50d
  9. SEP 18OR AGOR AG noticeno count stated+68d
  10. SEP 26CA AGCA AG noticemost recent · no count stated+76d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 30, 2023 – Jun 15, 2023
DE AG
Discovered
May 31, 2023· 1d undetected
IL AG + WA AG + ME AG +1
Data types
Financial account · Financial credentials · Identity (basic) · PII
DE AG + MT AG + WA AG +2
Attack vector
Misconfiguration
DE 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)

4,543,850

Sum of filed state slices

6,727· 0.1% of stated

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

US4,543,850
WA4,000
IN2,327
MT400

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 Aug 25, 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

76 days

Cadence

~1 / 10.9d

vs. multi-state median

15.2× slower

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.