All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
AlexHost unauthorized SSH Access
I've discovered unauthorized access to my AlexHost Moldova VPS starting from Jun 10 2026.
The attacker has logged in over SSH using provider-generated password which I did not change.
Along with unauthorized actions of installing Docker with "get-paid-for-traffic" software (similar to Dartnode incident), the malicious activity resulted in installing an SSH backdoor on Jul 17 2026, which allows the access with hard-coded password.
The backdoor is a pam_unix.so PAM module substitute with the following functions:
- Allow access as root with a pre-defined password, skip any logging for that login
- Log successful attempts with valid passwords for any account into a text file: login, date, plaintext password, IP
The backdoor's log file contained records of root access using the AlexHost-provided-upon-provisioning password from various IPs. This means the password has been leaked from somewhere, as I've always logged in using SSH key, but the password authentication wasn't disabled.
The hardcoded password inside the backdoor is not obfuscated in any way.
I've scanned the entire AlexHost range (on 11 Nov 2026) and checked other machines for this backdoor by SSH'ing into them with the backdoor password, and collecting /etc/{os-release,lsb_release} and such.
≈26 backdoored machines of other clients were running mostly Debian 13 and 12, but also Ubuntus and CentOSes.
I have several AlexHost VPS, and only one of them got pwned. All of the above means:
- OS templates are not backdoored: I've found no evidence upon checking, the fact that backdoor is running on Debian/Ubuntu/CentOS of different versions and not on exact single version template incline me toward this idea.
Malicious actor got access to root password of some selected servers. I could not get any incident investigation information out of AlexHost and they haven't published anything yet, thus most likely scenarios are:
- Some part of AlexHost infrastructure got breached (either the panel or email delivery which contain SSH password upon server setup)
- Malicious actions from tech support staff / trojaned tech support machine
This is amateur work: the backdoor is easy to detect, no hiding of its presence or of malicious actions have been performed. By “this” I mean the backdoor I found on my machine. There might be different attackers who got the leaked passwords, other could act smarter.
I've also scanned Dartnode and several other hosting providers for this backdoor password, and found no machines outside of AlexHost with it.
AlexHost has offered 2 months of free service for helping with investigation, which I've accepted, although I didn't do much.
SSH backdoor indicators
/usr/lib/x86_64-linux-gnu/security/pam_unix.so.1file, and/usr/lib/x86_64-linux-gnu/security/pam_unix.sois smaller than.1in size./usr/lib/locale/.cache/.system/.session_datapassword exfiltration log file
How could YOU detect password leaks
Instead of suggesting to disable password authentication to prevent this kind of attacks and to harden the system, which you all know already, I'd better tell you about pam-duress module which allows to set different passwords for a single account, each with different actions. We'll use it in an unorthodox way.
- Install pam-duress on your server
- Configure it as described in the manual, but use
[success=ignore default=ignore]forpam_duress.soline in PAM configuration, to prevent login from happening. This is important! - In
duress_signstep, input the root password you've received from the hosting provider - Change your system root password to something different
This way, when anyone attempts to log in with the password from the email/panel, the OS will behave as incorrect password has been entered, but will execute the scripts in /etc/duress.d to notify you about this attempt. It's like the root account has two (or more) passwords, but not really.
If the panel shows root password and allows to change it—do that, and enroll this changed password as additional duress password, along with the one you've received over email.
This allows to detect what has leaked exactly: panel or email server credentials.
The module works for both SSH access and IP-KVM (console).
Writing the duress action script is on you.
I've contributed .deb package compilation along with Debian/Ubuntu pam-auth-update support, but it hasn't been merged yet.

Comments
Gulp
Oof
How can I get a boyfriend this nerdy
bigger tits