FEDERALItem 7.01 · voluntary (Reg FD)MalwareHealthcareHealthcareRansomwareData EncryptedDelayed DiscoveryPIIFinancialCredentialsMediumContained

Akumin Inc.

bd_a1c0976498a76621 · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Nov 2, 2023

To disclose

—

Affected

Not disclosed

Linked

4 records

Confidence

67%

Full breach record for Akumin Inc. →

Akumin Inc. filed a supplemental 8-K on November 2, 2023, reporting operational milestones following a previously disclosed ransomware incident. The company has restored most systems and resumed patient appointments at its cancer centers, though some services remain offline. Trading on the Toronto Stock Exchange resumed on November 3, 2023.

J jump to incidentP pin to compareR raw source

Incident timeline — partial

? — ?

Breach window unknown

Nov 2, 2023

Filed

No interval is drawn: no breach start or discovery date is on record for this filing.

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 · +33dVerified by operator

Regulatory filings (2) · sorted by filing gap

SEC 8-Kbd_76bf8888383257712023-10-20 · +13dCandidate
SEC 8-Kbd_e43b19d902fc0c3b2023-10-16 · +17dVerified

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: —
Materiality determined: Oct 16, 2023
Notification sent: Nov 2, 2023
Affected individuals: Not disclosed
Data types: PIIFinancialCredentials
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for Impact
Threat actor: ExternalFinancial

During the incident: Restored the majority of its systems
Resumed patient appointments at most locations
Resumed trading on the Toronto Stock Exchange
Source: Quoted from the filing itself, not independently verified.

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

SEC 8-K+17d · this page

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/000177619723000028/
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
Filed at: Nov 2, 2023
Raw hash: d0562340b1ef225a2d2a02753511321f5dfb4a6d37a18725adcae83acb555128

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/html33.9 KB

Download View at source

Linked disclosures

Ransomware claims (1)

Regulatory filings (2) · sorted by filing gap

Reporting entityAkumin Inc.

Victim entityAkumin Inc.

IncidentRansomware

Stated responseRestored the majority of its systems

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancewww.sec.gov

Source filing