How to hide the fact that my client area runs on whmcs

[HOSKIA INDIA]

How to hide the fact that my client area runs on whmcs because someone trying to hack my whmcs with {php}evaL(base64_decode etc, How to hide the fact that my client area runs on whmcs it is possible ?

[Kian]

You clearly have security issues and hiding that you are using WHMCS makes no difference. It's like if the locking mechanism on the vehicle doors doesn't work on your car. You want to protect it from thiefs by hiding that fact that it's a Ferrari 🤔 The point is that you should fix your doors.

Edited June 12, 2019 by Kian

[brian!]

3 hours ago, HOSKIA INDIA said:

How to hide the fact that my client area runs on whmcs because someone trying to hack my whmcs with {php}evaL(base64_decode etc,

sadly, you're slightly more exposed than most because you previously bought a WGS product (ClientX), and when their site was hacked last year, and their WHMCS database was leaked on the internet, the hackers posted a sample list of domains using ClientX and publicly invited other hackers to have a go at hacking those sites - third from last on that list was your hoskia domain. 😲

I won't publish that hacker announcement link here (and I won't even publish the intro text as it contains a naughty word!), but I can PM you the link if you're interested to see it.

3 hours ago, HOSKIA INDIA said:

How to hide the fact that my client area runs on whmcs it is possible ?

not really - besides, your domain is out there now and no doubt being distributed to other hackers...

[WHMCS Lawrence]

To add to what @brian! said, you can customise the client area template to give your installation an unique look and feel, however the PHP file names would likely be a hint to anyone who is familiar with WHMCS and may still see attempts to a lesser degree than if your installation was running a default template.

The exploit these attackers are trying to use is quite ancient and does not affect any supported version of WHMCS (if I recall correctly, this only affected early 5.x releases and older, and was quickly patched after discovery).

Generally the most common source of intrusion can be traced to third party PHP software that has been installed alongside WHMCS, such as Joomla!, WordPress, or many others, that have publicly known exploits or weaknesses at the time. Following any compromise, a complete server or account audit is usually warranted, including searching for any files you do not recognize, in particular any shell scripts or uploaders that many hackers leave in place to allow future compromises. During a security audit, any scripts or third party software should be updated to the latest versions, including any security patches. 

Once this has been completed, our recommendation would be to delete all files on your WHMCS hosting account except for the WHMCS configuration.php file (including the files in other directories as well) in case the hackers have left any malicious files behind to be able to return later. This will allow you to begin with a "clean slate" by uploading a fresh set of WHMCS files, while using your existing database. 

Protecting your WHMCS installation is all about your server security. WHMCS can only ever be as secure as the server it is hosted on, so you need to ensure you have permissions on the server set appropriately so other shared users can't read or access your files, you also need to ensure you do not install any third party scripts which frequently have security issues in the same hosting account as WHMCS, and if possible you should consider moving WHMCS to an isolated VPS or dedicated environment for higher security.

Please also view http://docs.whmcs.com/Further_Security_Steps for information on keeping your WHMCS Installation secure.