Fact-check findings

The reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.

1. #3[disputed][awaiting moderator]in section: Scope and Affected Systems

   “The exact number of affected CVMs and the identity of affected customers has not been publicly disclosed as of June 2026.”

   reviewerThe exact number of affected CVMs and the identity of affected customers has not been publicly disclosed as of June 2026.The page cites only the brief public blog notice, which indeed omits a CVM count, but a fuller official post-mortem with the count exists and appears to have been publicly available within days of the incident. The investigation's research did not locate it.
   Proposed correction (not yet applied)

   Phala's status-page post-mortem (published/resolved June 6, 2026) later disclosed that the malicious change was applied to roughly 100 distinct CVMs; the identity of affected customers has not been publicly disclosed.
   citedphala.com/posts/security-incident-notice…pi-vulnerability
2. #18[disputed][awaiting moderator]in section: Prior Security Audits and Compliance

   “Phala also obtained SOC 2 Type I and HIPAA compliance certifications.”

   reviewerPhala obtained SOC 2 Type I and HIPAA compliance certifications.Phala's own sources disagree with each other; the more granular, dedicated compliance-status page marks HIPAA as not yet achieved, which should take precedence over the earlier press-style announcement. Notably, this section cites neither source for this specific sentence at all.
   Proposed correction (not yet applied)

   Phala also obtained a SOC 2 Type I certification; its own compliance documentation lists HIPAA compliance as still in progress ("Coming Soon"), despite a December 2025 company blog post announcing HIPAA compliance had been achieved.
3. #25[disputed][awaiting moderator]in section: Limitations of This Investigation

   “The full scope of the breach — including the number of CVMs affected, whether exfiltration was confirmed rather than merely possible, and any downstream losses suffered by users — has not been publicly disclosed.”

   reviewerThe full scope of the breach, including the number of CVMs affected, has not been publicly disclosed, and no independent forensic/third-party confirmation of the attack chain was available.This is the same underlying gap as the Scope and Affected Systems section finding: the investigation did not locate Phala's own fuller post-mortem, which answers several of the questions this section says are unanswered.
   Proposed correction (not yet applied)

   Phala's status-page post-mortem disclosed that roughly 100 distinct CVMs were affected and described the root cause as a broken-access-control flaw (OWASP A01) in CVM-modification endpoints, though whether exfiltration was confirmed rather than merely possible, and any downstream losses suffered by users, remain undisclosed.
   citedphala.com/posts/security-incident-notice…pi-vulnerability

No source the reviewer could reach confirms or contradicts the claim.

1. #10[unverifiable][awaiting moderator]in section: Incident Response and Remediation

   “Community commentary observed as Tier 3 sources noted a generally positive reception to the transparency of disclosure, though this assessment is low confidence given its sourcing.”

   reviewerCommunity commentary (Tier 3) noted a generally positive reception to the transparency of disclosure.Could not access the cited article to verify tone/content. The page already appropriately hedges this as low-confidence Tier 3 sourcing, which is good practice, but the underlying source could not be checked.
   citedmedium.com/@jamessoulman69/phalas-quick-…ike-ae8c1771f8f8

The claim was accurate when written but events since have overtaken it.

1. #19[stale][awaiting moderator]in section: Platform Background

   “Its native token, PHA, has a maximum supply of 1 billion and is used for staking, governance, and payment for TEE compute resources.”

   reviewerPHA has a maximum supply of 1 billion and is used for staking, governance, and payment for TEE compute resources.The 1 billion max-supply figure is independently confirmed, but the 'staking, governance, payment for compute' description of PHA's direct utility appears to predate Phala's 2025 migration to a vPHA-based governance/staking model and is no longer reflected in current official documentation.
   Proposed correction (not yet applied)

   Its native token, PHA, has a maximum supply of 1 billion; following Phala's 2025 migration to an Ethereum-based Layer 2, PHA is deposited to receive vPHA, which is used for governance, staking/collateral, and GPU mining rewards.
   citeddocs.phala.network/overview/pha-token
2. #20[stale][awaiting moderator]in section: Platform Background

   “https://docs.phala.network/overview/pha-token”

   reviewerCitation for PHA tokenomics no longer supports the specific max-supply/utility claim as the cited page has changed.Same underlying issue as the content-level finding.
   Proposed correction (not yet applied)

   https://www.coingecko.com/en/coins/phala-network
   citeddocs.phala.network/overview/pha-token
