Introduction
The Federal Trade Commission (FTC), along with Utah and California, has initiated legal action against telehealth provider Him & Hers. The allegations center on the company's business and data sharing practices, specifically claims that sensitive health information was disclosed to third parties without user consent or adequate safeguards. For security practitioners in the healthcare sector, this is a critical indicator of active regulatory scrutiny regarding "shadow data sharing." This is not merely a compliance paperwork issue; it represents a failure in data governance that results in the unauthorized exfiltration of Protected Health Information (PHI). Defenders must immediately audit their web and mobile applications for third-party data leaks that violate the HIPAA Security and Privacy Rules.
Technical Analysis
While this incident stems from a business practice, the technical mechanism of compromise involves the integration of third-party tracking, advertising, and analytics SDKs within web and mobile applications.
- Affected Platforms: Telehealth web portals and mobile applications (iOS/Android). The specific targets in this news item are the customer-facing interfaces used by Him & Hers.
- Attack Vector (Data Leakage): The vulnerability lies in the improper implementation of third-party JavaScript pixels and SDKs (e.g., Meta Pixel, Google Analytics) within patient appointment and checkout workflows. These scripts often capture Personally Identifiable Information (PII) and PHI (e.g., medication types, conditions) from form inputs or URL parameters and transmit them via HTTP/HTTPS to external endpoints.
- Exploitation Status: This is currently an active enforcement vector. The FTC is treating these configurations as unfair/deceptive trade practices. There is no CVE associated with this specific lawsuit, as it is a logic/privacy control failure rather than a software vulnerability.
- Impact: Unauthorized disclosure of PHI to third parties (data brokers/advertisers) lacking a Business Associate Agreement (BAA), resulting in regulatory fines and reputational damage.
Detection & Response
Detecting unauthorized data sharing requires monitoring outbound traffic from your web servers or client-side applications for known third-party tracking domains that have no business relationship (BAA) with your organization.
SIGMA Rules
---
title: Potential Telehealth PHI Leakage to Marketing Domains
id: 8a4b2c1d-9e3f-4a5b-b6c7-1d2e3f4a5b6c
status: experimental
description: Detects outbound web traffic from telehealth applications to known advertising/analytics domains which may capture PHI without a BAA.
references:
- https://www.ftc.gov/reports/ftc-staff-report-companies-use-and-disclosure-claims-consumer-health-information
author: Security Arsenal
date: 2026/05/15
tags:
- attack.exfiltration
- attack.t1567.002
logsource:
category: webserver
product: apache
detection:
selection:
cs-method:
- 'GET'
- 'POST'
cs-host|contains:
- 'facebook.com'
- 'google-analytics.com'
- 'doubleclick.net'
- 'tiktok.com'
- 'connect.facebook.net'
cs-uri-query|contains:
- 'email='
- 'phone='
- 'medication='
- 'condition='
condition: selection
falsepositives:
- Legitimate marketing traffic authorized by BAA
level: high
---
title: High Volume Data Exfiltration to Non-Medical External Endpoints
id: 9c5d3e2f-0f4a-5b6c-7d8e-9f0a1b2c3d4e
status: experimental
description: Identifies suspicious high-volume POST requests from internal web servers to unknown external IPs, characteristic of data syncing to CRM/Analytics clouds.
references:
- https://attack.mitre.org/techniques/T1041/
author: Security Arsenal
date: 2026/05/15
tags:
- attack.exfiltration
- attack.t1041
logsource:
category: network_connection
product: windows
detection:
selection:
Initiated: 'true'
DestinationPort: 443
DestinationIp|startswith:
- '0.0.0.0' # Placeholder for exclusion of internal CIDR
filter:
DestinationHostname|endswith:
- '.hospital.local'
- '.medical-domain.com'
timeframe: 5m
condition: selection | count() > 50 and not filter
falsepositives:
- Legitimate high-traffic API calls to approved partners
level: medium
KQL (Microsoft Sentinel)
// Hunt for telehealth app traffic connecting to known high-risk tracking domains
let HighRiskDomains = dynamic(["facebook.com", "google-analytics.com", "doubleclick.net", "tiktok.com", "analytics.tiktok.com", "bat.bing.com"]);
DeviceNetworkEvents
| where InitiatingProcessFileName in~("chrome.exe", "firefox.exe", "msedge.exe", "safari.exe")
| where RemoteUrl has_any (HighRiskDomains)
| project Timestamp, DeviceName, InitiatingProcessAccountName, RemoteUrl, RequestURL, SentBytes, ReceivedBytes
| order by Timestamp desc
Velociraptor VQL
-- Hunt for browser processes connecting to ad-tech domains from telehealth workstations
SELECT
Pid,
Name,
Username,
concat(Split(RemoteAddr, ":")[0]) as RemoteIP,
RemotePort
FROM netstat()
WHERE Name =~ "chrome" OR Name =~ "firefox" OR Name =~ "msedge"
AND RemotePort IN (443, 80)
-- Regex to match common ad/tracking hostnames if resolved (requires DNS cache lookup or enrichment)
Remediation Script (PowerShell)
This script scans IIS log files for requests containing sensitive keywords directed to external third-party domains.
# Audit IIS Logs for Potential PHI Leakage to Third Parties
param(
[string]$LogPath = "C:\inetpub\logs\LogFiles\",
[string[]]SensitiveKeywords = @("email", "phone", "ssn", "condition", "prescription"),
[string[]]BlockedDomains = @("facebook", "google-analytics", "doubleclick", "tiktok")
)
$LogFile = Get-ChildItem -Path $LogPath -Recurse -Filter "u_ex*.log" | Sort-Object LastWriteTime -Descending | Select-Object -First 1
if ($LogFile) {
Write-Host "Scanning recent log file: $($LogFile.FullName)"
Select-String -Path $LogFile.FullName -Pattern $SensitiveKeywords |
Where-Object {
$BlockedDomains | Where-Object { $_ -and $_.Length -gt 0 } | ForEach-Object {
$_.toLower()
} | Where-Object { $_ -and $_.Length -gt 0 } | ForEach-Object {
$line = $_; if ($_.Line -match $line) { return $true } }
} |
ForEach-Object {
$fields = $_.Line.Split(" ")
[PSCustomObject]@{
Date = $fields[0] + " " + $fields[1]
IP = $fields[8]
Method = $fields[3]
UriStem = $fields[4]
UriQuery = $fields[5]
UserAgent = $fields[9]
MatchedLine = $_.Line.Trim()
}
} | Export-Csv -Path "C:\Temp\PHI_Leak_Report.csv" -NoTypeInformation
Write-Host "Scan complete. Results saved to C:\Temp\PHI_Leak_Report.csv"
} else {
Write-Host "No log files found in $LogPath"
}
Remediation
Immediate defensive actions are required to align with FTC expectations and HIPAA regulations:
- Inventory Third-Party Trackers: Conduct a comprehensive audit of all website and mobile application scripts. Identify every SDK, pixel, and tag (e.g., Google Tag Manager, Meta Pixel).
- Verify Business Associate Agreements (BAAs): Ensure every vendor receiving PHI (even inadvertently via tracking pixels) has signed a compliant BAA. If they will not sign a BAA, they cannot receive PHI.
- Implement Data Masking: Configure tracking scripts to explicitly exclude PII/PHI. Use "hashed" emails or none at all. Ensure sensitive form fields are not automatically captured by "automatic event tracking" features.
- Network Segmentation: Restrict outbound internet access for production web servers to only necessary whitelisted endpoints (e.g., payment gateways, medical APIs). Block access to known advertising and data broker domains.
- Consent Management: Deploy a robust Consent Management Platform (CMP) that strictly respects user opt-outs and prevents the loading of marketing scripts without explicit affirmative consent.
- Regular Penetration Testing: Engage in Blue Team exercises specifically targeting data privacy logic to test for unauthorized data exfiltration via hidden parameters or cookies.
Related Resources
Security Arsenal Healthcare Cybersecurity AlertMonitor Platform Book a SOC Assessment healthcare Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.