Fieldtex Products Inc.
bd_3ceb6f5bbeac9dfb · schema v1 · pii pii-v1
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
Fieldtex is a manufacturer known as Fieldtex Cases that produces soft sided carrying cases for portable electronic equipment for m edical and military markets. Their second division is a medical s upplies distributor known as Fieldtex Medical. We will upload more than 14gb of corporate documents soon. Employ ee and customer, financials, confidential files, lots etc.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Nov 5, 2025
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_a1286c4eb277f0012025-08-19 · +78dVerified by operator
Regulatory filings (9) · sorted by filing gap
- HHS OCRbd_93b1e15b2201280f2025-11-20 · +15dVerified
- Illinois State AGbd_7efb42a3d2f81dfc2025-12-01 · +26dCandidate
- HHS OCRbd_1b7f2ba67e9a31d72025-12-03 · +28dVerified
- HHS OCRbd_1e4d9a58484d12832025-12-03 · +28dVerified
Show 5 more filings ↓Show fewer ↑up to 49d gap
- HHS OCRbd_43582e2576b7f7672025-12-03 · +28dVerified
- South Carolina State AGbd_57a74a9d0041b14f2025-12-04 · +29dVerified
- HHS OCRbd_06b768e5b5dd17ab2025-12-12 · +37dVerified
- Texas State AGbd_6464020d0158e5732025-12-17 · +42dVerified
- Massachusetts State AGbd_add23d3e22ad7f552025-12-24 · +49dVerified
Showing first 10 of 11 linked disclosures.
Filing propagation · 10 filings · 5 states
View merged incident ↗Pattern: first filing Nov 5, last Dec 24 (MA) — a 49-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 11 — the full spread may be wider.
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