One customer's website let an attacker into about 400 accounts on the same server. That is the Hostinger server breach, found on a shared server in Phoenix on November 9.
If your site is on a shared plan with any host, the sites beside it are part of your security.
What happened on the Phoenix server, day by day
On November 5, an attacker got in through "a vulnerable content management system on a customer website," Hostinger's incident report says. A content management system is the login and editor behind a site, like WordPress. The report does not say which one.
For about three days the attacker worked from inside that one account. Then they used a flaw nobody knew about yet in LiteSpeed Web Server, the software that hands pages to visitors, and broke out.
Each account on a shared server sits in its own walled space, here built with CloudLinux CageFS. The flaw let code from one website get past those walls, "eventually leading to root-level access on the server," Hostinger wrote. Root is the master key.
On November 8, Hostinger's monitoring flagged something odd. At 12:26 UTC on November 9 the company declared an incident, and from 13:30 UTC it moved the accounts to other servers and put affected sites back from backups taken before the attack.
LiteSpeed shipped a fix on November 10, and Hostinger had it on all of its shared servers by 16:03 UTC that day, webhosting.today reported. The Phoenix server is offline and held for investigation.
What the attacker read on 400 accounts
"The attacker ran code or read credentials on about 400 accounts, including database credentials and access tokens," the report says. Hostinger runs more than 5,000 servers, so this was one machine.
Database credentials are the username and password a website uses to reach the place its orders, form entries and customer details are stored. Access tokens are keys that let one system act inside another, like a payment or email account.
Hostinger says it found no sign the attacker reached its internal systems, its backups or customers' Hostinger logins. It emailed affected customers one by one and notified the authorities.
It is the second time this fall. In September, Hostinger reported a different LiteSpeed flaw used the same way on a server in Brazil, and it patched its servers the day of that attack, webhosting.today wrote.
Your site is only as locked as the wall between you and the stranger next door.
Your neighbor on a shared server is part of your security
Shared hosting puts hundreds of websites on one computer. Each owner sees only their own account. Nobody picks the neighbors.
On the Phoenix server, the way in was one customer's site. The owners of the other accounts did nothing wrong, and their database passwords were read anyway.
Take a flower shop in Frackville, on a shared plan with any host. Its site runs on WordPress, with an order form for Thanksgiving centerpieces. Every order lands in a database, and the password to that database sits in a file on the server.
The owner keeps WordPress updated every week. The account two doors down on the same server belongs to someone who stopped logging in years ago. That site is the one an attacker finds.
If the wall between accounts fails, the florist's file is one more file on the machine. Names, phone numbers and delivery addresses for every centerpiece order sit behind a password the attacker can now read.
What to ask your host about the Hostinger server breach this week
If you host with Hostinger, look for an email from November 9 or 10. Hostinger says affected customers were emailed one by one, and it answers questions around the clock through the account dashboard.
If you are with another host, the same questions apply. Ask them in writing:
- Is my website on a shared server, and how many accounts share it?
- Does the server run LiteSpeed, and does it have the fix LiteSpeed released on November 10?
- If the account next to mine is broken into, what keeps the attacker out of mine?
- Who changes my database password and my payment and email keys after a break-in, and how fast?
Then ask whoever looks after your site which content management system it runs and when it was last updated. The Phoenix break-in started with a vulnerable one.
A Freeborn Digital website keeps less on the server
Freeborn Digital builds every website as plain pages: HTML, CSS and JavaScript. There is no content management system to log into, no plugins, no PHP and no database on the site.
When someone opens a page, the server hands it over and runs nothing to build it. The two things this attacker used, a content management system to get in and database passwords to read, are not on a Freeborn Digital site.
For the Frackville florist, the centerpiece order form sends each order into the tools the shop already uses, behind their own logins. The web server holds pages and photos of centerpieces.
The domain and the site belong to the owner, hosted where the owner chooses. Freeborn Digital builds this as custom websites, launches it, and keeps it current. Send a change, a new centerpiece or the Christmas hours, and it is made.
The post on the PHP2Shell cyber attack covers the October attack on PHP, the language under most of these sites, and why a plain page gave it nothing to run.
Questions about the Hostinger server breach
Was my website part of the Hostinger breach?
Only accounts on one shared server in Phoenix, about 400 of them. Hostinger says it emailed each affected customer. If you host with Hostinger and got no email, ask through the dashboard.
What is a LiteSpeed zero-day?
LiteSpeed Web Server is the software Hostinger's shared servers use to hand out web pages. A zero-day is a flaw attackers use before the maker knows about it. LiteSpeed released the fix for this one on November 10.
Does updating WordPress protect me from this?
It closes one way in. The Phoenix attack started with one customer's vulnerable content management system and spread through the server software, which only the host can patch. Keeping your own site current still matters.
Does a website need a database to take orders?
No. A Freeborn Digital site is plain pages, and its forms send orders and bookings to the tools the business already uses. Nothing on the site stores them.
One account on a Phoenix server let an attacker into 400. Ask your host how many share yours. For a site with no database on it to read, tell Freeborn Digital what the business does at freeborndigital.com/start or 570-617-7655.
Want this for your business?
Start a Project