Last Updated: 2011-04-02 01:04:05 UTC
by John Bambenek (Version: 1)
Websense has been tracking a mass SQL-Injection attack for the past few days that started with only a few ten thousand websites and has exploded to potentially over 1 million websites. There doesn't seem to be anything particularly new about the infection mechanism (aside of the scope of its success) and the injection itself only inserts a random snippet of HTML to redirect victims to a rogue AV site that tells the user they are infected.
One of the domains implicated in this attack was registered in October and showed up on the radar in December, so it appears the preparation of this attack has taken some time and it's been perculating for awhile. The bulk of the infections, however, have only just occurred in the last few days. Infected sites tend to use the same URL structure including a file "ur.php". It appears this is only affecting sites using Microsoft SQL Server 2003/2005.
Defense against your sites getting infected is the standard things we ought to be doing anyway in regards to SQL injection (i.e.use prepared statements, filter input for control characters, whitelist if possible, blacklist if not). Webserver administrators should also be checking for sudden appearance of files in their httpdocs directory. More on this as it develops.
bambenek at gmail /dot/ com
Last Updated: 2011-04-01 02:19:27 UTC
by Kevin Liston (Version: 1)
April 1st is upon us. In some circles it is celebrated as "April Fools' Day." I choose to observe it as Open Source Intelligence Analysts' Day-- the one day of the year that we all have to be extra-suspicious of every news article, blog post and tweet. It's a good skill to develop, and we have this unique time where we know that there are hidden gems of disinformation being introduced into the streams of information we've come to rely on the rest of the year.
It's like a tornado drill for truth.