Google

WHOA @google let me know they saw my tweet last year & built a tool to defend against that exact call spoofing + AI voice clone attack!

As of today, fake call detection on Android alerts when someone is impersonating your contact. Here's what it looks like:

Ok, so how does fake call detection work?!

1. Attacker impersonates your contact by spoofing their number + voice cloning to steal your money, data, access, etc.

2. Your device knows your real contact’s 'digital handshake' confirmation signal, so when it’s missing, it notices.

3. If it’s missing, your device pings your contact's actual device to double-check their device is placing the call. If their real device says, "I'm not making a call right now," you'll get a warning on your screen about the spoof attack in action.

Fake call detection is on by default and works automatically on Android 12+ devices (so even older phones) Note: Love that this digital check uses end-to-end encrypted Rich Communication Services (RCS) technology, and is completely private. You can also turn this feature off if you prefer.

These types of phone scams are not hypothetical, they're hitting real everyday folks.

FTC cites $2.95 BILLION in losses due to these types of scams in 2024 and people rely on caller ID to verify someone is who they say they are! This will help people avoid sending their money to scammers and I'm so stoked to see it launch today.

Also honored to see the hard work I got to share with the Google team last year continue into 2026 and beyond with the fake call detection launch today! Programmatically catching and shutting down the latest phone call scams (including AI voice clones) is so close to my everyday work and it's such a thrill to work with orgs who prioritize solving this problem and protecting people from scams.

Also, the demo of fake call detection that Google made for me was an early version. In the launch today, the contact’s photo is also removed as another visual signal that it's likely an impersonator calling.

Really cool to see that update in action as we found that impactful in our research together!

I encountered this for the first time today while attempting to read something on archive.today.

I confirmed that decoding the qrcode using a computer and following the URL it contains is insufficient; the error it gave directed me here which is what the linked screenshot is of.

The old type of captcha remains available too, for now:

OC writeup by @cypherpunks@lemmy.ml

Though Google Cloud Next in Las Vegas was a couple weeks ago, I'm still working through it and trying to process everything I learned there. Three days, 32,000 attendees, 260 product announcements. One cool stand out...
Google shipped an entire agent accountability infrastructure at this conference. Every AI agent now gets a cryptographic ID and an auditable action trail tied to a defined authorization policy. They built anomaly detection that flags unusual agent reasoning in real time and maps it back to the source.
You build that when you're expecting things to go wrong at scale.
GE Appliances is deploying 800 AI agents across manufacturing and supply chain right now. That's operational continuity with autonomous software making decisions without a human in the loop.
Every enterprise leader needs to answer one question the technology doesn't answer for you: when an agent makes a decision that costs money or creates legal exposure, who owns it?
I'm looking forward to diving deeper into Gemini Enterprise and Chrome Enterprise. The Chrome Enterprise shadow AI reporting shows you every unsanctioned AI tool your employees are already using. You can't govern what you can't see.

https://cloud.google.com/blog/topics/google-cloud-next/google-cloud-next-2026-wrap-up

#AIGovernance #AgenticAI #GoogleNext #CIO #EnterpriseSecurity #security #privacy #cloud #infosec #cybersecurity #AI @google @googlecloud @googlecloudsec

How me not cluttering my search history with stuff I don't want to see in there, is supposed help protect the community, the learn-more-link didn't explain, though.

Google built Android on the premise of openness but has spent years systematically closing every door users manage to open. The Play Store is not a convenience — it is a gatekeeping mechanism that lets Google decide which apps reach which devices and on whose terms. Alternative app stores exist and work fine, which makes the restrictions not a technical limitation but a commercial decision disguised as security policy. Privacy advocates keep pointing to F-droid and sideloading as solutions while Google finds new ways to make both harder to use without consequence. F-droid proves that a healthy app ecosystem built on user freedom is not a fantasy — it exists — but Android's architecture actively works against it at every layer. Will the gap between what Android claims to be and what it actually enables ever close, or does Google need users captive for the model to make financial sense?