Website malware, made simple

A beginner’s guide for support specialists: what website malware is, how it gets in, how to spot each type, and how to guide a worried customer through it calmly.

Start with the symptom checker. Pick what the customer is telling you and see what it usually means.

Symptom checker

The customer says…

Choose a symptom to see the likely malware type.

1

What is website malware?

Malicious software built to infect, damage, or exploit a website and the people who visit it. It lives on the web server, not on anyone’s personal computer.

Web server 🪤 Infected website Your computer Visitor’s computer

Think of your computer as your house. Website malware is like someone breaking into an apartment building (the server) and setting a trap in one apartment (the website). Anyone who visits that apartment can be affected, even though their own houses are fine.

📂
It hides in many placesWebsite files, databases, or server configuration.
👻
It’s quietOften runs silently in the background.
🌐
Visitors can be hitNo download needed for it to affect them.
🔑
Passwords alone don’t fix itIt survives a password change if files aren’t cleaned.
🏘️
It can spreadOn shared hosting, one infected site can affect others in the same plan.

Why attackers do it

It’s never random. Attackers want one of five things: steal data, game search rankings (SEO spam), redirect visitors, hijack server resources, or deface the site. Knowing the goal helps you read the symptoms.

2

The seven types

Like a doctor matching symptoms to an illness, each type has its own signs and treatment. Tap one to open its card. Sites often have several at once.

🔬 Evidence lab: which type is it?

You’re looking around a customer’s site and find this. Pick the malware type it points to.

3

How malware gets in

An infection vector is the path an attacker uses to get in. Most infections come through preventable gaps, not targeted attacks. That’s good news: basic habits protect against them.

Shared hosting: one weak site risks all of them

On web and cloud hosting, sites in the same account share a file system. One outdated plugin on one site can put every other site in that account at risk. Agency plans isolate each website, which greatly reduces this.

4

How an infection grows

This explains why customers so often have several problems at once. Step through the four phases.

5

Try it: clean a self-healing infection

Self-healing WordPress malware hides in four places at once. If even one remains, it rebuilds the others. Mark the spots you’d clean, then run the cleanup.

Site status: infected

Pick which spots to clean. Hint: a customer who “only deleted the infected files” usually sees the malware come back within hours.

6

What it costs the customer

The infection is one problem; the complications often hurt more. Be factual and balanced: don’t downplay it, don’t exaggerate it.

Getting a Google warning removed

  1. Clean all malware from files and the database
  2. Fix the weakness that let it in
  3. In Google Search Console, go to Security Issues and request a review
  4. Wait for Google’s review, usually a few days
  5. Watch traffic recover gradually over the following weeks

Easy to miss: cleaning alone isn’t enough. Without a review request, the warning can stay even on a clean site. Also note: support can’t see a customer’s Search Console by default, so rely on their screenshots.

7

How to talk about it

Your role is to be the calm in the customer’s storm. Read each risky phrase and guess a better one before you reveal it.

🚫 No blame

Say “this plugin had an unlocked door,” not “you should have updated.”

🧾 Be specific

“You have a backdoor and SEO spam pages” beats “you have malware.”

🗣️ Plain words

“Bad code that damages websites,” not “server-side injection.”

🫂 Normalize, don’t minimize

It’s common and fixable, and most infections are automated, not personal.

🪜 One step at a time

Break big messes into small ordered steps.

➡️ End with a next step

Never stop at explaining the problem. Leave a plan.

If the customer blames the server: calmly explain our server-level security, without apologizing or accepting blame, then steer back to fixing the issue and preventing it. Don’t bring up server security unless they do.

8

The support playbook

The same five moves work for almost every malware case. Open each step.

1Acknowledge and calm

Acknowledge the stress briefly without amplifying it, then show progress right away.

“I understand this is stressful. This is fixable, and I’ll help you step by step. First, let me check our malware scanner, which takes about 5–10 minutes.”

2Check the Malware Scanner first
  • Always check before confirming malware. Some things only look like malware: affiliate plugins adding links, theme demo content, CDN or caching glitches, and browser extensions.
  • A clean scan doesn’t always mean a clean site. SEO spam often lives in the database (for example the wp_posts table), not in files.
  • If there are several issues, triage by urgency. Phishing comes first because it can lead to suspension.
3Explain what you found

Name the specific types. Remember the scanner shows what is infected, not exactly how the attacker got in. Point to likely causes such as outdated plugins without blame.

4Offer the cleanup options
Restore a backupQuickest free option, but only if the backup is from before the infection. It doesn’t fix the weakness that let it in.
Guided manual cleanupFine for light infections and customers comfortable with technical steps.
Paid cleanupBest for heavy infections or many files. Otherwise, an external professional service.

Paid cleanup eligibility: the site is WordPress, the server uses Monarx (not Imunify), and the domain points to Hostinger.

Full cleanup is outside support’s scope. We handle the server; the website’s content and files belong to the customer.

5End with prevention
  • Turn on automatic WordPress and plugin updates
  • Remove unused plugins and themes
  • Use strong passwords (12–15+ characters, or a password manager) and enable 2FA
  • Set up regular backups
  • If it keeps coming back, have them scan their own computer and change passwords from a clean device

Escalate immediately if you find phishing pages or signs the site is attacking others. These can lead to suspension without notice.

9

Practice real conversations

Three scenarios from the course. Read the customer’s message and pick the best first reply.

10

Investigation simulator

Four cases like the ones we see every day. Open files in File Manager, rows in phpMyAdmin, users and cron jobs, then mark each one as malware or clean. Submit when you’re done to see what you caught and what you missed.

🧠 Red flag cheat sheet (open before you start)
Code in the wrong placeAnything before <?php or <!DOCTYPE html>, or an extra first line in index.php.
Hiding tricksev​al(, base64​_decode(, gz​inflate(, hex like \​x68\​x74, or huge one-line strings.
Wrong folderPHP files in uploads, unknown files in mu-plugins, brand folders like /paypal/.
Strange destinationsDomains you don’t recognize, short links, rules that only target phones or Google visitors.
Same odd timestampSeveral files or rows changed at the same unusual time, like 03:14.
Don’t over-flagGoogle Analytics, cache plugin files, and WordPress’s own wp-cron are normal.
    11

    Check what you know

    Ten quick questions. No pressure.

    12

    Customer questions, flashcard style

    Read the question, think of your answer, then tap to flip.