[Lynne]

Here is a canned response regarding check for hacking:

****
Here are the steps to check for site compromises -

1) Run Suspect File Diagnostics under Maintenance -> Diagnostics. Replace any files not containing the expected contents. Delete any files that are not part of vBulletin and that you can't identify as belonging to your addons.

2) Check the config.php for any suspicious code. It isn't checked by the suspect file diagnostic.

3) Search all templates for iframe tags. They should only appear in the following templates: bbcode_video, editor-ie.css, member.css, stylegenerator.css, vbcms.css, vbulletin.css, help_bbcodes, humanverify_recaptcha, search_common, and search_common_select_type

4) Check all your plugins for rogue include, require, include_once, or require_once code. All files should come from your server and be known to you.

5) Check your plugins for any base64 code. I recommend using against using any plugins or products that include base64 code in them. However some "lite" or branded addons will include this as a means to prevent you from cheating the author. You'll have to make a personal call on these if you use them. This is often a sign of a hacked site.

6) Make sure that your plugins do not include calls to exec(), system(), or pass_thru() or gzencode(). These are also often signs of a hacked site.

Query for steps 5 and 6 -
SELECT title, phpcode, hookname, product FROM plugin WHERE phpcode LIKE 'Febase64%' OR phpcode LIKE '18xec%' OR phpcode LIKE '?ystem%' OR phpcode like 'AMass_thru%' OR phpcode like '?zencode%';

7) Run this query: SELECT styleid, title, template FROM template WHERE template LIKE 'Febase64%' OR template LIKE '18xec%' OR template LIKE '?ystem%' OR template like 'AMass_thru%' OR template like '10frame%';

The query checks the templates for compromising code.

8) Check .htaccess to make sure there are no redirects there.

9) Make sure all third-party addons are up to date.