All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed2 filings · 2 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 2 filings

Progress Software Corporation — May 2023 breach

Clustered 2 filings across 2 jurisdictions · filing window Jun 5, 2023 → Aug 18, 2023. View entity profile → Other incidents for this victim →

Agreement not assessableMerge100%

Determination

Confirmed

Members

2 filings

States

Affected · reported

First → last filing

Jun 5, 2023 → Aug 18, 2023

Merge confidence

100%

incident inc_fd2a399493a34af2 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filings describe hacking. Intrusion May 29, 2023–May 30, 2023, discovered May 28, 2023 — the first regulatory filing landed 8 days later. 1 individual reported across the linked filings. Data reported: Government ID and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

8days

Discovered → first regulatory filing

Filing span

74days

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; needs two dated filings.

Sensitive data

identity_government

Incident timeline

May 29, 2023breach begins

May 28, 2023discovered

notification delay · 8 days

Jun 5, 2023first filing

Aug 18, 2023most recent filing

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

Member cascade — every filing about this breach

JUN 5SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
AUG 18MT AGMT AG noticemost recent · 1 MT residentsauto-linked+74d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: May 29, 2023 – May 30, 2023
Discovered: May 28, 2023
Data types: Identity (basic) · Government ID
Attack vector: Unauthorized Access

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

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

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement1 member

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Merge provenance

Method: deterministic
Confidence: 1.00 · above the 0.85 auto-merge floor
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

74 days

vs. multi-state median

9.3× 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.