A developer with 20 years on Twitter/X shares a personal account of falling for a sophisticated phishing attack that resulted in losing access to their account. The post details five key mistakes: acting in a rush during a security task, not scrutinizing a convincing phishing email, failing to check the sender address or link URL, ignoring the browser autofill not triggering on the fake login form, and not having an authenticator app set up. The attacker quickly changed the account email and locked the victim out. Practical takeaways include always verifying sender and URL, treating missing autofill as a red flag, and using an authenticator app rather than SMS-based 2FA.

8m read timeFrom christianheilmann.com
Post cover image
Table of contents
First Mistake: doing any security things in a rush.Second Mistake: falling for a pretty good phishing mail.Third Mistake: not checking the URL of the link or the sender of the mail.Fourth Mistake: not realising a fake form despite using autofill.Fifth Mistake: allowing myself to be kept busy while the phishing attack is happening.Where I am now…Conclusion
2 Comments

Sort: