Our shared hosting server Ragnell has been compromised, and the majority of the index.php's have been replaced with a hacked version. We have disabled all copies of the compromised index files already.
We are at the moment making sure the hole used is fixed before re-enabling Apache. As part of this, PHP is being upgraded to PHP5.
We are also going to see about restoring the disabled index files, however this is going to take longer. The backup system we use is geared towards full system backups, so restoring individual files is likely to take a while. If you have an uptodate copy of your index file, it will probably be faster if you get it uploaded yourself. This can be done even while Apache is down.
Update 1430: The upgrade of php / Apache is almost complete. Once it's finished we will be able start restoring index files from backups.
Update 1515: Apache is back up and running. We are currently restoring the index files from backup. This is going to take a long time.
UPDATE 1615: If your site's index file has been restored or if you've restored it yourself let us know if there are any issues.
UPDATE 16:52: As restoring individual index files is proving to be far too unwieldy, we are currently restoring the whole partition to another box. This will allow us to script the restore of any index files which are still showing as compromised.
UPDATE 1910: The restoration of the index files is progressing, but it's slow, as we are checking each index file to see if it has been compromised or simply replaced from a customer's own backup. If you have a backup / replacement index file and are having issues uploading it you may need to CHMOD 644 the current index.php
UPDATE 09:30 Friday Aug 20th
After 3 failed attempts at a full restore to a machine in our offices, we have successfully done a full restore to a machine in the data centre. This morning around 9am we restored any files which had a checksum that matched that of the defaced files that were placed there during the compromise on Saturday last.
Anyone who requires other files to be restored for any reason should contact us ASAP so we can restore them for you.
We are at the moment making sure the hole used is fixed before re-enabling Apache. As part of this, PHP is being upgraded to PHP5.
We are also going to see about restoring the disabled index files, however this is going to take longer. The backup system we use is geared towards full system backups, so restoring individual files is likely to take a while. If you have an uptodate copy of your index file, it will probably be faster if you get it uploaded yourself. This can be done even while Apache is down.
Update 1430: The upgrade of php / Apache is almost complete. Once it's finished we will be able start restoring index files from backups.
Update 1515: Apache is back up and running. We are currently restoring the index files from backup. This is going to take a long time.
UPDATE 1615: If your site's index file has been restored or if you've restored it yourself let us know if there are any issues.
UPDATE 16:52: As restoring individual index files is proving to be far too unwieldy, we are currently restoring the whole partition to another box. This will allow us to script the restore of any index files which are still showing as compromised.
UPDATE 1910: The restoration of the index files is progressing, but it's slow, as we are checking each index file to see if it has been compromised or simply replaced from a customer's own backup. If you have a backup / replacement index file and are having issues uploading it you may need to CHMOD 644 the current index.php

After 3 failed attempts at a full restore to a machine in our offices, we have successfully done a full restore to a machine in the data centre. This morning around 9am we restored any files which had a checksum that matched that of the defaced files that were placed there during the compromise on Saturday last.
Anyone who requires other files to be restored for any reason should contact us ASAP so we can restore them for you.

![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=16a7156b-54d5-4545-8e7c-b6a537809229)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=d5cff252-fcce-4901-a031-50070db919d7)