arx_

Something being known doesn’t mean a solution exist.

Computing the the set of Unicode characters that would result in a homograph of a latin alphabet word is non trivial. Now do this for relevant/trusted domains, now put in place a mechanism to mark a domain as trustworthy that also minimises your liability.

It seems likelier than a @google.com spoof landing in the person’s inbox.

Without them providing the headers this is just idle guessing, but I’d argue my guess is likelier to be the truth.

The attacker doesn’t need to spoof anything, this is known as a homograph attack:

https://en.m.wikipedia.org/wiki/IDN_homograph_attack

https://www.xudongz.com/blog/2017/idn-phishing/

Per TFA

Title: I Was Scammed Out of $130,000 — And Google Helped It Happen Heading: Google failed me in two ways Body: Google has become the vault of our digital lives — and that vault had cracks.

If Ford adds seatbelts and you decide to take them off because they annoy you; when get into a crash you can’t claim Ford failed you since the seatbelts weren’t forced upon you more.

Not unless you actually got hired directly by Google. TVCs don’t have the same level of access/responsibility as FTEs. Also, iirc, your contract should state that it’s a breach to represent yourself as a Google employee.