Skip to content

Memorial Hospital and Manor ransomware disrupts records

Summary

Memorial Hospital and Manor logo

Ransomware forced Memorial Hospital and Manor to use paper records and manual workflows in November 2024. A later investigation confirmed theft of personal and health information.

Key facts

Timeline

  • Incident start:
    ? Earliest known or assessed start of malicious activity or incident activity.
  • First public signal:
    ? Earliest public indication of an outage, disruption, closure or other observable incident impact. The signal does not need to mention cybersecurity.
  • First public cyber evidence:
    ? Earliest credible public information connecting the incident or disruption to malicious cyber activity.
  • Official cyber disclosure:
    ? First official acknowledgment by the affected organization or an authoritative public body that the incident was cyber-related.
  • Last impact seen:
    ? Latest public indication that disruption, degraded operations, recovery work or unresolved impact was still ongoing.

Primary victim organization

Impacted location

Critical infrastructure sector

Incident characteristics

Assessments

Attack mechanisms

  • Ransomware

    Malware that encrypts systems or data, typically accompanied by a ransom demand.

  • Unauthorized access

    Unauthorized access to systems, accounts, networks, or data.

Data impacts

  • Data theft or exfiltration

    Data was copied, transferred, downloaded, or otherwise removed from the affected environment by an unauthorized party.

  • Data unavailable

    Authorized users could not access required data because of the incident, even when the data was not encrypted, deleted, or destroyed.

Operational impacts

Extortion indicators

  • Data-theft extortion

    The actor threatened to disclose, sell, distribute, or otherwise misuse stolen data unless the victim paid or complied with demands.

  • Public leak threat

    The actor explicitly threatened to publish or publicly release victim data or incident details.

  • Leak-site listing

    The victim was listed on a threat actor or ransomware data-leak site as an alleged target or nonpaying victim.

  • Countdown or payment deadline

    The actor imposed a deadline or public countdown before increasing the demand, publishing data, deleting keys, or taking another threatened action.

Incident narrative

A ransomware attack disrupted electronic health records and other systems at Memorial Hospital and Manor in Bainbridge, Georgia, in November 2024. The hospital detected unusual activity on Nov. 2, secured its network and brought in an independent cybersecurity firm. Its later public notice confirmed that an unauthorized actor had accessed and acquired personal and health information.

The initial disruption forced staff to use paper records. In its Nov. 3 report, WALB quoted the hospital warning that patients could face longer waits at the hospital and physician offices. The hospital said it believed the level and quality of care would be maintained. That assurance concerned continued care; it did not mean that normal electronic workflows were available.

The Hospital Authority’s financial statements for the year ended March 31, 2025 subsequently identified the event as ransomware. They said all systems were shut down and hospital duties, including financial recordkeeping, were handled manually. Management described work to stabilize operations, restore systems and strengthen controls. The statements also discussed a separate Change Healthcare disruption and an electronic health record implementation, so the year’s financial deterioration cannot be assigned entirely to this attack.

On Nov. 5, The Record reported that Embargo had claimed responsibility and threatened to release 1.15 terabytes of purportedly stolen data by Nov. 8. That volume and the group’s responsibility remain attributed claims. The hospital’s confirmation of unauthorized acquisition independently establishes data theft without validating every detail of the claim. No verified ransom amount or payment was established.

The hospital’s Feb. 7 notification letter said its review to identify affected people and information concluded Jan. 31. The information varied by person and could include names, Social Security numbers, birth dates, health insurance details and medical treatment or history. Letters went out Feb. 7, followed by the Feb. 10 public notice. The hospital reported the incident to the FBI and offered identity protection services.

The incident is presumed resolved. The reviewed statements describe restoration work but do not establish a precise final restoration date. Neither the January data-review milestone nor the February notification dates establish how long the systems outage lasted.

Threat actor and claim

Listed as: Memorial Hospital & ManorSource: ransomware.liveDiscovered:

Claim details

Embargo claimed Memorial Hospital and Manor/mh-m.org and alleged1.15TBtheft. NativeUSdomainsearchreturnedtwoapparentduplicateentries:samehospital/domain/group/volume,earliestnamedentrydiscoveredNov5,2024T09:18:46.151958Z; domainentry16:48:56.931581Z. Discoverytimeisnotproveninitialcompromise/postingtime; attack_dateunavailable. Keepthisoneexistingclaim,noduplicate. OriginalTheRecordNov5reportedthreattoleakdataNov8unlessransompaid; amountandpaymentnotestablished. OfficialFeb2025hospitalnoticeindependentlyconfirmsunauthorizeddataaccess/acquisitionbyanunknownactor,notEmbargoresponsibilityorclaimedvolume. SecurityWeekFeb10reportedsubsequentleak; actualdataset/authenticity/completenessnotverifiedandnotdownloaded. SharedEmbargoactor’sstandingprofile/threeprimaryCTIrefsverified312preserved; generictools/Storm0501affiliationnotincidentforensics. Browserransomware.liveknownsite-safetyblock,nobypass; nativeMCPmetadataandoriginalreportingused.

Organizations involved

Impacted location

  • Bainbridge, Georgia

    Preserve the existing Bainbridge physical site at1500EastShotwellStreet. Currentofficialwebsite,originalFeb7hospitalletter,financialreportfooterandpublichospitalFacebookaccountagree. ExactCensusstreetmatch confirms Bainbridgecity1304896,DecaturCounty13087, notanearbymunicipalityorcountycentroid. Existinghospital’s EHR/manualclinicalandfinancialworkflows affected; no newfacilityrecord. PublichospitalauthorityownershipdoesnotbyitselfmakeallDecaturCounty/Bainbridgeajurisdictionwidehospitaloutageorlegallydefinedexclusivecatchment. Retain supportedphysicalpair; no unsupportedcountyserviceoverlay. Currentcityboundary separatelysubmittedtoOps23b692ec-8c29-49b6-b99f-a30883b5dbe2; no competingcityidentity/description/geometrywrites.

Sources

See something that needs correction?

Signed-in members can report an error, update, or missing source.