Skip to content
Breach Index · running record

Phala security incident in 2026: the DeepSeek V4 Flash 0731 inference server

Phala runs confidential-computing infrastructure and hosts AI models for inference, including traffic that the router OpenRouter sends to it. This page tracks the intrusion Phala disclosed in its own preliminary report of 10 November 2026, separately from the wider canary research by Dragos.

Short answer

Was Phala hacked?

Yes, by Phala's own account. Its preliminary incident report (10 November 2026) says an attacker "took control of the inference VM" serving DeepSeek V4 Flash 0731, making in-flight request data visible during processing. Phala says it served this model only through the affected route, and that the requests were routed to it by OpenRouter.

Phala asks users to treat DeepSeek V4 Flash 0731 requests from 21 October 2026 00:00 UTC to 8 November 2026 05:35 UTC as exposed, and to "treat any credentials or other sensitive information in those requests as compromised". Requests confirmed as exposed by canary testing were sent on 21 and 22 October. Separately, Phala says the attacker chained a legacy internet-facing service with management interfaces that "did not independently authenticate callers", created unauthorized confidential VMs (CVMs) on two servers and obtained application credentials.

Dragos's 19 November canary research describes three breached AI providers but names none of them; no source says whether Phala is one of them.

Timeline at a glance

  1. 21 Oct 2026Attacker reaches internal management interfaces on one server and inserts malware (00:00 UTC); start of the DeepSeek V4 Flash 0731 exposure window. (Phala)Confirmed
  2. 22 Oct 2026Earliest observed misuse of data from the attack (05:41 UTC). (Phala)Confirmed
  3. 4–5 Nov 2026A second server tampered with and an unauthorized CVM created. (Phala)Confirmed
  4. 5 Nov 2026Unauthorized activity detected; initial intrusion contained (08:15–17:55 UTC). (Phala)Confirmed
  5. 6 Nov 2026KMS root key rotation completed (05:02 UTC). (Phala)Confirmed
  6. 8 Nov 2026A third-party researcher shows DeepSeek V4 Flash 0731 request data was exposed; the deployment is taken offline and containment completes at 05:35 UTC. (Phala)Confirmed
  7. 10 Nov 2026Phala publishes its preliminary incident report. (Phala)Confirmed
  8. 22 Nov 2026OpenRouter links Phala's report in its announcement on inference-provider incidents. (OpenRouter)Reported

Last updated 22 November 2026. Every entry is dated and linked to its source; claims by attackers are labelled as claims, never stated as fact.

Phala incident timeline, in detail

Confirmed = acknowledged by Phala, a regulator filing or a court. Reported = credible reporting Phala has not fully confirmed. Unverified claim = an attacker or leak-site claim.

Oct–Nov 2026ConfirmedIntrusion (AI inference infrastructure)

Inference VM serving DeepSeek V4 Flash 0731 taken over; prompts in flight exposed

What happened. Phala says the DeepSeek V4 Flash 0731 deployment ran on a new GPU server and "was serving production traffic without our full production security hardening". The attacker took control of the inference VM, so request data was visible while it was being processed. Phala ran canary tests from 1 July to 7 November; only canaries sent on 21 and 22 October were later misused, and Phala notes that sampling does not bound the full exposure.

Impact. Users who sent DeepSeek V4 Flash 0731 requests routed to Phala by OpenRouter between 21 October 00:00 UTC and 8 November 05:35 UTC should rotate any API keys, tokens, passwords or other secrets in those requests and review those accounts for unauthorized activity. Phala last observed misuse of data from the attack on 9 November.

Sources: Phala preliminary report · PlayCISO write-up

Oct–Nov 2026ConfirmedIntrusion (management plane)

Legacy service and unauthenticated management interfaces: unauthorized CVMs and application credentials

