FEDERALItem 8.01 · voluntaryMalwareHealthcareHealthcareRansomwareData EncryptedPHIPIIMediumActive

Akumin Inc.

bd_76bf888838325771 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Oct 11, 2023

Filed

Oct 20, 2023

To disclose

9 days

Affected

Not disclosed

Linked

4 records

Confidence

65%

Full breach record for Akumin Inc. →

Akumin Inc. disclosed that it determined on October 11, 2023 that its IT network was affected by ransomware. The attacker likely accessed files containing personal data and Protected Health Information (PHI). Akumin secured networks, engaged cybersecurity counsel and advisors, and notified law enforcement. The investigation is ongoing to determine the full impact and cost.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 9 days

Oct 11, 2023

Discovered

Oct 20, 2023

Filed

vs. sector median

8 wks faster

This filing is one of 4 records about the same incident.View merged incident

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Sitebianlianbd_a4530585606ac6fb2023-12-05 · +46dVerified by operator

Regulatory filings (2) · sorted by filing gap

SEC 8-Kbd_e43b19d902fc0c3b2023-10-16 · +4dVerified
SEC 8-Kbd_a1c0976498a766212023-11-02 · +13dVerified by operator

Name: Akumin Inc.
norm: akumin
SEC CIK: 0001776197
Domain: akumin.com

Name: Akumin Inc.
norm: akumin
SEC CIK: 0001776197
Domain: akumin.com
Industry: Healthcarenaics map

Discovered: Oct 11, 2023
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: PHIPII
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for Impact
Threat actor: ExternalFinancial

During the incident: Took quick action to secure its networks, including shutting down systems
Launched an investigation
Engaged experienced cybersecurity counsel
Engaged cybersecurity advisors
Notified law enforcement
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 9 days(9 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings

View merged incident ↗

SEC 8-KOct 16 · first

SEC 8-K+4d · this page

SEC 8-K+17d

Pattern: first filing Oct 16, last Nov 2 — a 17-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

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

Press / market report

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 statementThis record

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://www.sec.gov/Archives/edgar/data/1776197/000119312523259995/
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
Filed at: Oct 20, 2023
Raw hash: f7f6bbee26149f74202f383728dcb2fb52d888d23cf862063906a88676a1334e

AI-assisted summary above. The structured extract on this page was generated from the document below. Inspect the source to verify or correct any field.

text/html53.5 KB

Download View at source

Linked disclosures

Ransomware claims (1)

Regulatory filings (2) · sorted by filing gap

Reporting entityAkumin Inc.

Victim entityAkumin Inc.

Incidentdiscovered Oct 11, 2023

Stated responseTook quick action to secure its networks, including shutting down systems

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancewww.sec.gov

Source filing