One Million Sites Infected With Malware In Q2 42
Trailrunner7 writes "More than one million Web domains were infected with malicious code in the second quarter of 2010 — around one percent of all active Web domains, according to new data. The number of infected domains was extrapolated from data gained through a sample scan of what Dasient describes as 'millions of Web sites,' as well as from customer deployments. It suggests that compromises of Web sites are on the rise, as attackers look to push out malicious programs through so-called drive by download attacks."
*domains* infected? What? (Score:5, Insightful)
A domain is a node in the DNS namespace. How does that get infected?
If a web server hosts 20 domains, and is infected, does that count as 20 infections?
"Web site", "domain" and "host" are not interchangeable.
Less and less active... (Score:4, Insightful)
It used to be in the late 90s to early-to-mid 2000s there would be people left and right with adware that popped up stuff and computers would grind to a halt. Today, I'm not seeing that on anyone's computer that I've done tech support for. I have seen a bunch of systems grind to a halt due to Norton/McAfee, but none caused by viruses/spyware/adware/etc. The only thing I can think of is that IE7 and beyond stepped up security enough to make a major impact.
So even though "threat analyzers" pull up scary numbers, I'm not seeing the results in the wild.
Re:Less and less active... (Score:5, Insightful)
it just means the malware authors have grown up and want a paycheck.
It used to be that half the viruses were showy things written by amatures who wanted to fuck around.
most of the rest were trying to cash in on ad revenue from popups.
Now there's less money in popups(most of the big ad providers don't like being associated with malware) so the malware just sits quietly trying to steal your credit card number.
The more stealthy the more successful.
Re:Um yeah.. (Score:3, Insightful)
Windows 7 decided that an executable that I had on my computer(that I myself had just compiled) was a trojan...
I'm curious why you think Windows 7 was wrong? ;)
Re:Um yeah.. (Score:3, Insightful)
It isn't a trojan until it gets in someone else's machine. If you know it's a trojan and you install it anyway, it's no longer a trojan.
1) Just because he compiled it, doesn't mean he knew it was a trojan. One could download source from the web and compile it, and get a trojan as a result.
2) Even if he wrote it, it could be the result of a multiple-personality disorder coding against him... :D
3) I disagree that intent matters. Even if he wrote it himself, knowing full well what it was... I'm not sure I buy the idea that deliberately installing a trojan on purpose makes it any less a trojan.
Had the king of Troy divined that the greeks's had stashed some soldiers in the 'trojan horse' and he brought it into the city anyway... and then promptly burnt it to the ground. Well... it was still a "trojan horse". Similarly when a security researcher deliberately obtains a trojan to dissect, it is still a trojan.
A firearm isn't a weapon until it's aimed at a human
A crossbow aimed at a rabbit is a weapon. A machine gun in a crate is a weapon. A nuclear missile waiting in its silo is a weapon.
Indeed it would be impossible to build weapons, test weapons, find weapons, or sell weapons if they didn't exist until humans were in the cross hairs -- yet there isn't a person on the face of the earth who would be confused by any of those terms.