Continued img.4chan.org downtime

So, it has been a while and img is still down, presumably powered down to prevent DDoS by a bunch of retards. Now, I I wouldn't normally care about /b/ and /r9k/, but the the truth is that the lost sheep are slowly but certainly seeping into the other boards. The performance hit is already quite noticeable, especially zip is awfully slow and unresponsive at times.

This brings me to question why moot hasn't started to employ some sort of countermeasure. While I realize that DDoS is generally hard to prevent, there should be at least some options depending on the form of attack, like TCP syn cookies, firewalling certain packet types, etc.

Insight into this topic would be much appreciated.

From status.4chan.org:
Apparently the DDoS attack is being caused by a trojan some 4chan users have downloaded. If you've downloaded ANY FILES linked on 4chan, please immediately go to this link and download the removal tool: Trojan.Vundo Removal Tool @ Symantec. Otherwise, all users are encouraged to run a full system scan to ensure their system is clean. The sooner people do this, the sooner /b/ & /r9k/ will return.


So apparently /b/ self-pwned itself LOL
more here: http://www.businesspundit.com/how-4chans-b-board-got-crippled/