Paylogix
bd_ca3cbddf2cb96e96 · schema v1 · pii pii-v2
Full breach record for Paylogix →Press / market disclosure — not a breach-notification filing
A media or market posting that confirms an incident but carries no breach-notification fields, so compliance clocks aren't assessable. The summary below is extracted from the coverage — verify against the source.
Employee benefits platform Paylogix says hackers stole financial and health. Paylogix: The social benefits management company Paylogix was the victim of a cyberattack. Hackers stole sensitive information, including social security numbers, financial data, health information, and passport numbers, belonging to tens of thousands of people. The incident, which took place between November 13 and 18, was claimed by the ransomware group Akira in January 2026. Linked ransomware group: akira.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Aug 25, 2026
Press report
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Attack → press
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Siteakirabd_9d54362b0b4d6fe92026-01-15 · +222dVerified by operator
Regulatory filings (8) · sorted by filing gap
- South Carolina State AGbd_1bffe30fdb8208af2026-08-17 · +8dVerified by operator
- New Hampshire State AGbd_14770e2c01c0cb1f2026-08-14 · +11dVerified by operator
- Washington State AGbd_1f94d81f89d6c69f2026-08-14 · +11dVerified
- Vermont State AGbd_6e73b080f999ee562026-08-14 · +11dVerified by operator
Show 4 more filings ↓Show fewer ↑up to 24d gap
- Oregon State AGbd_9650736cc75dc07f2026-08-14 · +11dVerified
- California State AGbd_fb2ce99e0269730f2026-08-14 · +11dVerified by operator
- Massachusetts State AGbd_1cbe760a7baf97602026-08-01 · +24dVerified by operator
- Illinois State AGbd_ac2e39236975ec002026-08-01 · +24dVerified
Filing propagation · 9 filings · 8 states
View merged incident ↗Pattern: first filing Aug 1 (MA), last Aug 25 — a 24-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.
Source ceiling
- incident type + narrative only (may be machine-translated)
- discovery date
- materiality
- affected count
- data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
akira
According to ransomware.live, The Akira ransomware group is said to have emerged in March 2023, and there's much speculation about its ties to the former CONTI ransomware group. It's worth noting that with the end of CONTI's operation, several affiliates migrated to independent campaigns such as Royal, BlackBasta, and others. According to some reports, Akira affiliates also work with other ransomware operations, such as Snatch and BlackByte, as an open directory of tools used by an Akira operator was identified, which also had connections to the Snatch ransomware. The first version of the Akira ransomware was written in C++ and appended files with the '.akira' extension, creating a ransom note named 'akira_readme.txt,' partially based on the Conti V2 source code. However, on June 29, 2023, a decryptor for this version was reportedly released by Avast. Subsequently, a version was released that fixed the decryption flaw on July 2, 2023. Since then, the new version is said to be written in Rust, this time called 'megazord.exe,' and it changes the extension to '.powerranges' for encrypted files. Most of Akira's initial access vectors use brute-force attempts on Cisco VPN devices (which use single-factor authentication only). Additionally, exploitation of CVEs: CVE-2019-6693 and CVE-2022-40684 for initial access has been identified. Source: https://github.com/crocodyli/ThreatActors-TTPs