PayrHealth — an Austin, Texas–based healthcare revenue-cycle and payor-contracting vendor (payrhealth.com describes contract negotiation and revenue management for physician groups, hospitals, and ancillary providers; schema.org metadata lists 2121 Lohmans Crossing Rd, Suite 504-823, Austin, TX 78734) — filed multi-state data-breach notices in mid-November 2026. The Texas OAG Data Security Breach Reports and BreachTally readout BR-0005533 list 16,793 affected Texas residents and 121,894 individuals in total, with breach dates August 9–18, 2026, discovery November 11, 2026 in Texas metadata, U.S. Mail notice, and a Texas record published November 17, 2026. The Texas form’s November 11 discovery date sits months after PayrHealth says it found activity around August 18 and finished its review August 26 per the CA sample PDF; the filings do not explain that gap.
PayrHealth’s official Metabase data incident notice (dated November 18, 2026, linked from the homepage) states that on or around August 18, 2026 it discovered unauthorized activity affecting the Metabase platform in connection with the August 2026 Metabase vulnerability, secured its network, engaged forensic experts, and confirmed that a limited amount of PHI may have been subject to unauthorized access. The California sample notice index (reported November 16, 2026) lists August 18, 2026 as the breach date and hosts a redacted sample individual notice PDF.
This is confirmed regulatory filing plus published company notice — not proof that ransomware was deployed, that a specific CVE was the sole root cause, or that files appeared on a criminal leak site. PayrHealth attributes the incident to Metabase on its notice page; treat that as the company’s claim, not independent verification. We do not link extortion leak sites or reproduce stolen data.
Texas medical practices and small businesses that outsource billing or contracting should read this as business-associate / vendor risk: you may never have logged into PayrHealth, but your patients’ SSNs, claims, and clinical fields can still sit in a vendor’s environment — including internet-facing analytics if a vendor runs tools such as Metabase.

Snapshot
| Field | Detail |
|---|---|
| Entity | PayrHealth (formerly Healthcents, renamed 2021 per payrhealth.com metadata) |
| HQ / notice address | Austin, Texas · 2121 Lohmans Crossing Rd., Suite 504-823, Austin, TX 78734 |
| Official web host | payrhealth.com |
| Official incident notice | Metabase data incident (Nov 18, 2026) |
| Assistance line | 1-833-516-3348 (8 a.m.–8 p.m. Eastern, Mon–Fri, per official notice) |
| Texans (Texas OAG) | 16,793 · BR-0005533 · published Nov 17, 2026 |
| Total (Texas filing readout) | 121,894 individuals |
| California AG sample posted | Nov 16, 2026 (sb24-633009) |
| Vermont AG | 5 residents · reported Nov 16, 2026 (sibling row on BR-0005533) |
| Massachusetts OCABR | 47 residents · reported Nov 17, 2026 (sibling row) |
| Notice method | U.S. Mail (Texas metadata) |
| Monitoring vendor | 12 months Cyberscout (TransUnion) per CA sample PDF |
Data categories — compare filings before you quote one list
| Source | Categories listed |
|---|---|
| BR-0005533 (Texas readout) | Name · address · SSN · medical information · health insurance information · date of birth |
| CA sample PDF | Name · address · DOB · SSN · member/patient ID · insurance and claims information · treatment or diagnosis information (same narrative on official notice) |
Fields vary by person. Do not assume every category reached every individual.
BreachTally’s CA readout (aggregator) also lists driver’s license / state ID on its index — the sample letter’s affected-data paragraph does not name those fields (driver’s license appears only in credit-freeze request instructions).
Dates — Texas window vs California single day
| Source | Breach / incident window | Discovery / review |
|---|---|---|
| BR-0005533 | Aug 9–18, 2026 | Nov 11, 2026 (Texas metadata) |
| California sb24-633009 | Aug 18, 2026 | Not stated on index page |
| Official notice | Discovered on or around Aug 18, 2026; Metabase-related activity per PayrHealth | Review completed Aug 26, 2026 per CA sample PDF; no misuse indicated at time of publication |
The Texas readout’s Nov 11, 2026 discovery field does not match PayrHealth’s August detection/review narrative above, and none of the public sources we reviewed explain why Texas lists November 11.
BreachTally counts 91 days from the end of the Texas breach window (Aug 18, 2026) to the Texas record (Nov 17, 2026) — informational only, not a legal conclusion on Tex. Bus. & Com. Code § 521.053.
UNVERIFIED: Direwolf ransomware listing (not confirmed)
Unverified claim only: MedRisk (Aug 16, 2026) reports that ransomware trackers logged PayrHealth on the Direwolf extortion group’s leak site on August 15, 2026. That date falls inside the Texas filing’s August 9–18, 2026 breach window and three days before PayrHealth says it discovered the activity (August 18, per the official notice). PayrHealth’s notice does not mention ransomware or Direwolf. It is an extortion-site allegation, not confirmation by PayrHealth, Texas, or California. We do not link leak sites, sample stolen files, or reproduce stolen data. The November 2026 AG filings and official notice are the verified public record for consumers.
Why Texas clinics should care about billing vendors
PayrHealth is not your EHR — it is the kind of downstream revenue-cycle partner that holds claims, payer contracts, and patient demographics copied from your practice. A 121,894-person mail wave with SSNs plus medical and insurance fields is a template for:
- Medical identity theft and fraudulent claims tied to real diagnosis codes.
- Spear-phishing that cites your payer, your medical group, or “PayrHealth credit monitoring” with a typosquatted domain.
- Business-associate notice lag — you may need your own Texas/HIPAA clocks when a vendor finishes a file review, not only when patients first read headlines.
For a similar Texas healthcare vendor timeline from the same November batch, see MPOWERHealth (Addison).

