Threat reportPhishingTL-2026-0393
Abuse of Apple Account Change Notifications to Deliver Callback Phishing from appleid@id.apple.com (Operation iPhone Purchase Scam, April 2026)
Threat actors are weaponizing Apple's legitimate Apple Account change notification system to deliver callback phishing (TOAD) lures from appleid@id.apple.com. By embedding a fake $899 iPhone/PayPal purchase message and a scammer-controlled phone number into the first and last name fields of an attacker-owned Apple ID, then modifying shipping information to trigger a security alert, attackers cause Apple's infrastructure (IP 17.111.110.47) to send the phishing content to targets with valid SPF, DKIM, and DMARC.
Key facts
| Identifiers | TL-2026-0393 |
|---|---|
| Also known as | Apple ID Notification Phish, iPhone 899 PayPal Scam, Operation Apple Account Alert Abuse, Apple appleid@id.apple.com Abuse Campaign |
| Severity | HIGH |
| Affected products | Apple Apple ID (iCloud) Account Notification System; Apple id.apple.com / appleid.apple.com account management; Apple iCloud Mail outbound relay (outbound.mr.icloud.com) |
| Weaknesses (CWE) | CWE-20, CWE-79, CWE-451, CWE-290 |
| Tools | AnyDesk, ScreenConnect, TeamViewer, UltraViewer, callback_phishing_call_center |
| MITRE ATT&CK techniques | T1005 Data from Local System, T1036 Masquerading, T1056 Input Capture, T1102 Web Service, T1199 Trusted Relationship, T1204 User Execution, T1219 Remote Access Tools, T1539 Steal Web Session Cookie, T1566 Phishing, T1583 Acquire Infrastructure, T1585 Establish Accounts, T1587 Develop Capabilities and 5 more in the attack flow |
| Motivation | FINANCIAL |
| Target sectors | consumer, technology, financial, healthcare, government, education, retail |
| Target regions | North America, Europe, Asia-Pacific, Global |
| Detection rules | 9 (1 shown free) |
| Sources | 10 cited sources |
Detection coverage
As of 2026-04-20, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-0393 across Splunk SPL, Microsoft KQL and Sigma, covering 23 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: Apple Account Change Notification With TOAD Lure In From Display Name — Exploitation Phase (SPL)
Detects inbound Apple account change notifications from appleid@id.apple.com (or any @id.apple.com sender) whose RFC 5322 From display-name contains phone-number, currency, or TOAD-keyword patterns (purchase, cancel, pay-pal, paypal, iphone, refund, support), even when SPF/DKIM/DMARC all pass. Targets the TL-2026-0393 abuse primitive where attacker-controlled Apple ID name fields render verbatim into legitimate Apple notifications.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1566, T1566.002, T1566.004, T1656, T1036.005
- Data sources: o365_message_trace, proofpoint_tap, mimecast_email, exchange_transport, email_gateway
- Severity: high
- Confidence: high
Splunk SPL
index=email sourcetype="ms:o365:reports:messagetrace" OR sourcetype="proofpoint:tap:message" OR sourcetype="mimecast:email:receipt" OR sourcetype="mail" sender_address="*@id.apple.com"
| eval from_display=coalesce(from_display_name, sender_display_name, header_from_display)
| eval spf_pass=if(match(lower(auth_results), "spf=pass"), 1, 0)
| eval dkim_pass=if(match(lower(auth_results), "dkim=pass"), 1, 0)
| eval dmarc_pass=if(match(lower(auth_results), "dmarc=pass"), 1, 0)
| eval phone_in_name=if(match(from_display, "\d{7,}"), 1, 0)
| eval currency_in_name=if(match(lower(from_display), "(\$\s*\d+|\d+\s*usd|\d+\s*eur|\d+\s*gbp)"), 1, 0)
| eval toad_keyword=if(match(lower(from_display), "(purchase|cancel|pay-pal|paypal|iphone|refund|support)"), 1, 0)
| eval score=(3*(spf_pass+dkim_pass+dmarc_pass>=2)) + (2*phone_in_name) + (2*currency_in_name) + toad_keyword
| where phone_in_name=1 OR currency_in_name=1 OR toad_keyword=1
| table _time, sender_address, recipient_address, from_display, subject, auth_results, score
| sort - score, - _timeMicrosoft KQL
EmailEvents
| where TimeGenerated > ago(24h)
| where SenderFromAddress endswith "@id.apple.com"
| extend Display = tostring(parse_json(tostring(AdditionalFields)).FromDisplayName)
| extend Display = iif(isempty(Display), SenderDisplayName, Display)
| extend PhoneInName = iif(Display matches regex @"\d{7,}", 1, 0)
| extend CurrencyInName = iif(Display matches regex @"(?i)(\$\s*\d+|\d+\s*(USD|EUR|GBP))", 1, 0)
| extend ToadKeyword = iif(Display matches regex @"(?i)(purchase|cancel|pay-?pal|iphone|refund|support)", 1, 0)
| extend AuthAllPass = iif(AuthenticationDetails contains "spf=pass" and AuthenticationDetails contains "dkim=pass" and AuthenticationDetails contains "dmarc=pass", 1, 0)
| where PhoneInName == 1 or CurrencyInName == 1 or ToadKeyword == 1
| project TimeGenerated, SenderFromAddress, RecipientEmailAddress, Display, Subject, AuthenticationDetails, AuthAllPass, PhoneInName, CurrencyInName, ToadKeyword
| order by TimeGenerated descSigma
title: Apple Account Change Notification With TOAD Lure In From Display Name
id: 3a1f7b0e-0393-4a2a-8c1d-apple-toad-2026a
status: experimental
description: Detects inbound Apple account change notifications where the From display-name contains phone-number, currency, or TOAD-keyword patterns typical of the TL-2026-0393 abuse pattern, even when SPF, DKIM, and DMARC all pass.
references:
- https://www.bleepingcomputer.com/news/security/apple-account-change-alerts-abused-to-send-phishing-emails/
- https://attack.mitre.org/techniques/T1566/002/
- https://attack.mitre.org/techniques/T1566/004/
author: Threadlinqs Team
date: 2026/04/20
tags:
- attack.initial_access
- attack.t1566
- attack.t1566.002
- attack.t1566.004
- attack.t1656
- attack.t1036.005
logsource:
product: email
category: mail
detection:
sender:
from|endswith: '@id.apple.com'
lure_phone:
from_display_name|re: '\d{7,}'
lure_currency:
from_display_name|re: '(?i)(\$\s*\d+|\d+\s*(USD|EUR|GBP))'
lure_keyword:
from_display_name|contains:
- 'purchase'
- 'cancel'
- 'pay-pal'
- 'paypal'
- 'iphone'
- 'refund'
- 'support'
condition: sender and (lure_phone or lure_currency or lure_keyword)
fields:
- from
- from_display_name
- auth_results
- recipient
falsepositives:
- Legitimate Apple marketing notifications with rare numeric tokens in the display name
- Multilingual Apple notifications where brand words (support) appear in translated templates
level: high
Known false positives:
- Legitimate Apple marketing or localized notifications that happen to contain brand-related tokens in the display name
- Internal security awareness phishing simulations that replay Apple notification templates
Tuning notes: Start in audit/alert-only mode for 7 days. Tune the toad_keyword regex based on organization-specific false-positive terms (for example, remove 'support' if you observe heavy legitimate Apple support mail volume). Consider raising the score threshold to require at least two lure matches (phone + keyword) in high-volume environments. Allowlist any known-good Apple marketing sender subdomains via an exclusion macro.
- Apple Account Change Notification With TOAD Lure In From Display Name — Exploitation Phase (KQL) · unlock with TL Creds
- RMM Binary Dropped In Downloads With HKCU Run Or Scheduled Task Persistence — Post-Exploitation (KQL) · unlock with TL Creds
- Browser-Spawned Remote Access Software Launch Following Apple Account Notification — C2/Lateral Movement (KQL) · unlock with TL Creds
- Apple Account Change Notification Envelope-To Vs Final-Delivery Mismatch — Exploitation Phase (Sigma) · unlock with TL Creds
- Linux Crontab @reboot Persistence Pointing To Recently Downloaded Remote Access Binary — Post-Exploitation (Sigma) · unlock with TL Creds
- Cross-Platform Remote Access Software Execution With Browser/Explorer Parent — C2/Lateral Movement (Sigma) · unlock with TL Creds
- RMM Tool Dropped to Downloads With HKCU Run or User Scheduled Task Persistence — Post-Exploitation (SPL) · unlock with TL Creds
- Browser-Spawned Remote Access Software Launch Following Apple Account Notification — C2/Lateral Movement (SPL) · unlock with TL Creds
Indicators of compromise
As of 2026-04-20, Threadlinqs Intelligence tracks 23 indicators of compromise for TL-2026-0393.
Sample indicators (3 of 23)
- IP address:
17.111.110[.]47 - Domain:
id[.]apple[.]com - Domain:
email[.]apple[.]com
Defanged, TLP:CLEAR. Full set of 23 indicators: unlock with TL Creds.
Technical analysis
The campaign is active as of mid-April 2026 and bypasses most email gateways because the messages are genuinely originated from Apple-owned mail servers.
In April 2026, BleepingComputer reported and independently reproduced an active phishing campaign in which threat actors abuse Apple's transactional 'Apple Account change' notification system to deliver callback phishing (Telephone-Oriented Attack Delivery, TOAD) lures inside fully legitimate, authenticated email messages sent from Apple's own infrastructure. Because the messages originate from appleid@id.apple.com, are sent through Apple's outbound relay outbound.mr.icloud.com from Apple-owned IP 17.111.110.47, and pass SPF, DKIM (header.d=id.apple.com), and DMARC authentication checks, most secure email gateways (SEG), O365/Exchange Online Protection, Google Workspace Gmail filters, and Proofpoint/Mimecast/Abnormal solutions treat the message as trustworthy and deliver it directly to the user's inbox.
The abuse chain is simple and requires only a free Apple ID: (1) The attacker registers or hijacks an Apple ID using a disposable iCloud address (observed example: hxfedna24005@icloud.com); (2) the attacker inserts their callback phishing content into the account's 'First name' and 'Last name' personal information fields, splitting the message across both because neither field accepts the full payload in isolation (observed lure text: 'Dear User 899 USD iPhone Purchase Via Pay-Pal To Cancel 18023530761'); (3) the attacker modifies the shipping address on the account, which causes Apple to automatically generate and send an 'account information update' security notice; (4) because Apple's template renders the attacker-controlled first/last name fields verbatim into the email body, the phishing payload is delivered inside a legitimate-looking Apple security alert; (5) the email is sent first to the attacker's own Apple ID inbox, but header analysis (rn2-txn-msbadger01107.apple.com -> outbound.mr.icloud.com) shows the final delivery address is a distributed list of targets, indicating the attacker uses a mailing list or forwarding to fan the single Apple-originated notification out to many victims. The original recipient field (the attacker-owned iCloud address) is preserved inside the message, which reinforces the social engineering lure because the victim sees an unfamiliar iCloud address and believes their account has been taken over.
The lure itself is a callback/TOAD scam: victims are instructed to call the embedded number (18023530761 observed) to dispute a fraudulent $899 iPhone/PayPal purchase. A live human on the other end of the call, typically operating from a call center, walks the victim through installing remote access software (AnyDesk, TeamViewer, ScreenConnect, UltraViewer), through which the attacker drains bank accounts, captures MFA codes, installs persistence/RMM malware, and/or extracts further PII. The pattern mirrors prior 2024-2026 callback phishing campaigns observed from PayPal, Geek Squad, and Norton/McAfee scams, and it is a direct evolution of earlier 2022 and 2025 abuse of iCloud Calendar invitations and Apple Event RSVPs that likewise exploited Apple's trusted sending infrastructure. The same trust abuse primitive has been observed in Microsoft Azure Monitor alert abuse and Google Drive/Docs share-notification abuse — all rely on the premise that content user-controllable at the source will be rendered verbatim into an outbound notification signed by a trusted brand.
Impact is significant because (a) Apple's sending IP reputation is effectively unblockable for any organization whose users have personal Apple IDs, (b) SEG content filters struggle to distinguish legitimate Apple notifications from abusive ones when the only difference is a few tokens inside the name fields, and (c) the lure exploits the strongest possible authority/urgency signal (unauthorized account change alert + unauthorized $899 purchase). BleepingComputer reported the abuse to Apple on Friday, 2026-04-18, and at time of publication received no response; abuse remains possible. Defenders should add detection logic that parses inbound Apple account change notifications for high-entropy or phone-number patterns in the rendered 'Name' field, flag Apple notifications addressed to an iCloud address that does not belong to the recipient, and instrument endpoint telemetry for RMM/remote-access tool launches that follow a user call to an embedded phone number.
MITRE ATT&CK techniques by tactic:
Collection
Defense Evasion
T1036 Masquerading; T1684.001 Impersonation
Credential Access
T1056 Input Capture; T1539 Steal Web Session Cookie
Command and Control
T1102 Web Service; T1219 Remote Access Tools
Initial Access
T1199 Trusted Relationship; T1566 Phishing
Execution
Resource Development
T1583 Acquire Infrastructure; T1585 Establish Accounts; T1587 Develop Capabilities; T1588 Obtain Capabilities
Reconnaissance
T1589 Gather Victim Identity Information; T1598 Phishing for Information
Impact
Remediation
Patches
- No software patch — mitigation must come from Apple. Recommended Apple-side fixes: reject phone-number and dollar-amount patterns in Apple ID name fields; rate-limit shipping-address change notifications per account; display Apple ID display-name fields in a distinct visual container in outgoing templates; warn recipients when the notification's recipient-of-record differs from the final inbox delivery address
Immediate actions
- Instruct users to never call phone numbers embedded inside account notification emails; always navigate directly to appleid.apple.com or the Apple Support app to verify alerts
- Add a mail-flow rule to flag inbound messages from appleid@id.apple.com where the subject contains 'Apple Account' AND the body contains a phone number, a dollar amount, or keywords such as 'purchase', 'cancel', 'pay-pal', 'iphone', 'support' in the rendered name field
- Block or quarantine inbound messages from appleid@id.apple.com when the final recipient's iCloud address does not match the organization's known Apple ID inventory
- Submit abuse reports to reportphishing@apple.com and phishing-report@us-cert.gov with full raw headers; the victim's Mail client 'Report Junk' will forward to Apple
- Alert end users via short awareness bulletin that phishing lures are now arriving inside genuine, SPF/DKIM/DMARC-valid Apple emails
Workarounds
- On Apple Mail, enable 'Protect Mail Activity' and 'Hide My IP' so callback redirect attempts and tracking pixels are blunted
- End users: if an Apple notification references an iCloud address you do not own, treat it as hostile and report to Apple via the Mail 'Report Junk' action
- Blue team: enrich inbound Apple mail with a banner warning when body contains keywords ('purchase', 'PayPal', 'cancel', 'USD', phone-number regex) combined with display-name rendered text
Longer-term hardening
- Deploy anti-callback-phishing detection (Abnormal, Material, Sublime, Proofpoint TAP) that parses message body semantic intent rather than relying purely on sender authentication
- Add EDR detection for user-initiated downloads of remote-access tooling (AnyDesk, TeamViewer, ScreenConnect, UltraViewer, LogMeIn Rescue) within 60 minutes of inbound mail matching this signature
- Configure SEG to normalize and inspect message 'To' header mismatch: original envelope-to vs. final delivery recipient
- Add Detection-as-Code rule for Apple notification emails where rendered display-name field contains any digit sequence of length >= 7 (phone number heuristic)
- Create user-awareness training module specifically on 'trusted-brand notification abuse' covering Apple, Microsoft Azure, Google Workspace, and DocuSign pattern
Affected and fixed versions
- Apple — Apple ID (iCloud) Account Notification System
Vulnerable versions: all (service-side)
Fixed in: pending vendor response as of 2026-04-19 - Apple — id.apple.com / appleid.apple.com account management
Vulnerable versions: all (service-side) - Apple — iCloud Mail outbound relay (outbound.mr.icloud.com)
Vulnerable versions: all
Timeline
- Early precedent: threat actors abuse iCloud Calendar invitations to deliver phishing lures through Apple's legitimate servers (trust-abuse primitive established).
- Refreshed iCloud Calendar invite phishing wave resurfaces, demonstrating continued effectiveness of Apple trusted-sender abuse vectors.
- First observed abusive Apple account change notification in the wild; a BleepingComputer reader receives an email from locked-ioc-5 timestamped '2026-04-14 at 7:01:40 PM GMT' containing the phishing lure 'Dear User 899 USD iPhone Purchase Via Pay-Pal To Cancel 18023530761' embedded in the account-holder name field.
- BleepingComputer reproduces the abuse by creating a test Apple ID, inserting callback-phishing text across the first and last name fields, and modifying the shipping address to trigger an outbound notification.
- BleepingComputer contacts Apple regarding the abuse on Friday, 2026-04-18. No vendor response received by publication.
- Abuse remains exploitable; no Apple-side mitigation deployed. Campaign is assessed as ongoing and likely scaling via mailing-list fanout.
- BleepingComputer publishes public disclosure of the abuse campaign, including full email header excerpt, reproduction steps, and sending infrastructure details.
- Threadlinqs Intelligence publishes TL-2026-0393 with detection coverage and simulation data.
- As of 2026-05-29, this Apple Account-change callback-phishing (TOAD) abuse remains a live concern: it requires an Apple server-side fix, not a software patch, and reporting (BleepingComputer, Malwarebytes, TechRadar) confirms Apple had not responded and the name-field injection abuse stayed exploitable. No vendor mitigation has surfaced and callback/TOAD fraud is still surging, so it stays ACTIVE.
Sources cited
- CISA - Avoiding Social Engineering and Phishing Attacks (ST04-014) CISA · Government advisory · 2026-04-19
- Apple - Recognize and avoid phishing messages, phony support calls, and other scams (official) Apple · Vendor report · 2026-04-19
- Apple - Report spam or phishing emails to Apple Apple · Vendor report · 2026-04-19
- Proofpoint - Understanding Telephone-Oriented Attack Delivery (TOAD) callback phishing Proofpoint · Research · 2024-06-12
- MITRE ATT&CK - T1566.002 Phishing: Spearphishing Link MITRE · Research · 2026-04-19
- MITRE ATT&CK - T1598 Phishing for Information MITRE · Research · 2026-04-19
- MITRE ATT&CK - T1219 Remote Access Software MITRE · Research · 2026-04-19
- FBI IC3 - 2025 Internet Crime Report: Tech Support / Callback Fraud ic3.gov · Research · 2026-03-15
- BleepingComputer - Apple account change alerts abused to send phishing emails BleepingComputer · News · 2026-04-19
- BleepingComputer - iCloud Calendar invites abused to phish Apple users (prior abuse pattern) BleepingComputer · News · 2025-09-10
Previous and next in phishing
Drafted by the Threadlinqs research pipeline from 10 sources; published ; last updated —.