3. #21[stale][awaiting moderator]in the cited sources

   “https://docs.phala.network/overview/pha-token”

   reviewerMaster source-list citation for PHA tokenomics no longer supports the claim as stated.Third occurrence of the same stale citation.
   Proposed correction (not yet applied)

   https://www.coingecko.com/en/coins/phala-network
   citeddocs.phala.network/overview/pha-token

A cited source no longer resolves or no longer says what the page attributes to it.

1. #12[link rot][awaiting moderator]in section: Prior Security Audits and Compliance

   “A smart contract audit by EtherAuthority conducted on June 12, 2024, reported no active critical issues.”

   reviewerEtherAuthority completed a smart contract audit of Phala Network on June 12, 2024, reporting no active critical issues.The sole citation for this audit is dead, and web search found no independent corroboration that an EtherAuthority audit of Phala occurred at all; the claim cannot currently be verified from any live source.
   citedapp.trustblock.run/audit/bb61f86e-e46b-4…99d-1d9dd3c52509
2. #13[link rot][awaiting moderator]in the timeline

   “https://app.trustblock.run/audit/bb61f86e-e46b-4727-b99d-1d9dd3c52509”

   reviewerEtherAuthority completed a smart contract audit of Phala Network on June 12, 2024, reporting no active critical issues (timeline entry).Same underlying dead citation reused in the timeline.
   citedapp.trustblock.run/audit/bb61f86e-e46b-4…99d-1d9dd3c52509
3. #14[link rot][awaiting moderator]in the cited sources

   “https://app.trustblock.run/audit/bb61f86e-e46b-4727-b99d-1d9dd3c52509”

   reviewerTrustBlock audit record for Phala Network (master source list entry).Third occurrence of the same dead citation in the master source list.
   citedapp.trustblock.run/audit/bb61f86e-e46b-4…99d-1d9dd3c52509

The cited evidence supports part of the claim but not all of it.

1. #2[partially supported][awaiting moderator]in section: Scope and Affected Systems

   “Phala's own documentation describes Offchain KMS interactions as 'invisible off-chain,' which created the attack surface exploited in this incident.”

   reviewerPhala's documentation describes Offchain KMS interactions as 'invisible off-chain'.Minor misquote of a direct-quoted phrase from the cited documentation; the substance of the claim is correct but the quotation itself does not match the source verbatim.
   citeddocs.phala.com/phala-cloud/key-managemen…agement-protocol
2. #11[partially supported][awaiting moderator]in section: Prior Security Audits and Compliance

   “A Code4rena smart contract audit in March 2024 identified a denial-of-service vulnerability in which malicious users could send requests with excessive timeouts to crash workers.”

   reviewerA Code4rena audit in March 2024 identified a denial-of-service vulnerability allowing crashes via excessive-timeout requests.The core fact is accurate but the page presents the finding at face value without noting it was downgraded/disputed, overstating its standalone severity.
   citedcode4rena.com/reports/2024-03-phala-network
3. #16[partially supported][awaiting moderator]in section: Prior Security Audits and Compliance

   “https://medium.com/@jamessoulman69/phalas-security-audit-what-it-actually-means-for-developers-fe471534ff3e”

   reviewerSourcing for the zkSecurity audit fact relies on a personal Medium blog rather than Phala's own official audit documentation.A stronger, official source for the same fact exists and should replace the weak citation.
   citedmedium.com/@jamessoulman69/phalas-securi…ers-fe471534ff3e
4. #17[partially supported][awaiting moderator]in the timeline

   “https://medium.com/@jamessoulman69/phalas-security-audit-what-it-actually-means-for-developers-fe471534ff3e”

   reviewerSourcing for the zkSecurity audit date in the timeline relies on a personal Medium blog rather than official documentation.Same underlying sourcing issue reused in the timeline.
   citedmedium.com/@jamessoulman69/phalas-securi…ers-fe471534ff3e
5. #23[partially supported][awaiting moderator]in section: Platform Background

   “The network processed over 1.34 billion LLM tokens in a single day during 2025 stress tests.”

   reviewerThe network processed over 1.34 billion LLM tokens in a single day during 2025 stress tests.The headline figure is accurate but the 'stress tests' framing is an embellishment not found in the cited source.
   citedphala.com/posts/phala-2025-report

The cited evidence supports the claim as written.

1. #1[confirmed][no action needed]in section: Incident Overview

   “the earliest confirmed unauthorized activity occurred at 2026-05-31T22:26:36.808Z, and the vulnerability was identified and the API endpoint patched at 2026-06-01T15:47:49.456Z — a window of approximately 17 hours.”

   reviewerEarliest confirmed unauthorized activity occurred at 2026-05-31T22:26:36.808Z and the API endpoint was patched at 2026-06-01T15:47:49.456Z, a window of ~17 hours.Both the official notice and the fuller status-page post-mortem agree on these timestamps.
   citedphala.com/posts/security-incident-notice…pi-vulnerability
