Skip to content
cisonews.net

Incident · 8-K Item 1.05

Astrana Health data breach: callers spoofing the company's phone number got into its servers

Published . Updated 2026-11-12. By the cisonews.net Desk.

Astrana Health, Inc. disclosed to the SEC on September 23, 2026, under Item 1.05 of Form 8-K, that its subsidiary Astrana Health Management detected unusual activity tied to phone-based social engineering aimed at gaining access to company systems. The company believes private or confidential information on its servers was accessed or acquired without authorization, and the filing gives no count of affected people.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.

DateWhat happenedSource
Third quarter of 2026Calls to employees from people posing as staff, using the spoofed main number10-Q
September 22, 2026Astrana decides the incident is material8-K
September 23, 2026Item 1.05 8-K filed8-K
November 6, 202610-Q: data accessed and acquired; scope and notifications still under review10-Q

Who is Astrana Health?

Astrana is a California company that runs back-office services such as claims and billing for physician groups, SecurityWeek reported. The incident was at its subsidiary Astrana Health Management. Its quarterly report says that its risk-bearing organizations, with more than 20,000 contracted physicians, were responsible for coordinating care for about 1.5 million patients as of September 30, 2026. That figure measures the company's size. It is not a count of people affected by the breach, and Astrana has published no such count.

What happened in the Astrana Health data breach?

The filing describes a series of calls in which the callers posed as company personnel and spoofed the main corporate telephone number. They contacted certain employees to try to obtain access. The company says its cybersecurity team detected and responded to the activity and began an investigation. The filing does not give a date when the activity was detected or when it began.

What information was involved?

Astrana lists several remedial steps, among them credential resets, limits on remote access tools and restoration of some systems from clean backups. It is notifying state and federal regulators and payer partners.

The company has not settled what was taken. It is still assessing whether patient, employee, credentialed provider, confidential business and financial information, or intellectual property was involved. It says it intends to notify affected patients based on its findings.

Why did Astrana call the incident material?

Astrana set September 22, 2026 as the date it determined the incident to be material, citing the possible sensitivity of the data. It cannot yet estimate the full effect on operations, finances or reputation, but it does not currently expect a material effect on its financial condition or results. It carries cybersecurity insurance that may cover some losses, with no assurance of sufficiency.

What did Astrana's quarterly report of November 6, 2026 add?

Astrana's 10-Q for the quarter ended September 30, 2026, filed on November 6, 2026, states that private or confidential information held on its servers was accessed and acquired without authorization, and places the calls in the third quarter of 2026. At that date the investigation into the scope of the data, and the review of which notifications are required, were still under way.

The company expects further costs for cybersecurity experts and other advisers, remediation and notification, and says it cannot yet estimate the incident's full effect. It adds that its cybersecurity insurance may not cover all of those costs. The report gives no dollar figure for the incident.

Has a ransomware group claimed the Astrana attack?

Not as of the trade press reports. SecurityWeek wrote that Astrana did not name the attacker and that it had seen no known ransomware or extortion group claim the incident. The HIPAA Journal reported the same on September 29, 2026. Neither filing describes encryption or a ransom demand.

Will Astrana patients get a letter?

Astrana has said it intends to notify affected patients once its review shows who they are; its filings so far give no letter date and no count. The investigation is ongoing, and the filing states that Astrana will amend it when missing details are determined or become available. Neither the filing nor the November 10-Q says how many people are affected, which data types were confirmed, or whether notification letters have gone out.

The rule behind an Item 1.05 filing

Form 8-K Item 1.05 is where a public company reports a cybersecurity incident it has determined to be material. Under the rule the SEC adopted on July 26, 2023, the filing is generally due four business days after the company determines that the incident is material. Source: U.S. Securities and Exchange Commission, press release 2023-139. The guide What is SEC Form 8-K Item 1.05, and what counts as a disclosed cyber incident? reads the rule in full, and the glossary defines Form 8-K Item 1.05.

Other health care incidents on cisonews.net

All health care incidents

Sources

  1. 2026-11-06 · AAstrana Health, Inc., Form 10-Q for the quarter ended September 30, 2026 (SEC EDGAR), published November 6, 2026
  2. 2026-09-23 · AAstrana Health, Inc., Form 8-K (SEC EDGAR), published September 23, 2026
  3. 2026-09-24 · BSecurityWeek, Astrana Health Data Breach Impacts Private, Confidential Information, published September 24, 2026
  4. 2026-09-29 · BThe HIPAA Journal, Astrana Health Notifies SEC About Social Engineering Incident, published September 29, 2026
  5. 2023-07-26 · AU.S. Securities and Exchange Commission, press release 2023-139, published July 26, 2023

Tier A: the organization itself (including notices it filed with a state attorney general), a regulator or SEC EDGAR. Tier B: established press. Each fact on this page carries its supporting passage in the page source.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.