When Webmasters Get Phished? 55
SirJorgelOfBorgel asks: "Many of us run webservers. Some of us just for fun - hosting many of the 'less important' stuff around on the web, others professionally. Though you always try to keep your webserver secure there's always the possibility you get hacked. What do you do, then?" You would think that, by doing the right thing and reporting the incident to the proper authorities, they would do the right thing and go after the hackers, right? This may not be the case. Here's a cautionary tale on what may happen if you follow that line of reasoning. The real question here is: what else could SirJorgelOfBorgel have done to make things turn out as he expected?
"It happened to me a few months ago, and the hacker installed a phishing website. Of course I found that out within a few hours and removed it (and patched the used vulnerability). To be helpful, I packed the whole folder, relevant logs, etc, and sent them -- accompanied by a letter explaining what happened -- to the fraud reporting email address of the bank that was the target of the attempt. That's what we all would do, right?
To my surprise however, instead of them trying to found out who it was that made the attempt (an email address where the phished usernames/passwords were transmitted to was clearly visible in the source), they had me disconnected from the Internet and put on an ISP blacklist. Took me some cash and a lot of time to even get reconnected to the Internet. And there I thought they would be happy with this information.
In light of this, if you should ever notice a phishing attempt, would you still report it, knowing it might get yourself in a lot of trouble? I for one, probably won't.
Furthermore, though I know it is my own responsibility to make sure my PCs are well protected, would there be any legal action I should/could take to get reimbursed for my losses? (The bank is a US bank, I am not a US citizen.)"
Waste of time... (Score:2)
Re:Waste of time... (Score:2, Funny)
Re:Waste of time... (Score:2)
Re:They sound justified (Score:2, Insightful)
Re:They sound justified (Score:1, Troll)
Re:They sound justified (Score:1)
Re:They sound justified (Score:2)
Re:So (Score:2, Funny)
What does reading have to do with this? Or do you even know what that means?
Re:So (Score:2)
of course, the grandparent should really just let typos like that go. this is slashdot, after all.
Re:Folder? (Score:4, Interesting)
For unix, "directory" is right. (Score:1)
Of course, people may choose not to care.
chl
Re:For unix, "directory" is right. (Score:4, Interesting)
We evolve. Join the club.
Re:For unix, "directory" is right. (Score:1)
chl
Re:For unix, "directory" is right. (Score:2)
But as the GP says, the users of the computer don't think of it that way. They think of putting/saving a file *in* the folder, not saving it on disk somewhere and adding the link to it to a given directory.
Re:Folder? (Score:2)
Re:Folder? (Score:2)
When telling my wife where I saved a document, I tell her what "folder" it's in because that's the metaphor her gui (kde) uses.
I remember some desktop gui I used back in the eighties used drawers rather than folders. Can't recall where I saw that.
Re:Folder? (Score:4, Insightful)
Yes, of course, everyone running IIS is completely incompetant. There is no good reason ever to run IIS. Everything you can do in
I am a Unix guy, I don't run Windows on my personal machines. I don't run Windows on my (primary) work machines. I do, however, know that it is very possible to run a site of reasonable security on IIS.
Unix people (mainly noobs) with militant "you deserve what you get" attitudes are a serious detriment here. Plenty of OSS apps get badly hacked as well. Lately we've seen stats programs, and even freaking ZLIB expose remote code execution vulns.
I'm not saying "don't trust open apps", I'm saying "don't blanket condemn closed apps", especially when someone asks a simple question which deserves a simple answer. Show me where he says "I run IIS".
US Banks (Score:5, Insightful)
That said, it's important to remember that they're not going to actually read any explanations you attach to anything you send them. What they will do is look over the attachments, make their own determination as to what happened, and go tearing off in a random direction, convinced of the righteousness of their crusade.
So how do you notify them of the phisher without being bitten yourself? Complain about phishing emails coming from the address in question. Don't mention a website. Certainly don't mention your own server. Is this dishonest? Yes, technically. But if you're competent and you know they're not (or at the very least suspect they're not) it's more a case of tailoring the information to suit the audience. You don't explain moral values and arguments to a guard dog, you simply point at the intruder and tell the dog to "sic 'em!".
There are other US industries to be wary of, with regards to IT: insurance, legal offices, professional medical offices (hospitals, doctors, dentists, chiropractors, etc). The smaller offices tend not to know what's going on, the larger ones tend to push everything off on an IT department that's entirely too small for its own good (and may be staffed with less than the best), and they all tend to make demands that don't coincide with consensual reality.
Why is it like ths? From what I've seen it's a matter of not having IT people, or letting someone who doesn't understand what's needed do the hiring. They end up with a lot of paper tigers, or worse. I remember one insurance office that had hired an agent's neighbor - a 13 year old self-proclaimed 'firewall expert'. It took me two weeks and nearly $1000 of their money to sort out the mistakes he'd made (and find/remove all the snoopers he'd left behind).
In a nutshell, try not to use big words when dealing with US banks, and only give them the information they need to point them in the right direction. While your mileage may vary, it's a good practice, because it will protect you.
I'm sorry, but I don't have any advice on how to recover your losses with regards to the actions the bank took.
Re:US Banks (Score:2)
Re:US Banks (Score:3, Informative)
Worked at a company that dealt with banks a couple of years ag, and I have to agree. MORE THAN ONE of them used the name of the bank backwards a the passwords to thier vpns... seriously people, BANKS!
Re:US Banks (Score:2)
I emailed the site owner and even gave
Re:US Banks (Score:2)
I find so many phishing sites still up a week after the email timestamp, when I finally check my phishy-email folder.
I email the url, and email to the site contacts, ISP, lots of other info. I am thinking of making a firefox plugin called ' report phish ' which will email from a whois lookup, the nameserver admin, the webserver admin, the hosting guys, any personal email found on that root site, also the reply to address or any valid address in the site,
Report to someone who can do something about it. (Score:2)
I think your only liability is not to report it. Just report it to law enforcement instead.
If someone intentionally interferes with your business, yes, you should sue the fuck out of them. Especially if they have the ability to pay, like a bank.
However, I'm puzzled by this vulnerability you patched to prevent phishing. I, too
Re:Report to someone who can do something about it (Score:2, Informative)
Re:Report to someone who can do something about it (Score:3, Insightful)
Do the one thing the bank will do nearly anything to prevent... Publicize it far and wide. Let everyone know the bank, their name, and the cities affected wherein people whose information was compromised live. Once their customer base is all over their phone lines demanding information that only you can provide.
Of course, unless you signed an NDA in which case...ignore me.
Re:Report to someone who can do something about it (Score:4, Funny)
Re:Report to someone who can do something about it (Score:2)
you'll still have to spend time/money ... (Score:2)
Re:Report to someone who can do something about it (Score:2)
From TFA (or TF Post, or whatever):
"(the bank is a US bank, I am not a US citizen)"
Last thing I checked, US civil judgments still weren't enforceable abroad. Slander away, Mr. Sulu...
Re:Report to someone who can do something about it (Score:2)
Perraps your actions had nothing to do with it ... (Score:5, Interesting)
When I get a phishing attempt, I generally report them to the institution being impersonated, especially if it's more convincing than normal. I imagine that some other people do the same. It's entirely possible that other users reported `your' phishing site, and the bank was already in the process of getting it shut down when they received your email.
And if they did get your email, and it was received by the right people, they probably don't care. Your site cost them money, even if you claim that you weren't directly responsible, and they'll do what they can to stop it from happening again.
Ultimately, the right answer is to keep your system secured enough so this doesn't happen. Your email after the fact was the Right Thing [tm] to do, at least morally, but I'll bet if you had checked with your attorney, he'd have suggested not sending it at all. as it could be used as evidence if the bank decided to sue you.
It's not right, but it's the way things are ... being a Good Guy [tm] just doesn't pay anymore.
NAME NAMES! (Score:3, Insightful)
I need to know your company's name, so I avoid your insecure web servers.
I need to know the bank's name, so I can avoid ever reporting anything to them.
And I need to know your ISP's name so I can double-check any contracts I might have with them.
What's the point of posting this when we have no idea who it is, or even if you made it up or not?
Re:NAME NAMES! (Score:1, Insightful)
Name yourself so I can avoid you!
Re:NAME NAMES! (Score:2)
I'll concede that knowing the bank involved and other details about this incident would be nice to have, but as an Ask Slashdot the information isn't "needed".
Are you sure of cause and effect? (Score:2, Insightful)
1) It was the bank that had you disconnected (it might have been a phishing victim doing the complaining to someone else,
2) It was because you notified them that they had you disconnected (they might have already gotten phishing complains and had the disconnect in the works while you were still gathering the evidence)
I'd like to hear the bank's side of the story.
I know, in
Let me FUCKING guess (Score:1)
Their collection department used to call me up looking for their delinquent customer. The phone line was new to me, but apparently the number used to be owned by a real deadbeat.
When I explained the situation about the phone line, they told me that they were putting all my excuses into my record. Heh. Finally, I told them that they were fucking idiots, and hung up.
Next day they called back and asked why 1) I haven't paid them their money, and 2) why I was so rude to
Re:Let me FUCKING guess (Score:2)
http://www.fleet.com/bankofamerica/ [fleet.com]
Re:Let me FUCKING guess (Score:1)
Re:Let me FUCKING guess (Score:2)
I was flagged in Verizons customer database. Flag stated that I was rude, cursed a lot and actually knew what I was talking about... Aparently the new supervisor I chewed up and spit out after a week long DSL outage didn't like me.
Oddly enough, I found this out when I worked for them as a contractor a year after I closed my account - they keep their customer records for far too long.
I'd rather eat my own poop rather than do business with them. - thanks for the laugh...
Bank's view: you are the problem (Score:1)
You've shown that your system can be used to hurt his bank, so he will try to prevent that from happening ever again. The FBI will arrive shortly to impose a Mitnick order (that you must never use a computer ever again).
(What kind of world did you think you lived in, anyways?)