Jump to content

can't login (Empty file AdminLoginController.php)


Recommended Posts



I am using Prestashop version and it happened that I can't login into BO (once a week). If this happened I go to FTP and the file AdminLoginController.php is always empty 0 kb size. So I replace it by original file - then works everything ok.


I already tried to change password to FTP - (there were some weird files on FTP which I deleted - all of them) and I also changed access to BO and login folder on FTP. But these changes haven't helped. AdminLoginController.php was empty again today.


It looks like someone can get to FTP files but only I have regular access. Do anybody have some suggestions?


Thank you so much in advance!


Link to comment
Share on other sites

  • 1 month later...

Your must consider your database and ALL passwords and all system data as compromised. All passwords includes:


- customer passwords

- administrator user passwords

- database credentials (username, password)

- email adresses

- your salt to hash the passwords

- your email / smtp passwords

- eventually even FTP or SSH login credentials


If you only restore your PrestaShop from a backup, you will get hacked again and again. Updating your shop might help - together with changing all password related data. I would also change the mail address I use as administrator.


One of the major culprits in terms of getting hacked are file upload mechansms which are used to inject code (instead of uploading images) to your server. However, there are also many other ways. There are also a number of known modules which security flaws. Look here:



Edited by Scully (see edit history)
Link to comment
Share on other sites

By the way, it is not obvious that the overwritten file points to new hackings. It is possible that some code still remains in your systems and is executed from time to time. One could use cron (but unlikely) but rather functions which are modified but not executed on a daily basis. But when executed, the infection spreads again.


Recently I have seen injeted code where the PayPal Module has partially been overwritten. To hide the change, the injected code set back the modification timestamp to the time prestashop was initially installed. This made it hard to figure out file changes by timestamp. At the end there was only the solution for a complete new setup with new release and a fresh installation.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...