This is server header response...
Code:
HTTP/1.1 200 OK
Date: Wed, 01 Jun 2011 17:46:01 GMT
Server: Apache mod_fcgid/2.3.6 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
X-Powered-By: PHP/5.2.15
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html
So you are on apache linux, with front page extensions? If you're not using the front page extensions, those can go. I have heard (but not experienced) about security problems with that means of web development.
70.85.20.39 is the ip for jarvispainting.com
Other websites on those IPs are fine http://blekko.com/ws/ip:70.85.20.39
70.85.77.107 is the ip for thehomeconnection.com
Other websites on those IPs are fine http://blekko.com/ws/ip:70.85.77.107
except
http://noiraqescalation.com/
http://www.krabi-nightlife.com/
http://www.truthofthespoon.net/
http://www.aphrael.net/ (but they look like old errors)
Are they related to you? If not... consider contacting your host. If the virus has just started, and it has for one reason or another infected more that just your websites, or only partially some of your websites have been breached, not all of them, or especially if the problem is getting worse, then the virus could just be busy working it's way through the computer. Once a virus gets into a shared hosting environment, then it has to go to work to breach all the other accounts, but once it's in, it may have access to the shadow passwords (not sure the correct terminology), then it just needs to crack the hashed passwords to get to the other accounts.
I am guessing as to what is happening of course.
But, your host should be involved, especially if those other websites are hacked, and not related to you, and that should be the evidence to get them to start looking if they are a large organization that is busy, jmo...
Another thing you can try is whitelisting your IP so you are the only one who can access your accounts, that will help you figure out if the script doing damage is coming from your network and not from somewhere else, if the hosting company is not helping.
Then your other option is to get your corporate firewall to limit the service ports which are in use to access the remote host which is being attacked. Limiting FTP, or whatever other ports which might be causing an issue, with maybe just leaving HTTP 80 the only port available for access, until you get everything figured out.
EDIT: Everything looks fine now... what happened?