What happened. Phala says the attacker chained a legacy internet-facing service with management interfaces that "relied on loopback access for trust and did not independently authenticate callers", created unauthorized CVMs on two servers and obtained application credentials. Some CVMs may have had KMS-derived secrets exposed.

Impact. Phala contained the intrusion on 5 November and completed a KMS root key rotation on 6 November. CVM owners who received a notice should rotate the identified KMS-derived and other affected credentials; Phala says owners who got no notice need no action on current findings, and that it found no evidence of compromise affecting other models or products.

Sources: Phala preliminary report

Where the reports disagree

  • Exposure window vs confirmed exposure: Phala asks users to treat the whole 21 October to 8 November window as exposed, but its canaries confirm exposure only for requests sent on 21 and 22 October. Phala says the canary sampling does not bound the exposure, so use the full window.
  • Link to the Dragos research: Dragos says three AI providers were breached and names none. OpenRouter lists Phala's report among provider announcements but does not say Phala is one of the three providers it off-boarded. Phala's report credits "a third-party security researcher" and does not name Dragos.
  • This is a preliminary report; Phala may revise dates or scope.

The pattern across the record

Confidential computing does not cover the management plane

The attacker did not break the confidential VMs' isolation: they came in through a legacy service and management interfaces that trusted loopback callers, then created their own VMs.

A server outside the hardening baseline

Phala says the affected model ran on a new GPU server serving production traffic before full production hardening. New capacity added under demand is a common gap.

Prompts carry secrets

Anything in a prompt, including keys pasted into agent context, is readable by whoever controls the inference host.

What it means for Phala customers — and what to do

If you or your agents sent DeepSeek V4 Flash 0731 requests through OpenRouter, or run CVMs on Phala, check the dates against your own logs.

  1. 1.Rotate secrets sent in prompts

    Any API key, token, password or signed URL in DeepSeek V4 Flash 0731 requests between 21 October 00:00 UTC and 8 November 05:35 UTC.

    Secret rotation order planner
  2. 2.Act on a CVM notice

    If Phala notified you, rotate the KMS-derived and other credentials it named, then review those accounts for misuse.

    Leaked credential response
  3. 3.Pin your upstream providers

    For sensitive workloads, choose the providers your router may use instead of letting it pick, and keep secrets out of prompts.

    What to do this week
Take this with you
Incident timeline · What Phala customers should do · Sources

CISO takeaways

Sources

Company statements and regulator filings first, then reputable reporting. Reviewed 22 November 2026.

  1. 1.November preliminary incident report — Phala, 10 Nov 2026
  2. 2.Data Processing Incidents on Inference Providers — OpenRouter, 22 Nov 2026
  3. 3.Three breaches, endless leaks: Your AI supply chain needs canaries — Dragos, 19 Nov 2026

Frequently asked questions

Was Phala hacked?

Yes, by Phala's own preliminary report of 10 November 2026: an attacker took control of the inference VM serving DeepSeek V4 Flash 0731, and separately created unauthorized confidential VMs and obtained application credentials.

Which requests were exposed in the Phala incident?

Phala says to treat DeepSeek V4 Flash 0731 requests routed to it by OpenRouter from 21 October 2026 00:00 UTC to 8 November 2026 05:35 UTC as exposed. Canary testing confirmed exposure for requests sent on 21 and 22 October.

What should I do after the Phala incident?

Rotate any API keys, tokens, passwords or other secrets you sent in those requests and review the accounts for unauthorized activity. CVM owners who received a notice should rotate the credentials it names.

Is Phala one of the three providers Dragos found breached?

No source says so. Dragos does not name its three breached providers, and OpenRouter does not name the three providers it off-boarded.

Same sourced, verification-tagged timeline, company by company — compare how peers have fared.

Or see the full Breach Index and how to read it.

Independent analysis for security-leadership education; not affiliated with or endorsed by Phala. Facts are attributed to the dated sources above, and anything disputed or unconfirmed is labelled as such. See the full Breach Index.