GPL vs Nulled WordPress Plugins: How to Tell Them Apart
WordPress GPL · November 9, 2026

Look for almost any premium WordPress plugin and, besides the developer's own store, you'll find two other kinds of offer: GPL copies and “nulled” downloads. Both usually cost less than a licence from the developer, and on a download page they can look identical. The difference lies in what has been done to the files and who stands behind them, and it decides whether you are installing the developer's code or somebody else's.
Two definitions
A GPL copy is the developer's own release, passed on as the GNU General Public License allows. The code is unchanged, including the part that asks for a licence key. You don't get the key itself, so the developer's updates, support and cloud services are not part of it. Our explainer on what a GPL plugin is covers the licence in detail.
A nulled copy is a release someone has altered so that the licence check is removed, bypassed or fed a fake or leaked key, and which is then shared, usually with no name attached. Those edits are the selling point, and they are also the problem: once a stranger has changed the code, you can no longer tell what else they changed.
Notice what decides the label. It isn't the price, and it isn't the word “GPL” on a download page. It is whether the files are the developer's release, untouched, from a source that answers for them.
Why the difference matters
Code nobody vouches for
A plugin runs with the same permissions as WordPress itself: it can read your database, create users and write files. Altered copies have been used to slip in backdoors, hidden administrator accounts, spam links and redirects that only logged-out visitors see. One long-running malware family, known as WP-VCD, spread largely through nulled themes and plugins. Infected packages carried an extra file, class.theme-modules.php or class.plugin-modules.php, that compromised the site on activation and then spread to other WordPress sites in the same hosting account.
Not every nulled file is infected. The trouble is that you can't tell which ones are without auditing the code line by line, and that audit costs more than a legitimate copy.
Old versions and no clean way forward
Nulled downloads often lag well behind the developer's releases, so security fixes shipped long ago may be missing. Each update then means hunting for the next altered copy and taking the same gamble again.
Search visibility and reputation
Injected spam pages and redirects can get a site flagged by search engines and browsers. Cleaning up and asking for a review takes time, often far more than the plugin was worth.
Licensing grey areas
The GPL itself allows people to modify GPL code, so the legal position depends on the details. Nulled bundles often contain parts that were never released under the GPL, or rely on a key belonging to someone else's account. That is a question for a lawyer rather than a blog post, but it is one more reason to avoid them.
How to tell them apart before you download
- Look for an accountable seller. A real store says who it is and how to reach it, publishes terms and a refund policy, and states plainly what it delivers. Our terms of service, for example, set out what each purchase includes and that we are not affiliated with the original authors.
- Read the wording. “Nulled”, “cracked” and “pre-activated” describe exactly the alterations above. A seller using those words is telling you the files have been changed, which is reason enough to walk away.
- Check how files are delivered. Downloads tied to an account and an order are traceable. File lockers, link shorteners and download buttons that open advertising pages are not. Password-protected archives can't be checked by most virus scanners until they are opened, and a WordPress plugin is never an
.exefile. - Ask how the site pays for itself. The GPL does allow giving copies away, so “free” proves nothing on its own. But a portal that earns from aggressive advertising and offers no one to complain to has little reason to care what is inside its files.
How to check a plugin you already have
If you're unsure where a ZIP came from, inspect it before it goes anywhere near a live site:
- Scan the archive with an up-to-date antivirus tool. A clean result is reassuring, not proof; PHP backdoors are often missed.
- Read the file list. Watch for PHP files with random-looking names, PHP files inside image or font folders, and the WP-VCD file names mentioned above.
- Look at the licence screen on a test site. A plugin that reports itself as activated although you never entered a key has had its licence check changed.
- Compare with an original if you or a client have the developer's own ZIP of the same version. Any difference in the files is a red flag.
- Watch a test install. New administrator accounts, unexpected outgoing connections or new PHP files in
wp-content/uploadsare all reasons to stop.
Developers can also search the code for obfuscation, which legitimate plugins rarely need. From a terminal, inside the folder where you extracted the plugin:
grep -rnE "eval\(|base64_decode\(|gzinflate\(|str_rot13\(" .
A match is not a verdict, since some legitimate code uses these functions, but a long unreadable string fed into eval() deserves a much closer look.
If a nulled plugin is already on your site
Work through it calmly and in order rather than simply deleting the plugin and hoping:
- Take a full backup of the site as it is now and set it aside for investigation, not for restoring.
- Check Users for administrator accounts you don't recognise and remove them.
- Delete the nulled plugin or theme and install a clean copy from the developer or a trustworthy GPL source.
- Reinstall WordPress core files and every other plugin and theme from clean copies, because some infections edit files beyond the one they arrived in.
- Scan with a security plugin or your host's malware scanner, and look for PHP files in
wp-content/uploads, which should only hold media. - Change every password (WordPress users, hosting, database, SFTP) and generate new secret keys and salts in
wp-config.php. - Check the other sites in the same hosting account.
- If a search engine has flagged the site, request a review once it is clean.
If you have a clean backup from before the plugin was installed, restoring it and then changing passwords is often the quickest route. When in doubt, a professional clean-up costs less than a second infection.
Where a GPL store fits
A GPL store sits on the other side of that line. At WordPress GPL, every download is the developer's release as published, with nothing added and the licence checks left as they are, which is why some plugins show an activation notice you can dismiss. The GPL licence page explains what that means for every file, the FAQ covers downloads and support, and the refund policy explains when you get your money back within 14 days, for example when a file doesn't work and can't be fixed.
If you try a lot of plugins for client work, a membership covers the whole catalogue of plugins, themes and Elementor kits for a fixed period, so there's no reason to go digging through download portals.
FAQ
Are nulled plugins illegal?
There's no one-line answer, and this isn't legal advice. The GPL permits changes to GPL code, but nulled bundles often include material that was never GPL-licensed, or keys tied to someone else's account. The security risk applies either way.
Is a GPL plugin the same as a nulled plugin?
No. A GPL copy is the developer's unmodified release; a nulled copy has had its licence checks altered by a third party. They can share a name and a price range and still be very different files.
Why does my GPL plugin ask for a licence key?
Because the developer's activation check is still intact. The key connects to their services, such as updates, support and cloud features, which aren't part of a GPL copy. Our plugin installation guide explains how to handle the prompt.
Can a security plugin detect nulled code?
Often, but not always. Scanners recognise known malware such as WP-VCD, while a new or custom backdoor can slip past. Trustworthy sources and a test install beat detection after the fact.
How do I keep GPL plugins updated safely?
Download newer versions from the same trusted source and install them over the old copy after taking a backup. Our guide to updating GPL plugins and themes walks through each step.
Comments
Be the first to comment.
Leave a comment
Comments are moderated before they appear.