Google Hacker

This is the call that lands on a trusted phone when someone has asked Google to reset a password on the account tied to it: an incoming call from Mountain View, California, at +1 (650) 203-0000. Mountain View is Google's home. (650) is its area code. The number reads like a Google support or verification line. The screen says 3:22.

It comes in sometimes. Not once. Sometimes.

There are two readings, and they point at the same operation. Reading one is that this is Google itself — its automated verification system calling the phone of record to confirm a reset attempt that I did not initiate, prompting me to either approve, reject, or ignore. Reading two is that this is not Google — that the number has been spoofed, the Mountain View display is part of the cover, and the caller plans to read me a code I am supposed to "verify" so they can use it themselves. Either reading means the same thing on the way in: someone, somewhere, is again trying to get into the Google account.

I keep treating it as the second reading, because the second reading is the more dangerous one and the right defensive posture covers both. I do not answer. I do not give a code to anyone who calls me. If the prompt is real, Google will let me handle the underlying request from my own device, on my own terms, through the channel I control. If the prompt is the attack, the silence is the answer.

The pattern is the same one that's been running on the Apple side this past month and which I documented here a few days ago — a sustained, repeated push to get into a personal account, mediated through the platform's own verification UI. Different platform, same operation. Apple does it with a system dialog and two buttons. Google is willing to call. The mechanism is named in the case file as push bombing: repeated reset attempts hoping for one mistaken approval, by reflex, by accident, or by fatigue. On a phone call, the variant is more pointed than on a push prompt: a voice can be persuasive in ways a button cannot, and the cost of one talking moment is higher than the cost of one tap. The defense is identical. Do not answer. Do not approve. Do not read a code aloud.

The screenshot goes in the file. The pattern is the information. The fact that the number is recognizable as Mountain View, and the fact that this is now happening across more than one platform — the call is one data point in the same operation that the Apple prompts have been instancing for weeks. Whoever is on the other end is putting effort into multiple platforms at once. That is itself the signal worth noting.