Marathon Health database security incident

Marathon disabled the account on August 24 and confirmed on September 9 that exported files contained personal information.

Last modified

Summary

  • Environment: Marathon Health database supporting employer-sponsored health benefits
  • Operational impact: Individual notification announced; no clinical-service outage established in the reviewed notices
  • Financial impact: No incident cost quantified in the reviewed notices
  • Record status: Developing record. Reviewed November 4, 2026; updated as evidence emerges.

What happened

An impostor posing as an IT worker obtained Marathon Health employee credentials on August 24, 2026, then used them to access a cloud-hosted application and export files. Marathon identified suspicious activity and disabled the account within hours. [1]

Marathon Health notified Indiana University of a security incident involving information in one of its databases. The university’s October 15 notice warned that eligible medical-plan members could be affected even if they had never received care from Marathon Health. [4]

SMART Local 265 also informed members about the incident at Marathon Health, which provides Union Wellness Center benefits related to its Welfare Fund. These notices concern the vendor’s incident; they do not establish separate intrusions at the university or union. [2][4]

Impact

  • Vermont’s Attorney General table records 8,858 affected Vermont residents in Marathon Health’s October 30 report. This is a state-specific count, not a nationwide total. The filed categories are Social Security numbers and health records. [3]
  • SMART Local 265 said, according to Marathon Health, that members’ names and Social Security numbers may have been involved. Details vary by person and are provided in individual letters. [2][4]
  • Indiana University explained that Marathon Health holds information for all members of eligible Anthem PPO plans to administer benefits, verify coverage and provide services. Prior use of a health center is therefore not a condition for possible exposure. [4]

Marathon confirmed on September 9 that the exported files contained personal information. Its notification lists names, birth dates, contact details and Social Security numbers as potentially involved, with fields varying by individual. [1]

Timeline

  1. Employee account misused and disabled

    An IT-worker impersonator obtained credentials and exported information before Marathon disabled the account. Incident notice.

    [1]
  2. Personal information in exported files confirmed

    Marathon validated that the unauthorized person obtained personal information. Incident notice.

    [1]
  3. Indiana University informs plan members

    The university’s notice said Marathon Health planned to begin direct notification on October 20. This was an announced start date, not confirmation that every letter had been sent.

    [4]
  4. Vermont records Marathon Health’s report

    The state table lists the affected Vermont residents and reported information categories.

    [3]
  5. Briefing updated

    This briefing was last reviewed and updated on November 4, 2026.

Threat Group & Attack Vector

Marathon’s notification identifies IT-worker impersonation and abuse of an employee account as the access path. It does not establish whether the impersonation occurred by phone, email or another channel. [1]

Actors

  • No threat actor group has been identified in the reviewed public evidence.

TTPs

Response

Indiana University said individual letters would describe the affected information and complimentary identity monitoring. SMART Local 265 said people whose Social Security numbers were impacted would receive credit monitoring and identity-theft protection, with separate letters for eligible dependents where applicable. [2][4]

Marathon added safeguards and offered identity monitoring. It reported no evidence of misuse involving the information at notification. [1]