DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed6 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcl0phigh sensitivity
Merged incident · 6 filings

Paycom Payroll, LLC — May 2023 breach

Clustered 6 filings across 5 jurisdictions · filing window Jul 13, 2023 → Jul 10, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

4

Affected · reported

7,449

First → last filing

Jul 13, 2023 → Jul 10, 2024

Merge confidence

100%

incident inc_cb5be280a8414bd1 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion May 28, 2023–Jun 2, 2023, discovered Jun 2, 2023 — the first regulatory filing landed 59 days later (flagged late). 7,449 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 363-day schedule across 5 filings beginning Jul 13, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
59days

Discovered → first regulatory filing

Discovery variance
41days

Range of discovered_at dates across filings

Leak precedence
18days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
363days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dMaine✓ ME AG ≤30d · 18dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 28, 2023breach begins
Jun 2, 2023discovered · members disagree
notification delay · 59 days
Jul 31, 2023first filing
Jul 10, 2024most recent filing

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

Member cascade — every filing about this breach

  1. JUL 13Leak sitecl0p postfirst filing · attacker claim · unverifiedday 0
  2. JUL 31ME AGME AG noticestates nationwide total 7,449+18d
  3. JUL 31MA AGMA AG notice10 MA residents+18d
  4. JUL 31IN AGIN AG noticestates nationwide total 7,449+18d
  5. JUL 31MT AGMT AG notice1 MT residents+18d
  6. JUL 10MA AGMA AG noticemost recent · 4 MA residents+363d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 28, 2023 – Jun 2, 2023
ME AG
Discovered
Jun 2, 2023MT AGJul 13, 2023ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID
ME AG + MA AG + MT AG
Attack vector
Unauthorized Access
ME 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)

7,449

Sum of filed state slices

44· 0.6% of stated

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

US7,449
IN31
MA10
ME2
MT1

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 filing5 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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 22, 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

363 days

Cadence

~1 / 72.6d

vs. multi-state median

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