Pull down to refresh stories
Emerging

Apple’s Hide My Email feature has a bug that’s been exposing real email addresses, researcher claims

The bug was reported by 404 Media , which says that it has tested and verified that the vulnerability exists. Tyler Murphy, the researcher who found the bug, said that he warned Apple about the problem over a year ago and that it was unclear why the company had yet to remedy the problem. This piece sits on 1 source layers, but the real value is showing why the story should not be skimmed past too quickly.

The bug was reported by 404 Media , which says that it has tested and verified that the vulnerability exists. Tyler Murphy, the researcher who found the bug, said that he warned Apple about the problem over a year ago and that it was unclear why the company had yet to remedy the problem. The signal is strong enough to deserve attention, but it still needs to be read as something developing rather than fully settled.

Emerging The topic has initial corroboration, but the newsroom is still waiting on stronger confirmation.
Reference image for: Apple’s Hide My Email feature has a bug that’s been exposing real email addresses, researcher claims
Reference image from TechCrunch. TechCrunch

The bug was reported by 404 Media , which says that it has tested and verified that the vulnerability exists. Tyler Murphy, the researcher who found the bug, said that he warned Apple about the problem over a year ago and that it was unclear why the company had yet to remedy the problem. All of the attempts to exploit the bug have been successful, Murphy added. TechCrunch is the main source layer for now, and the rest should be read as a signal that is still widening. Changes like this often look small on screen while shifting product habits and day-to-day operating workflows much faster than expected.

What is happening now

The bug was reported by 404 Media , which says that it has tested and verified that the vulnerability exists. TechCrunch form the main source layer behind the core facts in this piece. This is still a developing thread, so the useful part is knowing which source signals are hardening and which ones still need caution. In software, the upgrades worth caring about are the ones that make workflows cleaner, reduce mistakes, and remove the need for extra tools.

Where the sources line up

TechCrunch is the main source layer for now, and the rest should be read as a signal that is still widening. Tyler Murphy, the researcher who found the bug, said that he warned Apple about the problem over a year ago and that it was unclear why the company had yet to remedy the problem. TechCrunch form the main source layer behind the core facts in this piece.

The details worth keeping

All of the attempts to exploit the bug have been successful, Murphy added. Changes like this often look small on screen while shifting product habits and day-to-day operating workflows much faster than expected. The people who feel the value first are often operators, editors, creators, and teams stitching multiple apps into one daily workflow. The next step is to see whether the current signals harden into a durable change or fade as a short-lived experiment.

Why this matters most

The signal is strong enough to deserve attention, but it still needs to be read as something developing rather than fully settled. With 1 source layers on the table, the part worth reading most closely is where firm facts meet the market's early reaction. “We don’t know the full scope of the issue, but in our limited tests with volunteers, 100% of Hide My Email addresses were exploitable,” Murphy told the outlet.

What to watch next

The next thing to watch is rollout speed, regional limits, and whether the update really changes day-to-day habits. Patrick Tech Media will keep checking rollout speed, user reaction, and how TechCrunch update the next pieces. From 1 early signals, the piece keeps 1 references that are useful for locking the main details in place. That is why the useful reading move is not to stop at the headline, but to compare the promise, the workflow change, and the likely cost before deciding anything.

Source notes