Intel Admits It Was Hacked in January

all i can say is that i know of only 1 way to stop all these attacks at once.  the original hacker used a shutdown code shortly after april first due to a successfull attempt to get outside help.  he panicked when he failed to stop me from sending info linking him as the original hacker onto my firewalls community site.  he ran install.exe from the driver's keyboard folder that created incoming cookies from support.microsoft.com that told the backdoor aka botnet to starte the removal processs.   the hacker paniced even further when my prompting of cookies caused him to wait as i didnt chose any option while coping all his source code and files

the reason im saying this is cause the worm changed again feb 13.  it made bluescreen reboots.  then i noticed it removed parts of the worm that intercepted any type of detection from your machine.   this was good at  first and i learned a lot more, but at the same time, i got more calls than the last 2 years combined with complaints linking to the botnet starting from scratch 2 years ago when i first faught it.  the only difference is that it seems to be running wild without the main hacker.   if this is to happen, i am about 60percent sure that feb of next year will be the time that the dns situation will be 10000 times worse.   i send over 2000 incoming packets per hour 24/7 since feb 2009.    imaging every machine doing  that.  this is what may come.  right now, you may experience such things as mouse having a mind of its own, or kernel lag, or popups increasing, access denied more and more.   system errors sooner or later, worm hijacking the operating system or first master boot record.  a lot of scripts and logs throughout your system.    internet speed cut down.   dns poisoning where your connection regulary dissconnect(linked to internal IP alterations/interceptions.,  letters and words disapearing or not being detected such as this message(memory pointers to NULLS).     and so on and so on..