ANNA JAQUES HOSPITAL
bd_6da1cded0badab37 · schema v1 · pii pii-v1
Full breach record for ANNA JAQUES 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.
Anna Jaques systems compromised after cyber issue | Local News | newburyportnews.com. Anna Jaques Hospital: Anna Jaques Hospital suffered a serious cyber incident that compromised its computer systems, causing delays in services and diverting ambulances to other hospitals on Christmas Day. Hospital administrators secured the environment and engaged cybersecurity professionals for the investigation, but did not provide details on the nature or target of the attack. The ambulance service resumed on December 26, and the hospital is working in collaboration with other facilities in the Beth Israel Lahey Health system. Linked ransomware group: moneymessage.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Dec 25, 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 Sitemoneymessagebd_b79385a89ec65c172024-01-19 · +26dVerified
Regulatory filings (6) · sorted by filing gap
- HHS OCRbd_33eb2e085be46f0f2024-02-20 · +57dVerified
- Massachusetts State AGbd_52cf0518f02a8f1b2024-12-05 · +346dVerified by operator
- Indiana State AGbd_70918698b29d68ce2024-12-05 · +346dVerified
- Vermont State AGbd_86baa33310a3dfbe2024-12-05 · +346dVerified
Show 2 more filings ↓Show fewer ↑up to 351d gap
- Maine State AGbd_a2d1f21ff5fd6dad2024-12-05 · +346dVerified
- New Hampshire State AGbd_339059c3c4b680752024-12-10 · +351dVerified by operator
Filing propagation · 7 filings · 5 states
View merged incident ↗Pattern: first filing Dec 25, last Dec 10 (NH) — a 351-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.
moneymessage
According to ransomware.live, Money Message emerged in March 2023 targeting Windows and Linux systems across banking, transportation, and professional services sectors, demanding ransoms in the millions and publishing stolen data on their blog if unpaid, with most known victims based in the US.