Post:
P1 / SEV-1 — URGENT SECURITY AND PRIVACY DESIGN ISSUE
iOS Messages contains a potentially dangerous behavior in its “Stop or Report Spam” → “Delete and Stop” workflow: selecting this option sends an outbound STOP message to the sender.
This creates a serious phone-number enumeration and validation risk.
The threat is not limited to conventional scams. Some spam operators are not initially trying to defraud the recipient. Their objective is simply to determine whether a telephone number is active, monitored, and associated with a real person. Any response—including STOP—can provide that confirmation. Validated numbers can then be retained, sold, shared, or targeted with additional spam, phishing attempts, and fraudulent campaigns.
This is particularly concerning because users may believe they are simply reporting and deleting unwanted messages. Instead, the operating system can initiate an outbound communication with the very sender they are attempting to avoid.
Security concerns:
- An unsolicited outbound response can confirm that a number is active and monitored.
- Users may trigger this behavior without understanding its security implications.
- Reporting spam should not require communicating with the suspected spammer.
- The reporting workflow should not override an existing block or otherwise initiate contact with a blocked sender.
- Blocking may be bypassed: Even when the sender has already been blocked, selecting “Delete and Stop” will override the block and still transmit an outbound STOP message to that sender. This appears to undermine the user's explicit decision to prevent further contact and potentially re-establish communication with a blocked number.
Expected behavior: Reporting and deleting suspected spam should be entirely passive. Apple should not transmit any message to the sender as part of that process without explicit, informed consent.
Requested action:
- Immediately disable “Delete and Stop” as a temporary mitigation pending security and privacy review.
- Escalate this issue to the iOS Messages engineering and Product Security teams.
- Review the outbound-message behavior, including interactions with blocked senders.
- Separate spam reporting, deletion, blocking, and subscription cancellation into distinct actions.
This is not merely a UI concern. It is a potentially systemic privacy vulnerability in a core operating-system messaging workflow, exposing users to further targeting precisely when they are attempting to protect themselves. - Investigate why the “Delete and Stop” workflow can transmit a message to a sender who is already blocked, and ensure that no spam-reporting action can override an existing block.
Requesting urgent engineering review and confirmation that this has been escalated.
See both screenshots attached.
Thanks