Skip to main content


infosec - CW: potential malicious link (obfuscated)

So Katy got a scam text claiming to be Canada Post with an underliverable package. I'm in the process of gathering information to send a report to their registrar's abuse department, but they're doing something clever to cover their tracks that I haven't fully been able to unravel.

For context, here is the link (with spaces added to prevent it from turning into an actual link and being accidentally clicked):

https:// canadapost-postecanadadeliverylivraison .com/canadapost/index.php

When opened from Safari on her phone, it loads a realistic looking phishing site, but when opened from any other browser, it returns an empty (0 bytes) page. I assume this is to hamper attempts to investigate abuse claims (though the domain name is already pretty incriminating).

Since there doesn't appear to be any kind of unique identifier, I assumed this to be some kind of spear phishing attack that was based on her browser's User-Agent string, but when I tell curl to mimic it, I still don't get a result.

Any ideas about how they're doing this?

reshared this

in reply to Jonathan Lamothe

infosec - CW: potential malicious link (obfuscated)
My current working theory is they're using some sort of tracking cookie that had previously been placed on her phone.
in reply to Jonathan Lamothe

infosec - CW: potential malicious link (obfuscated)
The link also works from her iPad.
in reply to Jonathan Lamothe

infosec - CW: potential malicious link (obfuscated)
...and it doesn't work in private browsing mode, so I'm pretty sure at this point it's a tracking cookie.
in reply to Jonathan Lamothe

infosec - CW: potential malicious link (obfuscated)

Sensitive content

in reply to Isaac Ji Kuo

infosec - CW: potential malicious link (obfuscated)
@Isaac Ji Kuo Perhaps, but that leaves me wondering why using private browsing trips it up.

This website uses cookies. If you continue browsing this website, you agree to the usage of cookies.