Resource·Store and business owners·Peak traffic readiness

Black Friday WordPress Security Checklist

Twenty checks to run before your biggest traffic day, whether that is Black Friday, a product launch or the December rush. Part 1 rules out the hack patterns that hide from site owners. Part 2 gets backups, updates, plugins and forms ready. Tick each item and watch your readiness score change.

Reviewed by Ali Yasin Jatoi, Founder & Lead Engineer

Published

How do I secure my WordPress site before a high traffic weekend?

The short answer: Rule out five hack patterns that stay hidden from site owners: a fake Cloudflare check, 302 spam redirects, altered core files, hidden admin users and must use plugin backdoors. Then confirm a backup restores, test every update on staging first, trim plugins above 15, and send a test order and a test form before traffic arrives.

If you would rather have these checks run for you every month, our Care plans from $99 per site per month include tested updates, daily backups and uptime checks.

Part 1: Which attacks should I rule out before a busy weekend?

Each of these can sit on a site for weeks without the owner noticing. On a normal day it costs a few visitors. On your biggest traffic day it costs the day.

01

A fake Cloudflare check that asks visitors to paste a command

Real Cloudflare checks never ask anyone to open Run or PowerShell and paste a command. If yours does, your site is being used to infect your visitors. The script often hides from logged in admins, search engines and security scanners, so the owner is usually the last to see it.

Check before your busy day: Log out, open a private window, and load your home page, a product page and checkout on a phone and on a Windows laptop. Any check page that asks for key presses or a pasted command is the attack.

Full fix: what to do about a fake Cloudflare check on your site.

02

Spam redirects that send visitors somewhere else

Injected URLs redirect through a 302 to gambling, pharma or replica goods sites, and they keep showing up in Search Console even after the malware is removed. The attacker usually leaves a way back in that brings the redirect rules back within days.

Check before your busy day: Search Google for site: followed by your domain and look for pages you never wrote. In Search Console, open the Pages report and look for URLs you do not recognise.

Full fix: the 302 redirect hack and the 410 Gone cleanup.

03

Core WordPress files with a backdoor added

Attackers add small backdoors to the core files WordPress loads on every request. Trojanized core files run on every request, survive plugin and theme cleanups, and look like part of WordPress until you compare them against the official release.

Check before your busy day: Compare every core file against the matching release from wordpress.org. WP CLI does this with wp core verify-checksums. Any file that does not match needs a closer look.

Full fix: WordPress core files that have been trojanized.

04

An admin account you did not create

An admin account you did not create is a confirmed backdoor. Attackers add a hidden admin so they can return after a partial cleanup, with names like wp_adminerlzp, adminer or wpsupport.

Check before your busy day: Open Users, filter by Administrator, and confirm you know every name on the list. Remove anyone who no longer works on the site.

Full fix: a hidden wp_adminerlzp admin user.

05

A must use plugin that brings the malware back

Must use plugins run on every request, load before regular plugins, and never show in the WordPress plugin list. That is exactly why attackers put their backdoor there. If malware comes back within a day of a cleanup, look here first.

Check before your busy day: Open the wp-content/mu-plugins folder on the server and confirm every file in it is one you or your host put there.

Full fix: malware that keeps coming back from a must use plugin.

Part 2: How do I get the site ready for peak traffic?

Backups verified, not just switched on

A backup only counts once it has been restored. Restore the latest copy to a staging site, click through checkout, and note how long the restore took. That is the number you need if something breaks on the day.

Updates staged before they go live

Run all plugin and core updates on staging first, check checkout and forms, then update the live site. Finish this a few days before the busy day, so nothing new lands while traffic is at its highest.

Plugin count above the threshold

Every active plugin above 15 adds to the work, because more plugins means more update conflicts and a bigger attack surface to watch. Take a backup, deactivate the ones you no longer use, and test again.

Forms tested the way a rush of visitors uses them

Place a test order, send the contact form and request a password reset. Then submit the form several times in a row from a phone, and confirm every submission and every email arrives.

The full checklist

Tick what you have done. Your answers stay in this browser only.

Part 1 checks: rule out the five hack patterns

Backups and rollback

Updates

Plugins and access

Checkout and forms

On the day

What should I do if I find one of these?

If you find one of these on a live site, do not delete files one at a time. A hidden admin or a must use plugin usually means there is more than one way in. Our emergency WordPress help is a flat $249 fix.

  1. 1

    You send the address

    Call, WhatsApp or use the form. Tell us what you see. No login needed to start.

  2. 2

    A human replies within 8 to 12 hours

    A senior engineer looks at the site from the outside first and tells you what is likely wrong.

  3. 3

    Fixed price agreed

    Emergency repair is a flat $249. You agree before any paid work starts.

  4. 4

    We fix and verify

    We fix the cause, then check the pages that matter: home, forms, checkout and login.

  5. 5

    Written note

    You get a plain English note of what broke, what we did and how to stop it happening again.

Common questions

When should I run this checklist?

At least a week before your biggest traffic day, so there is time to restore a backup, test updates on staging and fix what you find. Run the Part 1 checks again the day before.

Is this checklist only for Black Friday?

No. It works before any high traffic day: a sale, a launch, a campaign or the December rush. The checks are the same every time.

Can I run the Part 1 checks without a developer?

Some of them. Anyone can load the site logged out on a phone, search Google for their own domain and review the administrator list. Comparing core files and opening the must use plugins folder needs server access.

Why does the number of plugins matter?

Every active plugin above 15 adds to the work, because more plugins means more update conflicts and a bigger attack surface to watch.

What if I find one of these attacks?

Do not delete files one at a time, because the attacker usually has more than one way back in. Our emergency WordPress help is a flat $249 fix, and a human replies within 8 to 12 hours.