Skip to navigation

Threat reportVulnerabilityTL-2026-1043

Apple 'Hide My Email' Aliases Deanonymizable to Real Email Addresses (Unpatched 1+ Year)

mediumACTIVE

Apple's Hide My Email relay feature (iCloud+) contains an unpatched flaw that lets an attacker with limited technical skill reverse an anonymized alias back to the user's real underlying email address. Researcher Tyler Murphy (EasyOptOuts) reported it to Apple in June 2025 with reproduction steps; as of the July 1, 2026 public disclosure via 404 Media, Apple had not shipped a fix despite claiming in March 2026 that it had been 'addressed in a recent system change.'

Key facts

IdentifiersTL-2026-1043
Also known asHide My Email Deanonymization Bug, iCloud+ Email Relay Identity Leak
SeverityMEDIUM
Affected productsApple Hide My Email (iCloud+)
Weaknesses (CWE)CWE-200
MITRE ATT&CK techniquesT1119 Automated Collection, T1213 Data from Information Repositories, T1566 Phishing, T1566.002 Spearphishing Link, T1585 Establish Accounts, T1585.002 Email Accounts, T1586 Compromise Accounts, T1589 Gather Victim Identity Information, T1589.002 Email Addresses, T1593 Search Open Websites/Domains, T1596 Search Open Technical Databases, T1596.005 Scan Databases and 3 more in the attack flow
MotivationUNKNOWN
Target sectorsconsumer, technology, news - media, civil society, government administration
Target regionsGlobal
Detection rules9 (1 shown free)
Sources7 cited sources

Detection coverage

As of 2026-07-01, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-1043 across Splunk SPL, Microsoft KQL and Sigma, covering 19 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Bulk Hide My Email Alias-Reversal / Data-Broker Lookup Sweep (SPL)

Detects a scripting host (powershell.exe, curl, python3) issuing repeated, tightly-timed outbound calls to a small fixed set of non-corporate lookup/data-broker endpoints while passing word-plus-number email-alias strings (the Hide My Email alias format, e.g. purple-falcon482@icloud.com) as query parameters. This matches the reconnaissance/collection stage of the alias-deanonymization attack chain: an attacker with only 'limited technical skill' (per the reporting researcher) reverses an @icloud.com relay alias to the underlying real address, then cross-references it against a people-search/data-broker service to build a full identity profile. Covers T1596/T1596.005 (Search Open Technical Databases: Scan Databases) and T1589.002 (Gather Victim Identity Information: Email Addresses).

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1596, T1596.005, T1589.002
  • Data sources: proxy, pan:threat, suricata, DeviceNetworkEvents, sysmon_network_connection
  • Severity: medium
  • Confidence: high

Splunk SPL

index=proxy sourcetype="stream:http" OR sourcetype="pan:threat" OR sourcetype="suricata" 
(process_name IN ("powershell.exe","curl","python3","python.exe") OR http_user_agent IN ("curl/*","python-requests/*")) 
uri_query="*alias=*" (uri_query="*icloud.com*" OR uri_query="*relay-lookup*" OR uri_query="*databroker*" OR uri_query="*people-search*") 
| eval alias_token=mvindex(split(uri_query,"alias="),1) 
| rex field=alias_token "(?<candidate_alias>[a-z]+-[a-z]+\d{2,4}@icloud\.com[^&]*)" 
| bin _time span=5m 
| stats count as query_count, dc(candidate_alias) as distinct_aliases, dc(dest_ip) as distinct_dest_ips, values(uri_query) as sample_queries, earliest(_time) as first_seen, latest(_time) as last_seen by src_ip, process_name, _time 
| where query_count > 5 AND distinct_aliases > 2 
| convert ctime(first_seen) ctime(last_seen) 
| table _time, src_ip, process_name, query_count, distinct_aliases, distinct_dest_ips, first_seen, last_seen, sample_queries 
| sort -query_count

Microsoft KQL

let LookupPorts = dynamic([8443,8444]);
DeviceNetworkEvents
| where Timestamp > ago(24h)
| where InitiatingProcessFileName in~ ("powershell.exe","curl.exe","python.exe","python3")
| where RemotePort in (LookupPorts) or RemoteUrl has_any ("mock-relay-lookup","databroker-search","people-search","relay-lookup")
| summarize QueryCount = count(), DistinctRemoteHosts = dcount(RemoteUrl), FirstSeen = min(Timestamp), LastSeen = max(Timestamp) by DeviceName, InitiatingProcessFileName, bin(Timestamp, 5m)
| where QueryCount > 5 and DistinctRemoteHosts >= 2
| project Timestamp, DeviceName, InitiatingProcessFileName, QueryCount, DistinctRemoteHosts, FirstSeen, LastSeen
| order by QueryCount desc

Sigma

