No Stupid Questions

2315 readers

2 users here now

There is no such thing as a Stupid Question!

Don't be embarrassed of your curiosity; everyone has questions that they may feel uncomfortable asking certain people, so this place gives you a nice area not to be judged about asking it. Everyone here is willing to help.

ex. How do I change oil
ex. How to tie shoes
ex. Can you cry underwater?

Reminder that the rules for lemmy.ca still apply!

Thanks for reading all of this, even if you didn't read all of this, and your eye started somewhere else, have a watermelon slice 🍉.

founded 2 years ago

MODERATORS

[email protected]

How does someone send a phishing email using a legitimate domain? (notification.intuit.com in this case) (lemmy.ca)

submitted 1 week ago* (last edited 1 week ago) by [email protected] to c/[email protected]

7 comments fedilink hide all child comments

A friend received a spam email from [email protected]

Intuit is a real company, and intuit.com is their real domain. Looking online, a number of people received this scam email a few months ago, and then again over the last week.

If you came across this post from Google, this is why it reeks of a scam email:

12 of other email addresses are listed in the to and cc fields
it says that a subscription is set to renew, "$399.99 will soon be taken out of your account" and that it will happen within the "next 24 hours". Classic sense of urgency
It includes an 888 phone number that does not come up as any legitimate number, and it includes a PDF which my friend did not download in case it is malicious

Does this mean that Intuit lost control of that subdomain, or is there another way that someone might be spoofing it? I can have my friend check any other metadata if it would be helpful.

If you came here from Google, welcome to the Fediverse :)

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 6 points 1 week ago

Very good answer. It's really complicated since it's an old protocol and lots of different mechanisms have been added on top. I found one small error: You can't rely on the "received" headers either. Just the line from your mailserver and the IP and hostname right before. The rest of the path (before) can be fake, too. (And this regularly happens.)