PAREXEL INTERNATIONAL, INC. — August 2025 breach

Clustered 10 filings across 10 jurisdictions · filing window Dec 1, 2025 → Dec 17, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

Affected · reported

65,587

First → last filing

Dec 1, 2025 → Dec 17, 2025

Merge confidence

100%

incident inc_e95f2d81e5e844b4 · merged by deterministic · confidence 100%

Part of the ORACLE CORPORATION supply-chain incident (2025) — at least 7 organizations filed notifications naming this third party.

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe hacking. Intrusion Aug 9, 2025–Oct 5, 2025, discovered Oct 4, 2025 — the first regulatory filing landed 58 days later (flagged late). 65,587 individuals reported across the linked filings. Data reported: Government ID, Financial account, PCI, and 3 more. Notifications rolled out on a 16-day schedule across 10 filings beginning Dec 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

58days

Discovered → first regulatory filing

Discovery variance

47days

Range of discovered_at dates across filings

Filing span

16days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont✗ VT AG >45 bdayMaine⏱ ME AG >30d · 74dMassachusetts✓ MA credit monitoring dueTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

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.