GLOBALClaimed by PlayFirst sightinglinked via operator-confirmed · 100%
Posted to leak site Jun 22, 2023bd_b510a483252a5f3c
Pennsylvania, USA
Clustered 3 filings across 3 jurisdictions · filing window Jun 22, 2023 → Nov 9, 2023. View entity profile → Other incidents for this victim →
incident inc_3ea4abf3879e4813 · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
Identity (basic) · Government ID
CA VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 23, 2023 → Jun 10, 2023
When the intrusion reportedly occurred, per the linked filings
Jun 10, 2023
Reported by VERMONT AG, CALIFORNIA AG filings
Pennsylvania, USA
Hill International, Inc. notified consumers of a data breach where an unauthorized actor accessed the network and removed files between March 23 and June 10, 2023. Exposed data included names, dates of birth, passport numbers, SSNs, and driver's license info. Hill engaged forensic specialists, notified law enforcement, and provided one year of Kroll identity monitoring services.
Hill International, Inc. disclosed that an unauthorized actor accessed its network and exfiltrated files between March 23, 2023, and June 10, 2023. The company discovered suspicious activity on June 10, 2023. Affected data includes names, dates of birth, Social Security numbers, passport numbers, and driver's license/state ID information. The company engaged forensic specialists, notified law enforcement, and is offering one year of identity monitoring services via Kroll.
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.