Fox Valley Tax Solutions
bd_d7ca14dc1f1da5ad · schema v1 · pii pii-v1
Full breach record for Fox Valley Tax Solutions →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Akira on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
Fox Valley Tax Solutions is a full-service tax firm located in Saint Charles, Illinois, special izing in personalized tax preparation and strategic planning services. They cater to individual s, businesses, trusts, and estates, offering a range of services including tax consultation, IR S issue resolution, and notary services. We will upload 95gb of corporate data soon. Detailed client personal information (passports, DL s, SSNs, financial information), contracts and agreements, NDAs and other confidential docs.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
May 6, 2026
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Siteakirabd_73eed1ea83a599452026-05-15 · +9dVerified
Regulatory filings (5) · sorted by filing gap
- Illinois State AGbd_1e72d3c23948239f2026-06-01 · +26dVerified by operator
- Massachusetts State AGbd_921f32fca6912e8a2026-06-29 · +54dVerified by operator
- Indiana State AGbd_9e0d1081331eee282026-06-29 · +54dVerified by operator
- Nebraska State AGbd_e05d229bde75394c2026-06-29 · +54dVerified
Show 1 more filing ↓Show fewer ↑up to 54d gap
- New Hampshire State AGbd_e8e3dbc7fb9cd7712026-06-29 · +54dVerified by operator
Filing propagation · 6 filings · 5 states
View merged incident ↗Pattern: first filing May 6, last Jun 29 (NH) — a 54-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
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed 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