When I hovered my mouse pointer over the link in the message, I found that the first part of the name in the fully qualified domain name (FQDN) looked like something I would expect in a site name for my employer, but the ending of the domain name was securefileshares.com, which would not be a site I would go to to modify security questions for a work-related system. On my laptop, I use Outlook 2016 as my email; to view the email header for a message in Outlook 2016, you can take these steps, but most email clients provide a mechanism to view a message's header, which will show the originating system and other email servers a message has passed through. Viewing the header information, I saw the following lines:
Received-SPF: Temperror (SPF Temporary Error: DNS 'NoneType' object has no attri bute 'header') identity=mailfrom; client-ip=188.8.131.52; helo=mail.nova.phishme. com; firstname.lastname@example.org; email@example.com <text snipped> Received: from mail.nova.phishme.com (mail.nova.phishme.com [184.108.40.206]) by <text snipped> MIME-Version: 1.0 X-Priority: 3 X-PhishMe: Phishing_Training X-PhishMeTracking: TjaVg7y+fe0Q/<text snipped>
The header lines showed it was a training exercise, since PhishMe is a company that helps organizations train their employees to avoid phishing attempts. But, if you have a question about whether a message you have received is legitimate or is a spoofed message that appears to come from a legitimate sender, such as your employer, bank, or some source you would trust, it is best to type in a link rather than click on one within an email, unless you observe the actual link very closely. It can also help to identify a message sent by someone spoofing a legitimate sender by examining message headers. It is trivially easy for a spammer, malware purveyor, or other malefactor to spoof a "From" address, so you should never assume that a "From" address is a reliable means of identifying a message's actual sender.
Indian authorities stated that the callers were trained to disguise their Indian accents, so that they would sound more like native-born Americans. Employees of the scammers were given a six-page script with tips on how to allay potential victims suspicions. For their jobs as criminals, callers were paid between 10,000 rupees and 70,000 rupees every month, which is equivalent to between $150 and $1,050 U.S. dollars, police said. Shelke stated "Employees were aware of the fraud, but since they were getting a good salary, they remained silent."
I received a call from a scammer pretending to be an IRS employee in February of this year. In that instance, the person I spoke to had an obvious Indian accent. When I told him I knew he was a fraudster, he responded with a reference to a sexual act and hung up. Subsequently, my wife has received many similar bogus IRS calls. In the case where I spoke to the caller in February, the scam operation was spoofing the calling phone number.
Such scammers don't target just Americans. Tax agencies in Canada and Australia have all issued warnings over such scam callers. Last year, Sahil Patel, a scammer residing in Pennsylvania, was sentenced to 14 1/2 years in prison for his role in a similar scam where callers posed as law enforcement officers or tax agents. He was also ordered to forfeit one million dollars. The call centers Patel worked with used software that allowed them to spoof calling numbers so that those called would see a phone number that appeared to be associated with the agency with which the callers claimed to be associated.
At a Senate hearing in 2015 prior to Patel's conviction, a U.S. Department of the Treasury official estimated that such scams generated between 9,000 and 12,000 complaints a week and had gained scammers more than $15.5 million from 3,000 victims.
So kudos to Indian law enforcement officers for the recent operation; I hope they catch the kingpin(s) for whom those arrested worked.
When I then searched online for that number, I found others reporting receiving similar scam calls from that number, e.g., at the 800Notes page at 315-825-8947 I found reports such as "They called me 4 times. I finally picked up on the last time and it was a woman with an Indian accent claiming to be from Windows Tech Support and I immediately hung up. This is a scam."
Fifty minutes later, my wife received a similar call again at 1:52 PM from someone with an Indian accent. She informed the caller that she knew it was a scam and asked to be removed from the calling list. I used *69 again and this time I was informed that the caling number was 315-639-8222. I found that number also listed at the 800Notes site at 315-639-8222. When I tried calling that number I heard a message that "The number you have reached has been disconnected or is no longer in service."
We received two more "Windows Technical Departement" calls within a couple of hours. We were watching a series on Netflix during that period and I didn't try to check those two calling numbers with *69.
I think it was the second call where I again picked up the phone and talked to the caller who again had an Indian accent - my wife told me all four seemed to have an Indian accent. I asked where he was calling from and he told me New York. I asked him what company he worked for; he said "Windows Technical Department". I asked him if he knew what company produces Windows. He didn't answer, but attempted to continue with his spiel telling me where to click with the mouse. I tried to see if he knew anything except the spiel he had been given, but this caller wanted to stick with the spiel telling me where to click, though he eventually hung up when I told him to hold on for a minute while I went to another phone, where I was going to record our conversation.
My wife gets very annoyed by such calls; she's usually the one picking up the phone for our home phone number, which is a VoIP service from our cable provider. I haven't received such scam calls on my cell phone number, though I do get a fair number of unwanted telemarketing calls on that number, often from spoofed numbers. My wife said she frequently gets the Windows scam calls when I'm not home. A few months ago, I received a call on our home number from another scammer pretending to be from the IRS.
Our phone numbers are on the U.S. Federal Trade Commission (FTC) Do Not Call list, but, of course, scammers, and many telemarketers as well, don't bother checking that list.
Coincidentally, today I read an article on the Ars Technica site titled Mobile carriers aren’t doing enough to fight robocalls, senators say. I wasn't pleased by the following paragraph in that article:
AT&T CEO Randall Stephenson recently claimed that AT&T doesn't have the "authority" to implement new robocall blocking technology in its mobile network, even though the Federal Communications Commission clearly stated last year that carriers have the "green light" to offer robocall-blocking services to consumers.
After he hung up, I used *69 on my phone to see what calling number was reported. The calling number reported was 1-800-829-4933. That number and the one he gave are actual IRS numbers. The 1-800-829-4933 number is the IRS main taxpayer assistance line listed at How to Get Tax Help from the IRS and the 1-800-829-4933 one is the one listed on that same page for taxpayers to call with small business-related questions. However, it is common for telemarketers and scammers to spoof the calling number. Unfortunately, it seems that is fairly easy for them to do. E.g., often when I receive telemarketing calls to my mobile phone I notice that the first six digits of the calling number match those of my phone, but if I call the number back, the person who that phone number actually belongs to will answer and knows nothing about such calls. Telemarketers spoofing calling numbers is a common way to make it more difficult for people to identify the actual originating phone number when they file a complaint, but also telemarketers will spoof a calling number to make it more likely that the callee will think that he/she is receiving a local call and thus answer the phone. Con artists will spoof a calling number from a legitimate business, organization, or government agency to dupe a callee into thinking the call is legitimate.
After I hung up, I found the October 15, 2015 article on the IRS website, IRS Warns of Pervasive Telephone Scam, which notes:
The Internal Revenue Service today warned consumers about a sophisticated phone scam targeting taxpayers, including recent immigrants, throughout the country.
Victims are told they owe money to the IRS and it must be paid promptly through a pre-loaded debit card or wire transfer. If the victim refuses to cooperate, they are then threatened with arrest, deportation or suspension of a business or driver’s license. In many cases, the caller becomes hostile and insulting.
The article notes "that the first IRS contact with taxpayers on a tax issue is likely to occur via mail", which is what I would expect and lists the following characteristics for the scam:
The article notes that you can file a complaint with the Federal Trade Commission (FTC), a consumer protection agency, regarding such calls:
You can file a complaint using the FTC Complaint Assistant; choose “Other” and then “Impostor Scams.” If the complaint involves someone impersonating the IRS, include the words “IRS Telephone Scam” in the notes.
Note: I found that I needed to select "Scams and Rip-offs" and then "Impostor Scams", which is for "Someone posing as a well-known business, a family/friend, or a government agency". After that I made the following selections (it didn't sem to be as obvious as I would have expected how one should file a complaint regarding someone pretending to represent a U.S. federal government agency):
You will then be taken to the "Information Collection" step where "In just a few moments you will be able to tell your story in your own words. But first we would like to collect some information." After I completed the complaint submission process, I saw the following information:
Thank you for submitting your complaint to the Federal Trade Commission. Based on the information you have given us, we believe the following links to our consumer website may be helpful to you:
If you have any questions or would like us to add additional information to your complaint, please call 877-382-4357 to speak with a counselor.
The webpages to which the FTC link pointed had a link to another IRS article on such phone scams titled IRS Warns of Phone Scam.
I reported the spoofed site at the following phishing report wepbages:
|CastleCops||Phishing Incident & Termination|
|Symantec Phish Report Network||Report Suspected Phishing Sites|
The recipient doesn't have a PayPal account. Whoever created the spam message probably sent it to thousands of people with no way of knowing how many of those recipients might have PayPal accounts.
I checked the online directory for the university today and sent another message regarding the spoofed site; this time I sent the message to the chair of the School of Design at the university plus email addresses for people who appeared to be IT people at the university, and some general contact addresses. Hopefully, one of them can get the spoofed webpages removed and take action that will result in the perpetrator being apprehended and disciplined.
Going to http://mic.polyu.edu.hk/ instead, I found the following information for the site:
I reported the spoofed site to to the contact address listed for the Hong Kong Polytechnic University. The webserver being used to host the spoofed PayPal site apparently belongs to the Multimedia Innovation Centre School of Design at that university. I also reported this phishing attempt to PayPal via the PayPal Report Fake Site/Spoofwebpage. And I reported the spoofed site at the following phishing report wepbages:
|CastleCops||Phishing Incident & Termination|
|Symantec Phish Report Network||Report Suspected Phishing Sites|
The message attempted to trick PayPal users to going to a spoofed PayPal website to confirm the addition of an email address to a user's PayPal account. In reality, the link in the message would take the victim to http://sv1.melbhosting.com.au/%7Eforcast/index.html, which would redirect him to http://bourke.pcpro.net.au/icons/.pay/pal/index.html. There he would see a website mimicking the PayPal site where he would be prompted for his PayPal userid and password. If he entered a userid and password, he would see a form asking for personal information, including a credit card number.
I reported the spoofed site at 10:33 A.M. using PayPal's Contact Us - Protections/Privacy/Security - Report Fake Site/Spoof form. I also reported the site to the Phishing Incident Reporting and Termination (PIRT) Squad at 10:48 A.M. At 11:15 A.M. the webpage to which the link pointed, http://sv1.melbhosting.com.au/%7Eforcast/index.html was removed from the webserver on which it resided, resulting in a "HTTP 404 - File not found" message, but the spoofed PayPal site at bourke.pcpro.net.au was still accessible.
Shop Amazon Local - Subscribe to Deals in Your Neighborhood