Quote:
Originally posted by Nooze2k
Man has this worm caused alot of hell. The question I'm wondering about is do they have any idea who is responsible for it? From my personal experience, its not like any virus I've ever seen, from an execution point of view anyways. I'm not trying to give the wrong impression or anything, but its the most clever worm I've seen in a long time. Not real devasting to the home user (just annoying), but could cause havok on servers and such... primarily WinXP/2000 servers..... hmmmm.... perhaps a disgruntled former MS employee? Sure, abusing Windows flaws is nothing new, but then shutting down RPC services, subsequently shutting down the PC as well. Ingenious, if not evil. I could see a hefty charge against the culprit if caught, but in this case I wouldn't be surprised if he was hired after it all settles. I'm just wondering how I got it after doing a fresh install and seconds after my first dialup connection to the 'net after the install..... makes you think....
|
While I agree the impact of this worm was *huge*, it wasn't really all that "clever..." Public information about the vulnerability this worm exploits was released on July 16, and public exploit code was released ~1.5 weeks after. The author of this worm just wrapped some self-spreading code around a plain vanilla public exploit code, and voila! Instant havoc
This has happened before too, just not with such widespread vulnerabilities. Examples include Code Red, Nimda, and SQL Slammer.