Hi! We’re confident this IS NOT a 0click attack. It’s a bug in our phone number privacy+usernames implementation, fix coming soon. I’ve asked OP to clarify/delete in service of minimizing harmful misinfo

→ View original post on X — @mer__edith