Cross-Border Healthcare Data Under Attack: A Mock Campaign Against U.S.–South America Health Networks
Healthcare and Public Health sector · Remote access, patient-data integration and medical imaging systems
1. Executive summary
Fictional A financially motivated criminal group we call COBALT CONDOR is targeting the connections between U.S. health systems and their partners in South America: clinical research sites, telehealth providers and health information exchanges. The group enters through internet-facing remote access and vendor support tools. It then moves to the systems that carry patient data between organizations, steals clinical and patient records, and deploys ransomware. No real organization, government or known threat group is represented by this actor.
- Real exposure, fictional attacker. Every entry point in this scenario is a real flaw. Four of them are on CISA's list of vulnerabilities known to be exploited in the wild.[13]
- Patient safety, not just privacy. One real flaw lets an unauthenticated sender merge patient records in an imaging archive, which threatens the accuracy of medical records.[19]
- Several reporting clocks start at once. A single cross-border incident can trigger HIPAA breach notice in the U.S., a three-business-day notice to Brazil's data protection authority, and obligations under Chile's cybersecurity framework law.[8][5][6]
2. Strategic context: U.S.–South America health and cyber ties
Each of the following developments is real and documented.
- Cross-border health data exchange is expanding. On September 29, 2026, the Pan American Health Organization reported progress on the Pan-American Highway for Digital Health. This joint PAHO and Inter-American Development Bank initiative aims for secure, interoperable exchange of health information within and between countries. Chile was among the countries presenting national progress, and speakers stressed that data standards, governance and cybersecurity must accompany the technology.[1]
- Hemispheric cyber cooperation is established. DHS hosted the Western Hemisphere Cyber Conference in Washington in September 2023, bringing together the United States, 20 partner countries and industry. Speakers included representatives of Argentina, Brazil, Chile, Ecuador and Peru.[2] The Organization of American States' cybersecurity program helps member states build national strategies and incident response teams, and runs the CSIRTAmericas network for sharing threat information.[3]
- South American law treats health data and hospitals as high-stakes. Brazil's data protection law (LGPD) classifies health data as sensitive personal data.[4] Chile's Framework Cybersecurity Law (Ley 21.663, published April 8, 2024) lists hospitals, clinics, medical centers and pharmaceutical production and research among essential services, and establishes the National Cybersecurity Agency (ANCI).[6]
Our assessment: As health systems across the Americas connect, one organization's exposure becomes its partners' exposure. Attackers gain more ways in, and defenders face overlapping national rules when something goes wrong. The scenario below shows how that plays out.
3. Attack chain and techniques
Fictional The campaign narrative is invented. Each technique is a real entry in the MITRE ATT&CK framework, and each exploited flaw is a real, published vulnerability.
T1190 · T1133 · T1566.001
T1199 · T1078
T1210
T1565.001
T1567.002 · T1490 · T1486
| Stage | What happens in the scenario Fictional | ATT&CK technique (real) | Real flaw used |
|---|---|---|---|
| Initial access | The group exploits an unpatched VPN at a U.S. academic medical center that shares research data with partner sites in Brazil and Chile. | T1190 Exploit Public-Facing Application; T1133 External Remote Services[21] | CVE-2026-104935 |
| Initial access | Spanish- and Portuguese-language emails posing as clinical trial invoices target research coordinators. A vulnerable email gateway is exploited in parallel. | T1566.001 Spearphishing Attachment; T1190[21] | CVE-2026-76519 |
| Initial access | A third-party IT support provider's remote-support appliance is compromised, giving the group a trusted path into several client hospitals at once. | T1199 Trusted Relationship; T1078 Valid Accounts[21] | CVE-2026-102764 |
| Lateral movement | The group exploits the hospital's HL7 integration engine, which moves patient data between clinical systems and partner sites, and gains code execution. | T1210 Exploitation of Remote Services[21] | CVE-2023-43208 CVE-2026-82583 |
| Lateral movement | The group connects to the medical imaging archive from an unregistered system, which the archive's default configuration accepts. | T1210[21] | CVE-2026-105279 |
| Impact (integrity) | The group sends unauthenticated patient-merge messages, combining unrelated patient records to create confusion and add pressure during extortion. | T1565.001 Stored Data Manipulation[21] | CVE-2026-105667 |
| Exfiltration | Clinical trial datasets and patient records are uploaded to a commercial cloud storage service. | T1567.002 Exfiltration to Cloud Storage[21] | Not applicable |
| Impact (availability) | Backups and shadow copies are deleted, then ransomware encrypts clinical and research servers. | T1490 Inhibit System Recovery; T1486 Data Encrypted for Impact[21] | Not applicable |
4. Vulnerabilities and classifications
All entries below are real. CVSS scores come from NIST's National Vulnerability Database (NVD) or from CISA's medical device advisories, as noted. Weakness types use MITRE's Common Weakness Enumeration (CWE).[22] Exploitation status comes from CISA's Known Exploited Vulnerabilities (KEV) catalog, version 2026.10.16.[13]
| Priority | CVE | Product | Weakness (CWE) | CVSS | Exploitation status | Source |
|---|---|---|---|---|---|---|
| P1 | CVE-2026-102764 | BeyondTrust Remote Support | CWE-290 Authentication Bypass by Spoofing | 9.8 Critical CVSS 3.1, NVD; 9.3 in CVSS 4.0 (vendor) | In KEV added Oct 16, 2026; federal due date Oct 19, 2026 | [13][15] |
| P1 | CVE-2026-104935 | Ivanti Connect Secure (VPN) | CWE-290 Authentication Bypass by Spoofing | 8.6 High CVSS 3.1, CNA score on NVD | In KEV added Oct 13, 2026; federal due date Oct 16, 2026 | [13][14] |
| P1 | CVE-2026-76519 | Cisco Secure Email Gateway | CWE-23 Relative Path Traversal | 9.8 Critical CVSS 3.1, Cisco score on NVD | In KEV added Oct 14, 2026; federal due date Oct 17, 2026 | [13][16] |
| P1 | CVE-2023-43208 | NextGen Healthcare Mirth Connect (HL7 integration engine) | CWE-502 Deserialization of Untrusted Data | 9.8 Critical CVSS 3.1, NVD | In KEV added May 20, 2024; known use in ransomware campaigns | [13][17] |
| P2 | CVE-2026-105279 | J4Care dcm4che (medical imaging archive) | CWE-306 Missing Authentication for Critical Function | 9.1 Critical CVSS 3.1, CISA | No known public exploitation | [19] |
| P2 | CVE-2026-97851 | J4Care dcm4che | CWE-862 Missing Authorization | 9.1 Critical CVSS 3.1, CISA | No known public exploitation | [19] |
| P3 | CVE-2026-82583 | NextGen Connect (Mirth Connect) 4.7.1 and earlier | CWE-89 SQL Injection | 8.3 High CVSS 3.1, CISA | No known public exploitation | [18] |
| P3 | CVE-2026-78224 | NextGen Connect (Mirth Connect) | CWE-611 XML External Entity Reference | 8.2 High CVSS 3.1, CISA | No known public exploitation | [18] |
| P3 | CVE-2026-105667 | J4Care dcm4che (HL7 listener) | CWE-306 Missing Authentication for Critical Function | 7.5 High CVSS 3.1, CISA | No known public exploitation | [19] |
Priority method (Strat Cyber Advisors): P1 = listed in CISA KEV, so attackers are already using it. P2 = CVSS 9.0 or higher, not yet in KEV. P3 = CVSS 7.0 to 8.9. Federal due dates in KEV legally bind U.S. federal civilian agencies only; for everyone else they indicate urgency. CISA reports no known public exploitation of the two medical device advisories as of their release.[18][19]
5. Regulatory and policy obligations
These are real requirements that a cross-border incident like this one would likely engage. Whether each applies depends on the organizations and data involved. This section is not legal advice.
| Jurisdiction | Instrument | What it requires (summary) | Why it matters here | Source |
|---|---|---|---|---|
| United States | HIPAA Security Rule | National standards for administrative, physical and technical safeguards that protect electronic health information. | Governs the safeguards on the VPN, integration engine and imaging systems. | [7] |
| United States | HIPAA Breach Notification Rule (45 CFR 164.400–414) | Notify affected individuals within 60 days of discovery. Report to HHS: within 60 days for breaches affecting 500 or more people, or annually for smaller breaches. Notify prominent media where more than 500 residents of a state or jurisdiction are affected. Business associates must notify the covered entity. | The exfiltration of patient records is a reportable breach unless a risk assessment shows a low probability of compromise. | [8] |
| United States | Proposed HIPAA Security Rule update (FR Doc. 2024-30983, 90 FR 898) | HHS proposal to strengthen cybersecurity requirements for electronic health information. Published January 6, 2025; comments closed March 7, 2025. | Signals tighter future expectations for the same controls this scenario defeats. | [9] |
| United States | FD&C Act section 524B and FDA premarket cybersecurity guidance | Section 524B, in effect since March 29, 2023, sets cybersecurity requirements for "cyber devices." FDA issued final premarket guidance on June 27, 2025. | Applies to manufacturers of connected medical devices and imaging software. Hospitals rely on their patches and disclosures. | [10] |
| United States | CIRCIA rulemaking (cyber incident reporting for critical infrastructure) | CISA's rulemaking on mandatory incident and ransom-payment reporting is still in progress. CISA held town hall meetings in 2026. | Once final, it would add a federal reporting obligation for covered healthcare entities. | [11] |
| United States | HHS Healthcare and Public Health Cybersecurity Performance Goals | Voluntary practices from HHS: 10 essential goals that set a floor of safeguards, and 10 enhanced goals. | A practical benchmark for the controls in Section 6. | [12] |
| Brazil | LGPD (Law 13.709/2018), Arts. 5, 46 and 48 | Health data is sensitive personal data. Controllers must apply technical and administrative security measures, and must notify the data protection authority (ANPD) and affected people of incidents that may cause significant risk or harm. | Patient and trial data from Brazilian partner sites is covered. | [4] |
| Brazil | ANPD Resolution CD/ANPD No. 15 (April 24, 2024) | Controllers notify ANPD and affected data subjects within three business days, unless a specific law sets a different deadline. A supplementary notice can follow within 20 business days. | Sets a very short clock for the Brazilian side of the incident. | [5] |
| Chile | Ley 21.663, Framework Cybersecurity Law (published April 8, 2024) | Sets minimum requirements for preventing and responding to cybersecurity incidents, and duties for essential services and operators of vital importance. Health services, including hospitals, clinics and pharmaceutical research, are listed as essential services. Establishes ANCI. | Chilean partner hospitals and research sites are likely in scope as essential services. | [6] |
6. Recommended actions
Each action names the HHS Cybersecurity Performance Goal it supports.[12]
Within 72 hours
- Patch or isolate every P1 system in Section 4. Treat any that were exposed before patching as possibly compromised. Mitigate Known Vulnerabilities
- Inventory third-party remote-support tools and VPN accounts. Disable any that are unused. Vendor/Supplier Cybersecurity Requirements
- Require multifactor authentication on all remote access and on vendor accounts. Multifactor Authentication
- Warn research and billing staff about invoice-themed emails in Spanish and Portuguese. Email Security; Basic Cybersecurity Training
Within 30 days
- Move integration engines and imaging archives onto separate network segments that only approved partner systems can reach. Network Segmentation
- Turn on authentication for imaging (DICOM) connections and HL7 listeners. Reject connections from unregistered systems. Configuration Management
- Send integration-engine, imaging and remote-access logs to a central system and alert on unusual patient-merge volumes. Centralized Log Collection; Detect and Respond to Relevant Threats
- Test that backups can be restored and are stored offline. Basic Incident Planning and Preparedness
Strategic
- Build a cross-border incident playbook that maps HIPAA, Brazilian ANPD and Chilean Ley 21.663 notification duties and deadlines. Centralized Incident Planning and Preparedness
- Require partner sites and vendors to report incidents to you promptly, and write this into contracts and data-sharing agreements. Third Party Incident Reporting
- Keep a current inventory of systems that exchange data with international partners. Asset Inventory
- Encrypt research and patient data in transit and at rest. Strong Encryption
7. What to watch for
These detection ideas follow from the techniques and flaws above. They are general guidance, not indicators from a real incident.
- New administrator sessions or file activity on remote-support appliances, especially outside the vendor's normal support hours.
- VPN logins that succeed without a matching multifactor prompt, or that come from unexpected locations.
- Imaging archive connections from systems that are not on the registered list.
- Spikes in HL7 patient-merge messages, or merges from senders that do not normally send them.
- Large uploads from clinical or research servers to consumer cloud storage services.
- Deletion of shadow copies or backup catalogs.
Appendix A. Source map
Every citation in this advisory, traced to its originating publisher. All sources were opened and checked on October 19, 2026.
| # | What it supports | Source (origin) | Type | Link |
|---|---|---|---|---|
| 1 | Pan-American Highway for Digital Health; cross-border health data exchange; Chile's participation | Pan American Health Organization (PAHO/WHO), news release, Sept 29, 2026 | Intergovernmental | paho.org |
| 2 | Western Hemisphere Cyber Conference, Sept 27–28, 2023; participating countries | U.S. Department of Homeland Security | U.S. government | dhs.gov |
| 3 | OAS cybersecurity program; national strategies, incident response teams, CSIRTAmericas | Organization of American States, CICTE | Intergovernmental | oas.org |
| 4 | LGPD: health data is sensitive (Art. 5); security measures (Art. 46); incident notice (Art. 48) | Presidency of the Republic of Brazil, Law 13.709/2018 (official text) | Brazilian law | planalto.gov.br |
| 5 | Three-business-day incident notice; Resolution CD/ANPD No. 15/2024; 20-day supplement | Brazilian National Data Protection Authority (ANPD) | Brazilian regulator | gov.br/anpd |
| 6 | Ley 21.663 (published Apr 8, 2024); health as an essential service; ANCI | Library of the National Congress of Chile (BCN), Ley Chile (official text) | Chilean law | bcn.cl |
| 7 | HIPAA Security Rule standards | U.S. Department of Health and Human Services (HHS) | U.S. government | hhs.gov |
| 8 | Breach Notification Rule: 45 CFR 164.400–414, 60-day deadline, 500-person threshold | U.S. Department of Health and Human Services (HHS) | U.S. government | hhs.gov |
| 9 | Proposed HIPAA Security Rule update; FR Doc. 2024-30983; 90 FR 898; RIN 0945-AA22 | Office of the Federal Register (HHS proposed rule) | U.S. government | federalregister.gov |
| 10 | Section 524B (effective Mar 29, 2023); final premarket guidance (June 27, 2025) | U.S. Food and Drug Administration (FDA) | U.S. government | fda.gov |
| 11 | CIRCIA rulemaking town hall meetings; FR Doc. 2026-10417; 91 FR 30498 (May 26, 2026) | Office of the Federal Register (CISA/DHS notice) | U.S. government | federalregister.gov |
| 12 | HPH Cybersecurity Performance Goals; essential and enhanced goal names | HHS Cyber Gateway | U.S. government | hhscyber.hhs.gov |
| 13 | KEV status, dates added, federal due dates, ransomware use (catalog version 2026.10.16) | Cybersecurity and Infrastructure Security Agency (CISA), via its official kev-data repository | U.S. government | cisa.gov · data |
| 14 | CVE-2026-104935: CWE-290; CVSS 8.6 | NIST National Vulnerability Database | U.S. government | nvd.nist.gov |
| 15 | CVE-2026-102764: CWE-290; CVSS 3.1 9.8 (NVD), CVSS 4.0 9.3 (vendor) | NIST National Vulnerability Database | U.S. government | nvd.nist.gov |
| 16 | CVE-2026-76519: CWE-23; CVSS 9.8 | NIST National Vulnerability Database | U.S. government | nvd.nist.gov |
| 17 | CVE-2023-43208: CVSS 9.8 | NIST National Vulnerability Database | U.S. government | nvd.nist.gov |
| 18 | ICSMA-26-253-01 (Sept 10, 2026): Mirth Connect CVE-2026-82583, CVE-2026-78224; CWE and CVSS; exploitation status | CISA medical device advisory (official CSAF record) | U.S. government | cisa.gov |
| 19 | ICSMA-26-288-02 (Oct 15, 2026): dcm4che CVE-2026-105279, CVE-2026-97851, CVE-2026-105667; CWE and CVSS; exploitation status | CISA medical device advisory (official CSAF record) | U.S. government | cisa.gov |
| 20 | TLP:CLEAR definition; TLP version 2.0 | FIRST (Forum of Incident Response and Security Teams) | Standards body | first.org |
| 21 | Technique names and tactics: T1190, T1133, T1566.001, T1199, T1078, T1210, T1565.001, T1567.002, T1490, T1486 | MITRE ATT&CK Enterprise (each technique linked in Section 3) | Standards body | attack.mitre.org |
| 22 | Weakness names: CWE-290, CWE-502, CWE-306 and CWE-23 checked directly; CWE-89, CWE-611 and CWE-862 as named in CISA's advisory records | MITRE Common Weakness Enumeration | Standards body | cwe.mitre.org |
Appendix B. What is fictional
- The threat actor "COBALT CONDOR" and its motives. Any resemblance to a real group's name is unintended.
- The campaign, its targets (a U.S. academic medical center, partner sites, an IT support provider) and the sequence of events in Section 3.
- The mock severity rating and advisory ID.
- No real organization was attacked, and no indicators of compromise are given.
Everything else is real and sourced in Appendix A: the vulnerabilities, their scores and exploitation status, the ATT&CK techniques, the laws and regulations, and the policy context. These details reflect each source as of October 19, 2026 and may change.