{"id":6323,"date":"2023-12-04T13:28:33","date_gmt":"2023-12-04T13:28:33","guid":{"rendered":"https:\/\/really.zonky.org\/?p=6323"},"modified":"2023-12-04T13:28:37","modified_gmt":"2023-12-04T13:28:37","slug":"diagnosing-a-phishing-scam","status":"publish","type":"post","link":"https:\/\/really.zonky.org\/?p=6323","title":{"rendered":"Diagnosing A Phishing Scam"},"content":{"rendered":"\n
Just for fun (I have admittedly a very weird sense of fun), I thought I’d have a look at one of the phishing emails that came into me. I’ll go through this bit by bit, picking out bits that first occurred to me …<\/p>\n\n\n\n
Subject: LastPass : Required action needed regarding your account<\/code><\/pre>\n\n\n\n
Eh? Do I even have a LastPass account? I keep my passwords stored somewhere else, but it’s not impossible – I’ve been known to sign up to things just to test them out. Including cloud-based password managers.<\/p>\n\n\n\n
But all the same, let’s give it a point on the suspicion scale. Running total: 1.<\/p>\n\n\n\n
Well LastPass certainly use a funny looking email domain (the bit to the right of the “@”), but Marketing departments sometimes aren’t aware of how important that email domain really is. On the other hand, “tg8.so-net.net.jp” does look particularly uncorporate, so let us give it a suspicion point.<\/p>\n\n\n\n
Running total: 2<\/p>\n\n\n\n
On the other hand, it is too easy to fake<\/em> domains – I could very easily send you an email from the-management@l\u00e1stp\u00e1ss.com<\/em> (and even more subtle equivalents of “a” – “\u0430”, “\u1ea1”, “\u0105”, “\u00e4”, “\u00e0”, “\u00e1”, “\u0105”). And just to demonstrate something that looks identical can actually be quite different :-<\/p>\n\n\n\n
In [8]: print(ord('\u0430'))\n1072\n\nIn [9]: print(ord('a'))\n97\n<\/code><\/pre>\n\n\n\n
Now this isn’t to suggest that you should run your email headers through some Python code, but just that because something looks like lastpass.com<\/em> doesn’t mean it really is. The next thing that jumped out at me was the body of the email – I may be well trained, but something new and shiny is still distracting :-<\/p>\n\n\n\n<\/figure>\n\n\n\n
Now the first thing that jumps out at me is that red “Confirm my information” box. Screams “click here” doesn’t it? Well don’t click on it! In my email client (something you’re quite likely not using – claws-mail<\/em>), if I hold the mouse pointed above a link, it’ll tell me where that link goes in the status bar of the client. In this case it shows up as https:\/\/tg8.benchurl.com<\/em>\/…. doesn’t look very much like lastpass.com<\/em> does it? That’s sufficiently suspicious that I’ll award it 3 suspicion points.<\/p>\n\n\n\n
Running total: 5<\/p>\n\n\n\n
Notice how they don’t add a “Dear ${name}” to the top of the email? Not personally addressing email is ever so convenient to scammers that want to get your details – because they don’t necessarily know your name. That’s a suspicion point all on its own.<\/p>\n\n\n\n
Running total: 6<\/p>\n\n\n\n
Next note how it tries to rush you … “log in before January 16, 2024”. It’s subtler than many phishing scams, but it’s still trying to rush you. Add another suspicion point.<\/p>\n\n\n\n
Running total: 7<\/p>\n\n\n\n
There’s further details we could dig into, but that’s more than enough that the Delete button is the only thing this email should attract. That running total? It was just for fun, it’s not intended as a guideline for when to count something as a phishing email.<\/p>\n\n\n\n
In the case of doubt, contact the company via other means. <\/p>\n","protected":false},"excerpt":{"rendered":"
![\"\"](\"https:\/\/i0.wp.com\/really.zonky.org\/wp-content\/uploads\/2023-12-04_1242.png?resize=565%2C1024&ssl=1\")
<\/figure>\n\n\n\n