• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Server hacked: control panel login doesn't function

HMnet

Basic Pleskian
Hi @all!

I have a huge problem with my 1&1 RootStart - Plesk 8.1.
Yesterday the server was hacked, with my admin-password :-(

The hacker replaces all inxex.html, index.php and login.php files with his index.html with foreign data an he deleted all logfiles.

I managed it to restore the data of my customers, all systems are ok now.

But I can't login into Plesks Control Panel. I replaces the files in /usr/local/psa/admin/htdocs with the original files from Plesk, which ich had on another server. Now I get the error:
"The file login.php3 is part of Plesk distribution. It cannot be run outside of Plesk environment."

I tried to reinstall or to upgrade plesk by rpm-files. This doesn't function. I got many errors.

Had anyone another idea to solve this problem?

THX, HMnet
 
You never know what else the hacker did with your machine (rootkits, backdoors, keylisteners, etc.). I'd say reimage and restore customer data from backups. That's the only way to be sure.
 
Ok, you are right. That's what I have to do in a quiet minute.

But I thought I can quickly solve the problem, so I can manage the server again, until I can reimage the server.

Brand :confused:
 
I'd also suggest a hefty firewall in front of your machines. I learned that lesson a long time ago. Also you may want to lock down the admin user's ability to login to the admin panel to specific subnets.

I only allow necessary ports through my firewall to my plesk servers.

TCP
FTP 20, 21
SSH - 22
SMTP - 25
DNS - 53
HTTP - 80
POP3 - 110
IMAP4 - 143
HTTPS - 443
Adminserv - 8443

Optional TCP
SMTPS - 465
SMTP Submission - 587
993, 995 for Secure POP and IMAP

UDP
DNS - 53

Also do not grant shell access to anyone by default. Its not necessary in most cases.

Thats just my thoughts. I've had my history of being hacked.

Daily backups and weekly imaging is always a good idea to!

Thanks,
James
 
Back
Top