title: Bulk Alias-Reversal Lookup Sweep Against Lookup/Data-Broker Endpoints
id: 7a2c1e4d-3f61-4b9a-8e0d-1c9f6a2b5d10
status: experimental
description: Detects a scripting host making repeated bulk queries containing Hide-My-Email-style alias strings against lookup/reversal or data-broker endpoints, consistent with alias-to-identity deanonymization at scale.
references:
  - https://www.404media.co/apple-hide-my-email-vulnerability-reveals-peoples-real-email-addresses/
  - https://attack.mitre.org/techniques/T1596/005/
author: Threadlinqs Team
date: 2026-07-01
tags:
  - attack.reconnaissance
  - attack.t1596.005
  - attack.t1589.002
  - attack.t1596
  - cwe.200
logsource:
  category: network_connection
detection:
  selection:
    Image|endswith:
      - '\powershell.exe'
      - '\curl.exe'
      - '\python.exe'
      - '/curl'
      - '/python3'
    DestinationPort:
      - 8443
      - 8444
  filter_alias_pattern:
    CommandLine|re: '[a-z]+-[a-z]+\d{2,4}@icloud\.com'
  timeframe: 5m
  condition: selection and filter_alias_pattern | count() > 5
falsepositives:
  - Legitimate bulk-alias auditing tools run by the account holder or an authorized privacy service (e.g. EasyOptOuts) performing sanctioned re-testing
  - Internal QA/monitoring scripts validating relay-forwarding health
level: medium

Known false positives:

  • Authorized re-validation testing by the original reporter (EasyOptOuts) or Apple's own QA against the relay
  • Legitimate email-alias management tooling bulk-checking forwarding status for the account owner

Tuning notes: Tune the alias regex to the live Hide My Email word-list pattern (word-word-digits@icloud.com, and later @private.icloud.com once the domain migration ships); adjust the 5m/5-query threshold to your org's baseline proxy volume; exclude known privacy-service IP ranges performing authorized re-testing.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Automated Scan of Open Technical/Relay Databases for Alias Reversal (KQL) · unlock with TL Creds
  • Resolved-Identity Cache Marker Creation Consistent with Recon Persistence (KQL) · unlock with TL Creds
  • Outbound Phishing/Doxxing Delivery Targeting a Newly Deanonymized Real Address (KQL) · unlock with TL Creds
  • Sigma: Automated Bulk Alias-Reversal Query Pattern (Windows/PowerShell) · unlock with TL Creds
  • Sigma: Bulk curl/Python Requests to Local Reversal/Data-Broker Endpoints (Linux) · unlock with TL Creds
  • Sigma: Correlated-Identity Artifact + Phishing-Prep File Naming Pattern · unlock with TL Creds
  • Local Correlated-Identity Artifact Generation Following Alias Lookup (SPL) · unlock with TL Creds
  • Downstream Spearphishing-Prep Artifact Referencing Newly Resolved Real Address (SPL) · unlock with TL Creds

Indicators of compromise

As of 2026-07-01, Threadlinqs Intelligence tracks 19 indicators of compromise for TL-2026-1043.

Sample indicators (3 of 19)

  • URL: hxxps://cybersecuritynews[.]com/apple-hide-my-email-vulnerability/
  • URL: hxxps://www[.]404media[.]co/apple-hide-my-email-vulnerability-reveals-peoples-real-email-addresses/
  • URL: hxxps://discuss[.]privacyguides[.]net/t/apple-hide-my-email-vulnerability-reveals-peoples-real-email-addresses/38930

Defanged, TLP:CLEAR. Full set of 19 indicators: unlock with TL Creds.

19 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

Apple's Hide My Email, part of the iCloud+ subscription bundle, generates random word-plus-number email aliases under the @icloud.com domain (migrating to @private.icloud.com in a planned future change) that forward mail to a user's real address while concealing that address from the site or app the alias was given to. Researcher Tyler Murphy, co-founder of the opt-out service EasyOptOuts, discovered that these aliases can be reversed to recover the underlying real email address with 'limited technical skill.' In limited testing with volunteers, Murphy reported that 100% of Hide My Email addresses tested were exploitable: a newly generated alias was handed to Murphy, who was able to reply with the real email address tied to the Apple account it was supposed to hide.

Murphy reported the issue to Apple in June 2025 with detailed reproduction instructions. Apple acknowledged and began investigating in July 2025. In March 2026, Apple told Murphy the issue had been 'addressed in a recent system change'; Murphy re-tested and found the flaw still fully exploitable. Apple then requested additional information (April 2026) and said it was 'still investigating' (May 2026), asking Murphy not to disclose the issue publicly. In late May 2026 Apple promised a fix 'in the coming weeks.' No fix shipped, and Murphy coordinated disclosure with 404 Media, which independently validated the flaw and published on July 1, 2026, withholding the exact technical reproduction method because the bug remained exploitable at publication time.

