How to Check a Downloaded Plugin for Malware
A plugin gets full access to your site and your database the moment you activate it. Premium plugins in particular travel through many hands before they reach a download page — this catalog included — and a redistributed file is not guaranteed to match what the developer originally released. That is not a reason to panic; it is a reason to verify. Here is how we check every file before it is published, and how you can run the same checks yourself in about ten minutes.
How we check files before publishing
Every plugin and theme in this catalog goes through the same pipeline before its download link goes live:
- Antivirus scan. The archive is scanned with ClamAV plus a set of heuristic rules that flag known PHP malware signatures.
- Obfuscation heuristics. We search the code for the classic packing patterns —
eval(),base64_decode(),gzinflate(),str_rot13()— and review every hit. Most turn out to be legitimate vendor libraries (PDF generators, font tools, JWT helpers); anything we cannot explain blocks publication. - A real installation on an isolated server. Each file is installed and activated on a clean WordPress test environment that has no connection to this site or its visitors. We watch for fatal errors, unexpected database tables, new cron jobs and anything else the installation does.
- Outbound traffic monitoring. During the test installation we log every DNS request and outbound connection the product makes. Calls to the developer’s own update or font servers are normal; anything else is investigated before the file goes live.
The results are published on the product pages themselves — look for the “We tested” section, for example on WP Rocket or Advanced Custom Fields Pro: the exact version tested, the test environment, and what the installation did.
How to check a file yourself
1. Scan it on VirusTotal
Upload the ZIP to VirusTotal — it runs the file through dozens of antivirus engines at once. Clean across the board is a good sign, but signature scanners regularly miss custom PHP backdoors, so treat it as a first filter, not a verdict.
2. Diff it against a reference copy
If a free version of the same plugin exists on WordPress.org, download it and compare the two folders (WinMerge on Windows, diff -r on macOS/Linux). Differences where the premium build adds features or license handling are expected; changed core-logic files, or files that exist only in your copy, deserve a hard look.
3. Grep for the classic patterns
Extract the ZIP and search the PHP files for eval(, base64_decode(, gzinflate( and str_rot13(. Legitimate plugins use these occasionally — but a long unreadable blob wrapped in them, especially near the top of a file or in a file unrelated to any real feature, is a red flag.
4. Activate on a test site, never straight on production
Use a local WordPress install or your host’s staging feature. Activate the plugin, click through its settings, and keep an eye on the Users list and Settings → General. On a live site, a security plugin adds a second pair of eyes — Wordfence has a free scanner and firewall that catch changed files and known signatures.
Red flags that mean “delete the file”
- New administrator accounts you did not create, or code that calls
wp_create_userwith administrator rights for no feature-related reason. - Outbound connections to unrelated domains right after activation — a plugin has no reason to send your site URL or admin email anywhere except the developer’s own licensing server.
- Chained obfuscation —
eval(gzinflate(base64_decode(...)))-style wrappers hiding entire payloads. Serious vendors do not ship code they cannot show. - Files that do not belong: PHP files inside
images/oruploads/folders, or files named to imitate WordPress core (wp-logging.php,class-wp-cache.php).
After installation
Whatever the source, keep a scheduled backup running — the free UpdraftPlus handles it — and keep plugins updated. In practice, most compromised sites are hit through a legitimate plugin that was several versions behind on a known vulnerability, not through a booby-trapped download. And if you install redistributed GPL plugins regularly, our GPL licensing guide explains why the sources vary so much — and our manual update guide shows how to keep such plugins current without losing settings.