NEWS
The WordPress GPL That Makes Nulled Plugins Look Legal
WordPress treats plugins as GPL, so cheap copies look legal. Georgia Tech found malware in over 97% of nulled plugins in one dataset.
WordPress.org tells plugin authors that their PHP inherits the GPL, and that rule is why a $10 copy of a $150 plugin can look legal. Georgia Tech researchers later found malware in more than 97% of the nulled plugins in one large backup set, and the people who pull those sites offline are often the hosts.
The cheap zip is not a pirate stall in a back alley. It sits in the same search results as clubs that claim, sometimes honestly, that they are only passing on GPL code.
WordPress.org Treats Plugins as GPL Derivatives
WordPress ships under GPLv2 or later. The project’s license page says derivatives of WordPress code inherit that license, and it names plugins and themes as the examples. It also admits the legal line is not a court ruling.
There is some legal grey area regarding what is considered a derivative work, but we feel strongly that plugins and themes are derivative work and thus inherit the GPL license. If you disagree, you might want to consider a non-GPL platform such as Serendipity (BSD license) instead.
WordPress.org, License page
That is the official line, not a blogger’s gloss. WordPress.org says plugins and themes are derivative work, and the directory on WordPress.org requires GPL-compatible code for anything hosted there. The GPLv2 terms from the Free Software Foundation are what give a later holder the right to run the code, read it, change it, and pass copies on.
A paid plugin can still be GPL software. The vendor is allowed to charge. What the buyer usually pays for is the rest of the product: updates, support, license checks, and anything that lives on the vendor’s servers. Someone who only has the PHP files does not magically get those services.
The Thesis Fight Locked That Rule In
The rule did not become community law by accident. In 2009 WordPress asked the Software Freedom Law Center whether theme PHP counted as a derivative of WordPress. The center’s view, as WordPress later used it, was that PHP loaded into WordPress was derivative, while CSS and images could stand as separate work.
Chris Pearson, creator of the Thesis theme, sold that theme on his own terms. Matt Mullenweg, co-founder of WordPress, argued the PHP had to follow the GPL. They fought it out in public in July 2010, and Mullenweg raised the prospect of a lawsuit. Pearson then announced a split license: GPL on the executable PHP, a separate license on images, CSS, and client-side JavaScript.
HOW THE GPL RULE GOT LOCKED IN
- 2009: The Software Freedom Law Center reviews WordPress themes and treats the PHP as derivative of WordPress, with CSS and images able to stand apart.
- July 2010: Mullenweg and Pearson argue in public over whether Thesis must follow the GPL.
- 22 July 2010: Pearson announces a split license so the PHP can be shared under the GPL.
No court ever wrote a clean test for every plugin. The practical result was simpler. Anyone who wanted to stay in the WordPress world treated plugin PHP as GPL, and a secondary market grew up around that assumption. Some shops copy the files as released. Some shops edit them.
97% of Nulled Copies in One Dataset Were Malicious
Ranjita Pai Kasturi and colleagues at the Georgia Institute of Technology built a scanner they called YODA and ran it across nightly backups from CodeGuard, covering more than 400,000 WordPress sites from July 2012 to July 2020. The paper, presented at USENIX Security in 2022, found 47,337 malicious plugins on 24,931 sites. At the time they published, 94% of those malicious plugins were still active. Every compromised site in the set had two or more infected plugins.
Nulled copies were the ugly subset. The paper counted 8,525 malicious nulled plugin instances. A separate count found 6,223 sites with at least one nulled plugin. Over 97% of the nulled plugins in that set showed malicious behavior. That figure is the study’s sample, not a live census of every shop still online.
Piracy also had a price tag on the other side of the till. The researchers estimated $228K in developer revenue lost to pirated plugins, $41.5K spent on 3,685 malicious plugins sold on legitimate markets, and $834K of previously benign plugins infected after they were already installed. More than 40,000 plugin instances were hit after deployment, often by one bad plugin infecting others on the same site.
NULLED SHOPS IN THE GEORGIA TECH SET
| Source in the study | What YODA saw |
|---|---|
| vestathemes.com | 3,177 plugin instances on 2,398 sites, the most common nulled source in the set |
| theme123.net | 100% of copies seen were malicious |
| themelot.net | 100% of copies seen were malicious |
| Unknown shops | 2,603 of the 8,525 malicious nulled instances, just over 31% |
The paper is careful on a point the headlines skip. Not every nulled file in the wild is malware. In this backup set, almost all of them were. Malicious payloads on nulled copies showed up in force from late 2015, even though nulled shops had been around since 2013.
Wordfence later said the volume story changed. Its 2024 annual security report, posted in April 2025, said nulled plugins are no longer a major threat, with very few infections coming from those installs compared with 2020, when they were among the top sources. That is a statement about how often Wordfence was seeing those infections, not a claim that edited zips became safe.
A 2025 Campaign Renamed the Wordfence Folder
On 9 September 2025, Wordfence’s threat team described a campaign built around tampered premium plugins. Samples reached them on 26 August 2025. Six detection signatures went out on 2 September 2025 to paid Wordfence, Care, Response, and paid CLI customers. Sites on the free plugin received the same signatures after the usual 30-day delay.
The interesting part was the target. One variant waited for a crafted request, then renamed the Wordfence plugin directory, which took the security plugin offline. Other builds kept a foothold so the attacker could add more malware, create administrator accounts, or steal data. The site owner who installed the “free premium” zip had turned off their own alarm.
Wordfence put the warning on X the same day.
🟦 Attention #WordPress users:
The Wordfence Threat Intelligence Team has discovered a new malware campaign that highlights the hidden risks associated with “nulled plugins”, or premium plugins that have been tampered with by third parties.
Read more:https://t.co/7SAfoYMzIs
— Wordfence (@wordfence) September 9, 2025
Paolo Tresso’s write-up for Wordfence framed the campaign as nulled plugins used to weaken your defense. The edited plugin did not only add a backdoor. It tried to make the existing defense fail, which is a different job from a random spam injector.
Sucuri kept the older warning current. On 30 March 2026 it posted that thousands of WordPress compromises still trace back to one choice, installing a nulled plugin, and that the follow-on damage still includes malware, backdoors, and SEO spam. The Georgia Tech paper is four years old. The install habit is not.
Why a Premium Badge Can Still Be Fake
A nulled zip can paint “Premium” on the dashboard and still be the free plugin with the labels changed. Mark Maunder of Wordfence wrote on 12 March 2025 that genuine Wordfence is sold only on Wordfence.com or through the WordPress plugin directory, and that several third-party plugins either restyle the free product or sit beside it and claim to unlock paid features.
Those features do not live in a PHP flag. They come from Wordfence’s cloud: current firewall rules, malware signatures, the paid IP blocklist. Maunder’s point was blunt. You cannot switch those on by editing the plugin files. You need a paid key. A cracked copy that says Premium is a costume.
The same split shows up across the commercial plugin trade. Page builders, form tools, and SEO suites often keep templates, image CDNs, AI credits, or update servers behind an account. Editing a license function does not clone that infrastructure. It only stops the plugin from nagging you.
WHAT A CHEAP COPY DOES NOT INCLUDE
- Vendor updates: The person who posted the zip cannot push security patches from the developer’s pipeline.
- Cloud feeds: Firewall rules, blocklists, and API data stay on the vendor’s servers and never arrive without a real key.
- Support: Forum access and ticket queues belong to paying customers; developers still see people open free.org threads while running an edited copy.
- A known diff: Unless you compare every file to a paid original, you cannot see whether the only change was the license check.
That last item is the security problem in one line. GPL redistribution, done cleanly, passes on the files as the developer shipped them. A nulled plugin is a modified plugin. The usual edit removes a license check. A second edit can add a hidden admin, a mailer, or a downloader, and the dashboard will still show a green “activated” badge.
Shared Hosts Inherit the Cleanup
The Georgia Tech paper named a stakeholder who never chose the zip. Hosting providers, it said, have no view of which plugins a customer installs, yet they still have to keep the platform clean. YODA was written so a host or a marketplace could run it, because the site owner is often the last person to know what is in wp-content.
When a scanner flags malware, the next email is usually from the host, not from the plugin shop. Shared accounts get suspended. Managed WordPress hosts put the site behind a holding page. Abuse desks send a list of paths and wait for a clean scan. Cleanup notes used after those suspensions keep repeating the same first step: delete nulled plugins and themes, because they are the pattern that brings the infection back.
The blast radius is larger than one wp-admin. A plugin runs with the same file and database rights as WordPress itself. SEO spam on one site can put a malware warning on the server’s shared IP. Outbound mail from the box starts landing in spam. Neighbors on the same hardware did not install the $10 zip and still share the reputation hit.
Plugin-to-plugin infection inside a single site is already in the Georgia Tech numbers. Over 40,000 previously clean plugins were infected after install, which is how one bad file becomes three. On a host that sells thousands of WordPress accounts, that is a queue of tickets, not a lecture about licenses.
GPL talk is also the cover people use when they mean a cracked file. The license really does let you copy unmodified PHP. The fee on a commercial plugin is still the thing that buys updates and a human on the other end of a ticket. Mixing those two facts is how a search result for “GPL club” and a search result for “nulled” end up looking like the same bargain.
For a throwaway test site, an admin can open the files, compare hashes, and accept the risk. For a shop, a publication, or any host account that sits beside other customers, the original developer or the WordPress.org directory is the supply chain with a name on it. A zip from an unnamed third party still runs with the same privileges as every other plugin on that server.
-
Cloud Hosting4 weeks agoUtho Asks India to Book B300 GPUs Before They Arrive
-
NEWS1 month agoRank Math PRO Joined a 2026 Pattern of Paid Plugin Backdoors
-
AI1 month agoGoDaddy Lets AI Agents Run Hosting, Email and Stores
-
NEWS1 month agoElementor Pro’s Form Bug Left Hosts Holding the Cleanup
-
NEWS4 weeks agoFirstVDS Disk Theft Exposes a Live VMmanager Flaw
-
Email Hosting1 month agoWindows Updates Cap RPC Calls and Stall Exchange Mail
-
Cloud Hosting1 month agoYandex Cloud Bots Moved to Selectel After the Strikes
-
Email Hosting1 month agoTitan Puts a $3 Inbox Beside Google on Squarespace