Generic vendor onboarding graphic (illustration only) — the table below is the breach-relevant due-diligence checklist.
Vendor due diligence and email-security checklist
Generic checklist for Texas practices and small businesses — not a transcript of PayrHealth’s internal runbook:
| Step | Action |
|---|---|
| 1 | Inventory business associates that touch claims, eligibility, or contracting — not only EHR and labs. |
| 2 | Contract for 72-hour (or tighter) incident notice to you, plus provider-downstream patient notice responsibilities. |
| 3 | Require Strong MFA (FIDO2 / YubiKey or open TOTP) on vendor admin, VPN, and remote-support roles. |
| 4 | Harden internet-facing BI/analytics (e.g. Metabase, Superset, Grafana) — disable public sharing / anonymous access, restrict to VPN, enforce MFA, and apply vendor CVE advisories. |
| 5 | Enforce DMARC reject and MTA-STS on your domain before the next vendor breach mail cycle. |
| 6 | After any vendor incident, warn staff: no MFA codes by phone; no “updated W-9 / payer contract” links from unexpected senders. |
| 7 | Reconcile state AG data-type lists with your own minimum-necessary exports — document what you did share vs what the filing lists. |
| 8 | Run a baseline posture check via the free domain security scan homepage search (type the domain yourself — do not trust emailed ?domain= links). |
MFA: YubiKey and Google Authenticator
| Grade | Meaning |
|---|---|
| Fail | SMS, voice, email OTP, or no public YubiKey / open TOTP path |
| Pass | Self-serve Google Authenticator-style open TOTP |
| Strong | FIDO2 / YubiKey-class security key for sign-in |
| Unevaluated | No login on the public host, or no usable public MFA documentation |
| Platform | Grade | YubiKey | Authenticator |
|---|---|---|---|
| payrhealth.com (marketing + notice) | Unevaluated | — | — |
| Workforce mail (M365 MX) | Unevaluated | Not public | Not public |
| Cyberscout enrollment (if offered) | Unevaluated | — | — |
payrhealth.com is a Webflow marketing and notice site with no public sign-in to grade. MX points to Microsoft 365 (payrhealth-com.mail.protection.outlook.com), so workforce accounts are likely Entra ID tenants — where Microsoft documents FIDO2 keys and authenticator apps. That is baseline guidance, not proof of PayrHealth’s live policy.
Harden your billing, EHR, and M365 admin roles with hardware keys or open TOTP before the next vendor notice drives phishing volume.
Directory: MFA support directory · Category → Healthcare.
Recommended MFA tools
| Product | Best for | Get it |
|---|---|---|
| YubiKey 5C NFC | USB-C laptops + NFC phones | Amazon |
| YubiKey 5 NFC | USB-A desktops + NFC phones | Amazon |
| Proton Pass | Passkeys + authenticator-style TOTP | Proton Pass |
We may earn a commission if you buy a YubiKey or sign up for Proton Pass through the links above.

