Page 4 of 4
Re: XeNTaX attacked by virus
Posted: Thu Dec 02, 2010 3:49 pm
by Balder
I just noticed the problem with the wiki, I hope it'll be solved with no big data loss. Also looking forward for the sonofabitch who hacked the wiki to die, as I was in need of consulting some GRAF's. He made me lose much time reverse engineering already done work.
Anyway, keep it going, try to ignore this loozers attacks and shield up the website.
Best regards!
Re: XeNTaX attacked by virus
Posted: Fri Dec 03, 2010 10:43 pm
by XpoZed
The answer is actually quite simple. The site was hacked by a bot that search for vulnerabilities thru search engines as google/bing/yahoo/whatever.
Most of these bots just try to exploit the system so they can use the host for further (for example DDoS) attacks to other sites.
Best way to protect yourself from attacks is to watch for the latest system updates, and patch your forum/wiki on time.
I'm a PHP programmer myself, and i can help you with some advices, but the sad truth is, i'm also too lazy and bored from PHP coding to handle the forum/wiki support myself.

Re: XeNTaX attacked by virus
Posted: Sat Dec 04, 2010 12:59 am
by Dinoguy1000
As I understand it, the wiki attack was unrelated to the forum/website one; it was just a matter of unfortunate timing. At any rate, MediaWiki has always been quite hardened against attacks (it has to be, to be good enough for one of the Top Ten websites); I suspect (having absolutely no data to actually back it up) that the attack may instead have exploited an extension.
Re: XeNTaX attacked by virus
Posted: Tue Dec 07, 2010 10:04 pm
by Mr.Mouse
"Mark Forums Read" works once again from the main index page.
Re: XeNTaX attacked by virus
Posted: Thu May 26, 2011 3:16 pm
by maxfire02
Hi all of you!
I am newbie here and i am scared that XeNTaX has been attacked by virus
by the way is the website safe to use now and can we visit attacked forum index is it risky to our systems?
Thanks
Re: XeNTaX attacked by virus
Posted: Thu May 26, 2011 4:32 pm
by Dinoguy1000
Yes, everything's fine now; this was resolved months ago.