GLOBALClaimed by Cl0pFirst sightinglinked via operator-confirmed · 100%
Posted to leak site Jul 13, 2023bd_f8013dcb4ad0be62
Online Payroll Services - HR Payroll Software - Paycom
Clustered 3 filings across 3 jurisdictions · filing window Jul 13, 2023 → Jul 31, 2023. View entity profile → Other incidents for this victim →
incident inc_cb5be280a8414bd1 · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
Government ID · Identity (basic)
ME MT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 28, 2023 → Jun 2, 2023
When the intrusion reportedly occurred, per the linked filings
Jul 13, 2023
Reported by MAINE AG filing
Online Payroll Services - HR Payroll Software - Paycom
Paycom Payroll, LLC reported an external system breach (hacking) occurring between May 28, 2023, and June 2, 2023, discovered on July 13, 2023. The incident affected 7,449 individuals, including 2 Maine residents. Acquired data included names combined with driver's license numbers. Paycom provided 24 months of identity monitoring via Experian and enrolled employees in additional protection benefits.
Affected (this filing): 7,449
Paycom Payroll, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2023-07-31. The breach occurred from 5/28/2023 to 6/2/2023. 1 Montana residents were affected.
Affected (this filing): 1
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.