The actual malicious code is hidden by character codes that change letters in the script to numbers to conceal them as the virus moves through firewalls.
The tool searches for sites that are vulnerable to this particular attack, and directs itself against those sites, Rothacker writes.
There's no easy way to fix the vulnerability of the database to this attack except to "harden" the database by applying all the patches and making all the security requirements consistent. Monitoring the database for unusual activity is important, too.
The key is to keep the injections out in the first place.
To do that, the main web server should check other web apps to make sure they have credentials giving them permission for access to the site and validation of who they are, rather than just letting any unauthenticated process launch new code, Rothacker writes.
Users should also have specific limits on their access. Unknown users or those just recently signed up should not get more than Read access to anything but the most basic information and forms whose content will be analyzed to reduce the chance malicious code is already present.
Read more of Kevin Fogarty's CoreIT blog and follow the latest IT news at ITworld. Follow Kevin on Twitter at @KevinFogarty. For the latest IT news, analysis and how-tos, follow ITworld on Twitter and Facebook.