Payactiv
bd_384bdccd7645f4e1 · schema v1 · pii pii-v1
Full breach record for Payactiv →Payactiv, Inc. disclosed a cybersecurity incident affecting 18,085 Washington residents. Unauthorized access occurred between April 3 and August 20, 2025. Payactiv discovered the incident on August 19, 2025, and began notifying residents on September 29, 2025. Compromised data included names, dates of birth, and Social Security numbers. Payactiv engaged third-party experts, notified law enforcement, and offered one year of credit monitoring.
J jump to incidentP pin to compareR raw source
Incident timeline
Apr 3, 2025
Begins
Aug 19, 2025
Discovered
Oct 11, 2025
Filed
vs. sector median
2 wks faster
Linked disclosures
Why this link?Regulatory filings (10) · sorted by filing gap
- Oregon State AGbd_3ce26a4c298b1b782025-10-11Verified by operator
- Massachusetts State AGbd_8be66137203225392025-10-11Verified
- Maine State AGbd_cba3b5443bba44b32025-10-11Verified by operator
- California State AGbd_f8b2d1de52f6d8942025-10-11Verified
Show 6 more filings ↓Show fewer ↑up to 88d gap
- Vermont State AGbd_3157c62a8df34b922025-09-30 · +11dVerified
- Nebraska State AGbd_6126269966c2978a2025-09-29 · +12dVerified
- New Hampshire State AGbd_7e085442c1731a302025-09-29 · +12dVerified
- Montana State AGbd_e3ea6aa0a8094db52025-09-29 · +12dCandidate
- Indiana State AGbd_69970be9b9ebe3362025-09-25 · +16dVerified
- Texas State AGbd_e018df5178963fbc2026-01-07 · +88dVerified
Filing propagation · 11 filings · 11 states
View merged incident ↗Pattern: first filing Sep 25 (IN), last Jan 7 (TX) — a 104-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.