Independent cybersecurity audits
EmailMeNow audit, November 19, 2026, via authenticated admin API (scope=full) — no public /?domain= URL and no POST /start. 100% is the ideal overall domain-security score. 0 of 2 scored hosts reach it.
| Organization | Domain | Overall | Gap vs 100% |
|---|---|---|---|
| PayrHealth (official) | payrhealth.com | 77% | −23 |
| Cyberscout (monitoring vendor in CA sample) | cyberscout.com | 61% | −39 |
| Domain | Identity | Transport | Website |
|---|---|---|---|
| payrhealth.com | 75% | 15% | 87% |
| cyberscout.com | 75% | 15% | 43% |
How to read this: payrhealth.com at 77% still shows 15% transport — the recurring MTA-STS enforcement gap matters when attackers spoof “PayrHealth monitoring” or “payer contract update” mail after a 122k-person notice. cyberscout.com at 61% is the monitoring brand named in the CA sample PDF; enroll only via the URL and code in your mailed letter, not forwarded links.
These scores are public posture only; they do not reconstruct August access paths inside PayrHealth.
For managed review, see EmailMeNow services.

Website stack
Passive website-tech probes on November 19, 2026:
| Domain | Stack signal |
|---|---|
| payrhealth.com | Webflow (hosted SaaS) · live TLS Google Trust Services (issuer WE1) · expires 2026-12-22 (handshake Nov 19, 2026) |
| bfs.cyberscout.com (common Cyberscout enrollment host) | Stack undetected · Google Trust Services TLS expires 2027-01-30 (CT) |
Point-in-time only. A marketing homepage is not proof that billing, EDI, Metabase, or admin hosts share this stack.
Blacklist and lookalike domains
Email blacklist (public DoH, November 19, 2026): payrhealth.com clear (0 mail/domain hits on checked lists). SPFBL notes on shared web/CDN IPs are low-signal provider noise unless you also see deliverability failure.
DNS lookalike scans on payrhealth.com (standard profile):
| Metric | Count |
|---|---|
| To review | 5 |
| Likely owned by brand | 2 |
| BEC staging (automated) | 0 |
Registered strings worth a manual review (omit unrelated live businesses):
| Lookalike | Technique | Note |
|---|---|---|
| pyrhealth.com | omission | Live NS + A + MX |
| paydhealth.com | adjacent-key | Live NS + A + AAAA + MX |
| payrhealth.net | tld-swap | HTTP redirect to payrhealth.com (likely brand-owned) |
| payrhealth.org | tld-swap | HTTP redirect to payrhealth.com (likely brand-owned) |
parhealth.com is a different live brand (Par Health, a pharmaceutical company) — not a PayrHealth typo to treat as incident-related.
Patients and clinic staff should type payrhealth.com, not a one-letter typo. Continuous monitoring: Cybersquat Domain Monitoring.
CourtListener
CourtListener REST search on November 19, 2026 for “PayrHealth” and data breach returned a U.S. District Court for the Southern District of Texas civil docket 4:26-cv-06857 captioned In re PayrHealth, LLC Data Breach Litigation, filed August 19, 2026 (CourtListener docket). That filing predates the November 2026 state AG publications above; pleadings are allegations until adjudicated. We did not rely on docket text for breach counts or data-type lists — those come from AG filings, the CA sample PDF, and the official notice.
We did not treat the August federal docket as a substitute for a present HHS OCR “wall of shame” row; check HHS OCR’s public breach tool for updates before assuming a HIPAA posting is missing.
What affected individuals and Texas practices should do now
- Read PayrHealth’s official Metabase data incident notice and your mailed letter. Call 1-833-516-3348 (per the official notice) or use the mailing address on your letter with questions.
- If your letter offers Cyberscout, enroll only through the web address and unique code in that letter within the 90-day window described in the CA sample PDF — not a search-result or text-message link.
- Watch explanation of benefits, payer statements, and credit files — SSN plus treatment/diagnosis and claims fields support tailored phishing and medical identity theft.
- Practice owners: PayrHealth says it notified medical providers before patients (CA sample PDF). If your practice hasn’t heard from them, ask — and treat unexpected “urgent portal” mail as phishing.
- Report phishing to IC3 and monitor the Texas OAG breach portal.
Related coverage
- Texas healthcare breaches hub
- Healthcare AG breach tracker
- Texas OAG YTD dashboard
- MPOWERHealth Texas vendor breach (Nov 2026)
- Prism Medical supplier breach (Nov 2026)
- MFA support directory
Check your domain free at audit.emailmenow.com, add Domain Watch ($29/mo) to catch spoofed vendor mail earlier, or see automated reports and monitoring.
Sources: Texas OAG Data Security Breach Reports · BreachTally BR-0005533 · California AG sb24-633009 · California AG sample notice PDF · PayrHealth — Metabase data incident (Nov 18, 2026) · PayrHealth corporate site · MedRisk — UNVERIFIED Direwolf claim (Aug 16, 2026). Independent EmailMeNow audit, website-tech, blacklist, cybersquat, and CourtListener work November 19, 2026.