DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed9 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedblack_bastahigh sensitivity
Merged incident · 9 filings

PRGX Global Inc. — April 2022 breach

Clustered 9 filings across 9 jurisdictions · filing window May 2, 2022 → May 15, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

8

Affected · reported

13,231

First → last filing

May 2, 2022 → May 15, 2023

Merge confidence

100%

incident inc_513739ef73b246f6 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Apr 8, 2022–Apr 9, 2022, discovered Apr 8, 2022 — the first regulatory filing landed 268 days later (flagged late). 13,231 individuals reported across the linked filings. Data reported: Government ID, Financial account, PCI, and 3 more. Notifications rolled out on a 378-day schedule across 8 filings beginning May 2, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
268days

Discovered → first regulatory filing

Discovery variance
187days

Range of discovered_at dates across filings

Leak precedence
244days 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
378days

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 >180dVermont✗ VT AG >45 bdayCalifornia✗ CA 60-day late · 391dMaine✗ ME AG >90d · 208dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Apr 8, 2022breach begins
Apr 8, 2022discovered · members disagree
notification delay · 268 days
Jan 1, 2023first filing
May 15, 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

  1. MAY 2Leak siteblack_basta postfirst filing · attacker claim · unverifiedday 0
  2. JAN 1IL AGIL AG noticeno count stated+244d
  3. MAY 8MA AGMA AG notice90 MA residents+371d
  4. MAY 8VT AGVT AG noticeno count stated+371d
  5. MAY 8CA AGCA AG noticeno count stated+371d
  6. MAY 8IN AGIN AG noticestates nationwide total 13,231+371d
  7. MAY 8MT AGMT AG notice2 MT residents+371d
  8. MAY 8ME AGME AG noticestates nationwide total 13,231+371d
  9. MAY 15NH AGNH AG noticemost recent · 26 NH residents+378d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 8, 2022 – Apr 9, 2022
VT AG
Discovered
Apr 8, 2022IL AGApr 9, 2022VT AG + CA AG + MT AG +1Oct 12, 2022ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · Government ID · PCI · PII
MA AG + ME AG + VT AG +3
Attack vector
Unauthorized Access
VT 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)

13,231

Sum of filed state slices

234· 1.8% of stated

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

US13,231
IN106
MA90
NH26
ME10
MT2

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 filing8 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
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

378 days

Cadence

~1 / 47.3d

vs. multi-state median

47.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.