Many people picture a hacked site as a homepage with a hacker's message. Most modern attacks do the opposite and try to stay invisible. The attacker wants to use your site for as long as possible: sending spam, placing pages in search results, redirecting visitors or using server resources. Catching a compromise early means paying attention to small but recurring signs.
Signs visible from outside
Often someone else notices first. The browser may show a red warning before opening the site, or Google may label it as possibly hacked in results. Other signals include:
- pages in a foreign language or unrelated topic appearing under your domain in Google;
- visitors on phones or from search being redirected elsewhere;
- a security issue email from Google Search Console;
- your host warning about spam sent from the site or excessive resource use;
- email from your domain suddenly landing in recipients' spam folders.
Each sign can have another cause, such as a wrong SPF record for mail, but several at once deserve a closer look.
Example: a hotel in Bukhara
Foreign tourists booked rooms through a family hotel's site in Bukhara. Several guests said they never received confirmation emails, and the owner found hundreds of bounces from unknown addresses. The host also reported mass mailing from the site. The investigation found an unknown administrator created five days earlier and a PHP file disguised as an image in the uploads folder. The site looked normal, so the problem surfaced only through email.
Checking accounts and settings
wp user list --role=administrator --fields=ID,user_login,user_email,user_registered
wp plugin list --status=active
wp option get siteurl
wp option get home
Start with who can access the site, because an unknown administrator account is one of the clearest signs of a compromise. WP-CLI bypasses dashboard filters that some malware uses to hide accounts. An unknown admin, a plugin you never installed or a siteurl pointing to another domain are strong signals.
Checking files
wp core verify-checksums
find . -name "*.php" -mtime -7 -ls
find wp-content/uploads -name "*.php"
grep -rlE "eval\(base64_decode|gzinflate\(base64_decode" --include=*.php .
Core files can be compared with the official release, while for everything else you look at modification dates and locations. The uploads folder should not contain PHP files, since it normally holds only images and documents. Many recently changed PHP files without any updates on your side are suspicious, but compare with your update history, and remember attackers can fake file dates.
Cron jobs and logs
Malware often restores itself through scheduled tasks, so review crontab -l and wp cron event list for anything you did not add, especially commands downloading files. In access logs, most POST requests normally go to the login page, forms and admin-ajax.php; many POSTs to an unfamiliar PHP file may indicate a webshell:
grep "POST" access.log | awk '{print $7}' | sort | uniq -c | sort -rn | head -20
Log locations vary by host; on sayt.uz hosting logs are available in the ISPmanager panel.
First steps once confirmed
Deleting files in a hurry or reinstalling the site can hide the problem without removing its source. Record the current state first, then clean up, and change passwords from a device you trust, because some compromises start with malware stealing the owner's password.
- Take a copy of the current files and database for analysis.
- Change hosting, FTP, database, admin and email passwords from a clean device.
- Remove unknown users, files and cron jobs.
- Replace core, plugins and themes with official copies and update them.
- Find the entry point: an outdated plugin, a leaked password or another flaw.
If the entry point stays open, the cleaned site will be compromised again within days. If you are unsure where to start, open a ticket from the sayt.uz cabinet.