|
Post by Dianne on Sept 25, 2011 9:27:44 GMT -5
We just offered GALS a way to keep their member up to date on the progress of getting all this mayhem at their site sorted out. I sent an DM via twitter. I haven't heard back yet so we'll see.
I don't have a way of getting in touch with .NET if anyone wants you may contact them on our behalf and tell them as well that we would be happy to keep fans abreast of their progress of getting the site up and running again.
Sincerely, The Team of WOGBF's
|
|
|
Post by Dianne on Sept 25, 2011 10:30:28 GMT -5
I've learned a little.... Look at this.... www.zone-h.org/archive/notifier=TiGER-M@TE He's hacked 18,190 sites. I guess if they are going to get hacked, it might as well be by someone famous. He's being sought by the FBI. AND thehackernews.com/2011/01/exclusive-interview-with-tiger-mte.htmlIt's interesting that they're proud enough of themselves to sign their work. Apparently, this is a big time hacker, too. We just got an anonymous tip that Google’s been ‘hacked’ – sure enough, visitors of the company’s Bangladesh search site (Google.com.bd) see a defaced landing page rather than the usual search site. As far as I can tell, www.google.com.bd functions properly, so whether this really constitutes a ‘hack’ is up for debate. Local Bangladesh media, including online newspaper bdnews24.com, reported on the news as well, quoting a CTO of a local ISP, who confirmed the hack. Nevertheless, it seems like only a subset of users see the defaced landing page, while others report that they can visit and use the search engine without any hiccups. According to Zone-h, Bangladeshi hacker TiGER-M@TE has been quite active with defacements lately, and has targeted some high-profile sites in the past, including the local website for American Express and Airtel (video). Update: Google responds that Google Bangladesh has not been hacked. Apparently this is actually a Bangladeshi DNS registry issue that caused users going to Google.com.bd and other web addresses to be redirected to to another site. The issue is now resolved but may not clear for a while because of cache issues.
|
|