AUTOPAY Direct, Inc.
bd_29d55959bdbcd925 · schema v1 · pii pii-v1
Full breach record for AUTOPAY Direct, Inc. →2 incidents on fileAUTOPAY Direct, Inc. experienced a ransomware attack where a threat actor infiltrated its network and exfiltrated personally identifiable information (PII) of customers from February 2 to February 3, 2022. The company discovered the incident on February 5, 2022, when the actor demanded ransom. AUTOPAY did not pay the ransom, terminated unauthorized access, and engaged forensic investigators. Remediation included implementing MFA and enhanced security controls. Affected individuals were offered 12 months of Experian IdentityWorks.
J jump to incidentP pin to compareR raw source
Incident timeline
Feb 2, 2022
Begins
Feb 5, 2022
Discovered
Apr 26, 2022
Filed
vs. sector median
+2 wks slower
Linked disclosures
Why this link?Regulatory filings (7) · sorted by filing gap
- New Hampshire State AGbd_07d252a1f53fa0562022-04-18 · +8dVerified
- Washington State AGbd_27c3947e62aa6b162022-04-14 · +12dVerified
- South Carolina State AGbd_2c0e299e2e7ca1b02022-04-14 · +12dVerified
- Maine State AGbd_702f47d2350c448f2022-04-14 · +12dVerified
Show 3 more filings ↓Show fewer ↑up to 115d gap
- Indiana State AGbd_e1528908ef61677d2022-04-11 · +15dVerified
- Montana State AGbd_d2c472e50e8656412022-03-31 · +26dVerified
- Illinois State AGbd_2e2021ad759667742022-01-01 · +115dCandidate
Filing propagation · 8 filings · 8 states
View merged incident ↗Pattern: first filing Jan 1 (IL), last Apr 26 (CA) — a 115-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.