2. #4[confirmed][no action needed]in section: Scope and Affected Systems

   “CVMs using Onchain KMS — where key authorization operations are required to be anchored on-chain and observable via blockchain governance — were not affected.”

   reviewerCVMs using Onchain KMS were not affected by the incident.Confirmed by both the original notice and the later post-mortem.
   citedphala.com/posts/security-incident-notice…pi-vulnerabilitydocs.phala.com/phala-cloud/key-managemen…agement-protocol
3. #5[confirmed][no action needed]in section: Nature of Exposed Data

   “secrets are encrypted client-side using X25519 + AES-256-GCM before transmission and are designed to be decryptable only inside the TEE at runtime — Phala Cloud servers are explicitly documented as being unable to read plaintext values.”

   reviewerSecrets are encrypted client-side using X25519 + AES-256-GCM and are decryptable only inside the TEE; Phala servers cannot read plaintext.Matches cited documentation closely.
   citeddocs.phala.com/phala-cloud/cvm/set-secur…onment-variables
4. #6[confirmed][no action needed]in section: Nature of Exposed Data

   “Phala explicitly advised affected customers to treat as compromised: all secrets stored in encrypted environment variables, AWS registry credentials (including ECR credentials), and any other external service credentials used by affected CVMs.”

   reviewerPhala advised customers to treat all secrets, AWS/ECR credentials, and other external credentials on affected CVMs as compromised.Matches source.
   citedphala.com/posts/security-incident-notice…pi-vulnerability
5. #7[confirmed][no action needed]in section: Severity Context: TEE Trust Model Violation

   “Phala Network markets itself as a confidential AI cloud providing hardware-rooted trusted execution environments (TEEs) on Intel TDX and NVIDIA H100/H200 GPUs.”

   reviewerPhala markets itself as a confidential AI cloud with hardware-rooted TEEs on Intel TDX and NVIDIA H100/H200 GPUs.Confirmed, though the homepage's exact claim about operators being unable to read data is implied by marketing language ('Keep secrets private, and prove what ran') rather than stated as an explicit sentence.
   citedphala.com/
6. #8[confirmed][no action needed]in section: Severity Context: TEE Trust Model Violation

   “This is particularly consequential for downstream AI agent and crypto wallet deployments — documented use cases in Phala's own developer guides — where private keys or high-value API credentials may have been stored as encrypted environment variables.”

   reviewerCrypto wallet/AI agent deployments are a documented use case in Phala's developer guides, where private keys or credentials may be stored as encrypted environment variables.Confirmed.
   citedphala.com/posts/developer-guide-securely…r-on-phala-cloud
7. #9[confirmed][no action needed]in section: Incident Response and Remediation

   “No independent post-mortem from a third party had been published as of the date of this investigation.”

   reviewerNo independent post-mortem from a third party had been published as of the date of this investigation.Technically accurate as worded (no third-party post-mortem exists), distinct from the separate finding about Phala's own unaddressed post-mortem.
   citedphala.com/posts/security-incident-notice…pi-vulnerability
8. #15[confirmed][no action needed]in section: Prior Security Audits and Compliance

   “Phala's dstack confidential container framework completed an independent security audit by zkSecurity between May and June 2025, validating its zero-trust compute architecture using secure boot, cryptographic measurements, and remote attestation.”

   reviewerzkSecurity completed an independent security audit of Phala's dstack framework between May and June 2025, validating its zero-trust architecture.The underlying fact checks out, but see the separate sourcing-quality finding: the page cites only a pseudonymous Medium post rather than Phala's own official audit page, which was readily available and more authoritative.
   citedmedium.com/@jamessoulman69/phalas-securi…ers-fe471534ff3e
9. #22[confirmed][no action needed]in section: Platform Background

   “In 2025 Phala donated its dstack framework to the Linux Foundation.”

   reviewerIn 2025 Phala donated its dstack framework to the Linux Foundation.Confirmed verbatim by the cited source.
   citedphala.com/posts/phala-2025-report
10. #24[confirmed][no action needed]in section: Platform Background

    “No regulatory actions by the SEC, CFTC, OFAC, or DOJ against Phala Network or its operators were identified in available sources as of June 2026.”

    reviewerNo regulatory actions by the SEC, CFTC, OFAC, or DOJ against Phala Network or its operators were identified as of June 2026.Absence-of-evidence claim; reasonably supported by a clean search, though inherently harder to fully verify.