DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed11 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 11 filings

Progrexion ASG, Inc. — March 2021 breach

Clustered 11 filings across 10 jurisdictions · filing window May 12, 2021 → Jul 12, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 filings

States

10

Affected · reported

13,133

First → last filing

May 12, 2021 → Jul 12, 2021

Merge confidence

100%

incident inc_38cb4047c5ad4b1f · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Mar 3, 2021–Apr 22, 2021, discovered Apr 8, 2021 — the first regulatory filing landed 34 days later (flagged late). 13,133 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Notifications rolled out on a 61-day schedule across 11 filings beginning May 12, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
34days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
61days

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 clocksOregon✗ OR AG >45dMaine✗ ME AG >90d · 95dWashington⏱ WA AG >30dFull clock table in Litigation Timeline

Sensitive data

authenticationfinancial_credentialsidentity_government

Incident timeline

Mar 3, 2021breach begins
Apr 8, 2021discovered
notification delay · 34 days
May 12, 2021first filing
Jul 12, 2021most 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 12ID AGID AG noticefirst filing · no count statedday 0
  2. MAY 26OR AGOR AG noticeno count stated+14d
  3. JUN 8ID AGID AG notice30 ID residents+27d
  4. JUN 8SC AGSC AG notice363 SC residents+27d
  5. JUN 8WA AGWA AG notice150 WA residents+27d
  6. JUN 9NH AGNH AG notice3 NH residents+28d
  7. JUN 9MA AGMA AG notice26 MA residents+28d
  8. JUN 9CA AGCA AG noticeno count stated+28d
  9. JUN 16IN AGIN AG noticestates nationwide total 13,133+35d
  10. JUN 16DE AGDE AG noticeno count stated+35d
  11. JUL 12ME AGME AG noticemost recent · states nationwide total 13,133+61d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 5, 2021
OR AG
Discovered
Apr 8, 2021· 34d undetected
ID AG + OR AG + SC AG +5
Data types
Authentication · Financial account · Financial credentials · Identity (basic) · Government ID · PII
ID AG + NH AG + WA AG +5
Attack vector
Unauthorized Access
ID 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,133

Sum of filed state slices

861· 6.6% of stated

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

US13,133
SC363
IN286
WA150
ID30
MA26
NH3
ME3

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing11 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

61 days

Cadence

~1 / 6.1d

vs. multi-state median

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