Neither 404 Media nor Cyber Security News nor follow-on coverage (AppleInsider, TechCrunch) discloses the precise technical mechanism (e.g., whether it is a metadata leak, a predictable/derivable alias-to-account mapping, an API response disclosure, or a side channel in the mail-forwarding path); this is a deliberate responsible-disclosure omission while the bug remains live. No CVE identifier or CVSS score has been assigned as of this writing. The vulnerability does not itself involve code execution, malware, or data exfiltration in the traditional sense; its impact is deanonymization/identity-correlation, which downstream enables targeted phishing, doxxing, harassment, and account-linkage attacks against users who relied on Hide My Email to compartmentalize their identity (e.g., journalists, activists, domestic-abuse survivors, or privacy-conscious consumers signing up for services with an alias). A separate, related Apple change — migrating newly generated Hide My Email addresses from the shared @icloud.com domain to a dedicated @private.icloud.com domain — is scheduled for the coming weeks and has been criticized by Murphy and press coverage because it will let websites trivially identify and block Hide My Email addresses by domain, further eroding the feature's anonymity value (a related but distinct privacy regression, not the deanonymization bug itself).

MITRE ATT&CK techniques by tactic:

Collection

T1119 Automated Collection; T1213 Data from Information Repositories

Initial Access

T1566 Phishing; T1566.002 Spearphishing Link

Resource Development

T1585 Establish Accounts; T1585.002 Email Accounts; T1586 Compromise Accounts

Reconnaissance

T1589 Gather Victim Identity Information; T1589.002 Email Addresses; T1593 Search Open Websites/Domains; T1596 Search Open Technical Databases; T1596.005 Scan Databases; T1597 Search Closed Sources; T1597.002 Purchase Technical Data; T1598 Phishing for Information

Remediation

Patches

  • No vendor patch has been publicly confirmed or verified as of 2026-07-01; Apple claimed a fix in March 2026 that testing showed was ineffective, and promised another fix 'in the coming weeks' as of late May 2026

Immediate actions

  • Treat existing Hide My Email aliases as potentially linkable to your real email address until Apple confirms a fix
  • High-risk users (journalists, activists, domestic-abuse survivors, executives) should avoid relying on Hide My Email as a sole anonymity control for sensitive signups
  • Monitor accounts tied to Hide My Email aliases for unusual phishing or credential-stuffing attempts, since a leaked real address can be used for targeted follow-on attacks
  • Where possible, pair Hide My Email aliases with a secondary, unrelated real mailbox not otherwise exposed, to reduce blast radius if the alias is deanonymized

Workarounds

  • Assume any existing Hide My Email alias may be reversible to the real address and avoid using it for accounts where identity exposure carries high risk
  • Use alternate/third-party email alias or forwarding services with a demonstrated non-reversible design for sensitive signups

Longer-term hardening

  • Apple should ship and confirm a verified fix to the alias-to-identity reversal flaw, not just an internal 'system change' claim
  • Independent re-validation of any Apple-issued fix by the original reporter (EasyOptOuts) or a third party before considering the issue resolved
  • Apple should reconsider the @private.icloud.com domain migration, which trades deanonymization risk for trivial alias-blocking by third-party sites
  • Users should diversify email-alias providers (e.g., SimpleLogin, Firefox Relay, AnonAddy) rather than depending on a single vendor's alias implementation

Affected and fixed versions

  • Apple — Hide My Email (iCloud+)
    Vulnerable versions: all Hide My Email aliases as of 2026-07-01

Timeline

  • Tyler Murphy (EasyOptOuts co-founder) discovers the Hide My Email deanonymization flaw and reports it to Apple with detailed reproduction instructions.
  • Apple acknowledges the report and states it is investigating the issue.
  • Apple tells Murphy the issue has been 'addressed in a recent system change'; Murphy re-tests and confirms the vulnerability is still fully exploitable.
  • Apple requests additional information from Murphy and states it is performing further checks.
  • Apple tells Murphy it is 'still investigating' the issue and asks him not to disclose it publicly; Murphy proposes Apple halt Hide My Email sales until a fix ships.
  • Apple promises a security update addressing the issue is 'expected in the coming weeks.'
  • Apple issues a domain-consolidation notice stating that newly generated Hide My Email addresses and Sign in with Apple relay addresses (currently under privaterelay.appleid.com) will both migrate to the shared private.icloud.com domain; existing addresses on legacy domains continue to work.
  • TechCrunch and Help Net Security report on the planned @private.icloud.com domain consolidation, noting it removes source ambiguity and could let third-party sites trivially identify and block Hide My Email/Sign in with Apple relay addresses.
  • 404 Media confirms the deanonymization exploit remains fully active and unpatched as of this date, immediately prior to publication.
  • 404 Media (journalist Joseph Cox) publishes the vulnerability with Murphy's account, withholding exact technical details because the flaw remains exploitable; Cyber Security News, AppleInsider, and other outlets pick up coverage the same day. No fix has shipped and no CVE has been assigned.

Sources cited

Previous and next in vulnerability

Drafted by the Threadlinqs research pipeline from 7 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats