I got hacked at 3:59 AM without clicking anything. My voicemail handed the attacker my Telegram login code.
Here is exactly how it worked, so it doesn't happen to you.
3:54 AM. My phone rings about ten times in a row, No Caller ID. That was not harassment. It was the attack: keep my line busy.
Meanwhile, the attacker asks Telegram to log in with my number and picks "send the code by phone call". My line is busy, so Telegram's robot call lands on my voicemail and reads the code out loud to it.
Carrier voicemail can often be reached remotely, with a default PIN or a spoofed caller ID. He listens to the message. At 3:59 he is in.
Fortunately, the attack was noisy. The calls woke me up. At 4 AM I only wanted to go back to sleep, but I had the presence of mind to check my notifications. Telegram was showing a new login from a device I didn't know. That check is what saved me: I ended his session within minutes. If I had rolled over, the next day would have been a mess.
In those few minutes he had already typed /balance, then /start on every old wallet bot he could find in my chats. He was hunting for funds tied to my Telegram. The bots were long dead and nothing was lost. He still had time to set his own 2FA password on my account.
What would have stopped it:
Telegram two-step verification, with a recovery email. With a password on the account, the code alone is useless.
Your voicemail. Change the PIN, block remote access, or turn it off (##002# cancels call forwarding on most carriers).
Same for WhatsApp and any service that can send a code by voice call.
No seeds, keys or passwords in Saved Messages. Ever.
A burst of masked calls at night is a signal, not a nuisance. Check your notifications and your active sessions.
I have been building in crypto for more than ten years and I had never thought about my voicemail. Check yours today.
We’re investigating an issue where users with specific conditional access policies applied may be unable to access any Microsoft 365 service. We’re reverting a recent change to mitigate impact. For more details please look for MO531859 in the admin center.
📢Update Compliance reports will no longer be available after March 31, 2023📆.
Please enroll in Windows Update for Business Reports ASAP. More info: Microsoft 365 admin center Message Center post MC527281 and here: https://t.co/1t6bEP7H8p
#WUfB#IntuneInspired#MicrosoftIntune
We're investigating an issue wherein users may be unable to access their Exchange Online mailboxes via any connection method. Additional details can be found within the Service Health Dashboard under EX522020.
We've identified a potential networking issue and are reviewing telemetry to determine the next troubleshooting steps. You can find additional information on our status page at https://t.co/pZt32fOafR or on SHD under MO502273.
We've narrowed down our list of potential solutions and workarounds, and we'll be validating their efficacy. We'll provide additional information as it becomes available. Refer to MO497128 in the admin center for details.
We will try another round to get @mwbengtsson to 2k follower list.
Martin created a cool toastnotification community tool, with #configmgr Integration, follow him to get more infos, we like to close the 2k-bag today, please #rt
I've already fixed my AppLocker rules - SO SHOULD YOU! #mustread KUDOs to @GHaslinger@Oddvarmoe you might be interested as well, for the how to fix it part https://t.co/5bHDP8bo2q