Cogdell Memorial Hospital
bd_a9107cf0c1478764 · schema v1 · pii pii-v1
Full breach record for Cogdell Memorial Hospital →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.
Network Incident Preventing the Use of Systems and Phones - Cogdell Memorial Hospital. Cogdell Memorial Hospital: Cogdell Memorial Hospital is facing a computer incident that blocks access to some of its systems and severely disrupts its telephone network, resulting in the disconnection of its network and the adoption of manual processes to maintain routine services. They are collaborating with IT specialists and have informed the relevant authorities, while clarifying that there is currently no evidence of fraudulent use of data, but the investigation is ongoing. The hospital advises caution regarding potential scams and promises to provide additional information as soon as it becomes available. Linked ransomware group: lorenz.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Nov 1, 2023
Press report
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Attack → press
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitelorenzbd_44f1da499aa8c6e82023-11-09 · +8dCandidate
Regulatory filings (1) · sorted by filing gap
- Presslorenzbd_6e42fa4322d633dd2023-10-10 · +22dCandidate
Filing propagation · 2 filings
View merged incident ↗Pattern: first filing Oct 10, last Nov 1 — a 22-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
- 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.
lorenz
According to ransomware.live, Tesorion describes Lorenz as a ransomware with design and implementation flaws, leading to impossible decryption with tools provided by the attackers. A free decryptor for 2021 versions was made available via the NoMoreRansom initiative. A new version of the malware was discovered in March 2022, for which again was provided a free decryptor, while the ransomware operators are not able to provide tools to decrypt affected files.