Same. Also noticing that the sidebar for Stingrays players (so people like Tart) isn't working either.
Yeah you're all lucky you can post at the moment. I'll fix it all up after I've had a proper chat with AK47 about securing the forum from future hacks. I don't have a lot of time at the moment but the main issue is the fact that it'd be a waste of energy to fix the site completely only for them to wipe it again.
You don't necessarily need to restore a backup to resolve this issue. The most common compromises from this issue are a template replacement issue where one of the common templates has its pre-parsed version replaced. They often also leave a backdoor through a plugin as well. The following steps will allow you to find these problems in the system: 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. Even these should be manually reviewed. 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 iframes. These are also often signs of a hacked site. Query for step 4 and 5 - SELECT title, phpcode, hookname, product FROM plugin WHERE phpcode LIKE '%base64%' OR phpcode LIKE '%exec%' OR phpcode LIKE '%system%' OR phpcode like '%pass_thru%' OR phpcode like '%iframe%'; 7) Run this query: SELECT styleid, title, template FROM template WHERE template LIKE '%base64%' OR template LIKE '%exec%' OR template LIKE '%system%' OR template like '%pass_thru%' OR template like '%iframe%'; It checks the templates for compromising code. 8) Check .htaccess to make sure there are no redirects there. This isn't a vBulletin issue per se but can cause problems. After finding issues and removing them, your software may not be completely operational. There are a couple things you need to do. 1) Delete any additional administrators you did not authorize. Usergroups -> Usergroup Manager. Look at users listed as Primary and Secondary users in the Administrator group. 2) You need to rebuild your styles. The easiest way to do this is to run upgrade.php. 3) Rebuild your plugin Datastore by opening Plugins / Products -> Plugin Manager and saving the display order. 4) Finally, Upgrade your system to the latest version. If you're exposed to this vulnerability, you are running out of date software. The only way to remain secure is to upgrade to the latest versions. 5) This is optional but I recommend placing .htaccess password controls on the install, includes, packages and vb directories as well as admincp and modcp.
https://www.vbulletin.com/forum/sho...o-avoid-being-Hacked-by-TeamPS-i-e-p0wersurge I found it the other day. I was going to post the link but yeah must have forgotten (the other day that is, not now).
It's not a database/templates/style issue though; it's a deleted-site-files-from-public_html issue; so fail.
Haha, fuck up, like you all of a sudden know more than someone who is a main techie on two forums. Don't claim that as your own ffs.
It isn't my own....probs should have quoted it or something but it's pretty obvious that I don't know that much. I know a little bit of programming but tbh I have no desire to learn it properly and make it my profession. Clearly isn't my writing and not there to perceive....
