DisclosureLens
GLOBALUnknownRansomwareAkiraLow

Paylogix

bd_ca3cbddf2cb96e96 · schema v1 · pii pii-v2

Severity

Low

Discovered

—

Filed

Aug 25, 2026

To disclose

—

Affected

Not disclosed

Linked

13 records

Confidence

60%
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.

Incident timeline — mostly unverified

? — ?

Breach window unknown

Aug 25, 2026

Press report

—

Corroborated · see linked filings

This record's own dates cannot anchor compliance clocks; see the linked filings.

Attack → press

—

Compliance clock

Not assessable

This press report is one of 13 records about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (10) · sorted by filing gap

Show 6 more filings ↓up to 24d gap

Showing first 10 of 12 linked disclosures.

Filing propagation · 10 filings · 10 states

View merged incident ↗

Pattern: first filing Aug 1 (MA), last Sep 18 (NY) — a 48-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Cascade drawn from the first 10 linked disclosures of 12 — the full spread may be wider.

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market reportThis record

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

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.

About this groupFirst seen 2023-04-12

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

1,853 tracked hereFull profile →