Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Security · Explainer

Are Nulled WordPress Plugins Safe?

Short answer

No, nulled WordPress plugins are not safe. They are premium plugins copied and changed by an unknown person to skip the license check, and Wordfence found that such copies typically contain backdoor code. You cannot verify what else was changed, and the copy gets no security updates from the vendor.

Key takeaways

  • A nulled plugin is a premium plugin copied and changed to skip its license check, then shared outside the vendor's own channel.
  • Wordfence found malware from nulled plugins or themes on 206,000 sites in 2020, over 17% of all infected sites it saw.
  • A backdoor can stay quiet until a specific web request wakes it, so a site can look fine while it is compromised.
  • Nulled copies get no vendor updates, so every flaw found after install stays open on your site.
  • Deleting the plugin folder, checking for unknown admin accounts, and scanning the whole site are the first steps after an install.

What is a nulled WordPress plugin?

A nulled plugin is a premium WordPress plugin that someone copied, changed to skip its license check, and shared outside the vendor's own sales channel.

Wordfence defines nulled plugins and themes as pirated copies of premium products with their license checking features disabled or removed, and says they typically contain backdoor functionality (Wordfence 2020 threat report).

The person who nulls a plugin edits its code. You cannot see what else changed without reading every file in the package.

A backdoor is hidden code that lets an attacker return to your site later without your password. It is the main thing that makes a nulled copy different from a legal free plugin.

Are nulled WordPress plugins safe?

No. A nulled plugin is not safe, because you cannot check what an unknown person changed in code that runs with full access to your site.

WordPress's own hardening guide gives this advice: "Do not get plugins/themes from untrusted sources. Restrict yourself to the WordPress.org repository or well known companies." (Hardening WordPress)

Not every nulled copy is proven to contain malware. That is the wrong test, because you have no reliable way to prove that a given copy is clean.

Wordfence's 2024 annual report said it saw very few infections from nulled plugins and themes that year, so the risk is not the same every year. That finding does not make an unknown package safe, because one clean copy tells you nothing about the next download (Wordfence blog).

What is inside a nulled plugin?

A nulled plugin can hide several kinds of extra code, and the plugin still works normally while the extra code waits.

  • Backdoors. Hidden code that lets an attacker run commands or return later.
  • Hidden admin accounts. Code that creates an administrator you did not add.
  • SEO spam. Links or pages added to your site to boost other sites in search results.
  • Redirects. Code that sends some visitors to other sites, often only visitors from search engines.
  • Data theft. Code that reads form entries, orders, or login details and sends them elsewhere.
  • Security kill switches. Code that turns off your security plugin so the rest stays hidden.

The best-known example is WP-VCD, a malware family that came pre-installed in nulled themes from a network of download sites. Wordfence counted it on 154,928 sites in 2020, which was 13% of all infected sites it saw that year (Wordfence 2020 threat report).

A recent forum case shows the same pattern with plugins. A site owner found files flagged as a nulled Wordfence copy, including a plugin called “Wordfence Security Activ@tor” version 1.4.0, which is not a Wordfence product (WordPress.org support forum).

What do the numbers say about nulled plugins?

The largest public count comes from Wordfence's 2020 threat report, which drew on its scanner and its site cleaning team.

FindingNumberSource
Sites with malware from a nulled plugin or theme, 2020206,000Wordfence
Share of all infected sites that yearOver 17%Wordfence
Sites hit by WP-VCD malware, 2020154,928Wordfence
Share of infected sites hit by WP-VCD13%Wordfence
Malicious files found on WordPress sites, 2020Over 70 millionWordfence
WordPress sites with malicious files, 20201.2 millionWordfence

Wordfence's scanner found malware from a nulled plugin or theme on 206,000 sites in 2020, accounting for over 17% of all infected sites (Wordfence 2020 threat report).

The wider picture makes the update problem worse. Patchstack counted 11,334 new vulnerabilities across WordPress in 2025, a 42% rise on 2024, and 91% of them were in plugins (Patchstack State of WordPress Security in 2026).

Patchstack also found that 46% of those flaws had no fix from the developer when they were made public. A nulled copy cannot receive a fix even when one exists.

What happened in the 2025 tampered-plugin campaign?

In September 2025, Wordfence researchers described a campaign built on tampered premium plugins, and the details show why a nulled copy can look safe for months.

The infected copies were older versions of two major premium plugins. Their hidden code ran on every page load but stayed dormant until a specific URL request woke it up.

Once triggered, the code disabled the security plugin by renaming its folder, created a new administrator or promoted an existing user, and could switch the security plugin back on later so nothing looked wrong.

A scan that runs while the backdoor is dormant may find nothing. An active security plugin is not proof that a site is clean.

Why do nulled plugins never get security updates?

A nulled copy has no valid license, so the vendor's update channel never serves it. Your dashboard only offers updates from WordPress.org or from a vendor server tied to a license.

That leaves the copy frozen at an old version. Every flaw found after that version stays open on your site, and you get no warning about it.

Patchstack measured a weighted median of 5 hours from disclosure to mass exploitation for heavily attacked flaws in 2025 (Patchstack State of WordPress Security in 2026). An unpatched plugin is an open door during that window.

A plugin that WordPress.org closes also stops getting updates through your dashboard. The closure page explains what happens next (what happens when a plugin is closed on WordPress.org).

How can you tell if a plugin on your site is nulled?

Work through this list in your dashboard and in your file manager. One match is a warning, and two or more mean you should treat the plugin as untrusted.

  1. Open Plugins, then Installed Plugins, and note the version of each premium plugin.
  2. Compare that version with the current version on the vendor's own site. A nulled copy is often far behind.
  3. Look for a license field that never accepts a key, or no license screen at all.
  4. Check for update notices. A premium plugin that never offers an update is a red flag.
  5. Compare the folder name, plugin name, and text domain with the vendor's product. Tampered copies often rename one of these.
  6. Open Users, then All Users, and filter by Administrator. Delete nothing yet, but note any admin you did not create.
  7. Look in wp-content/mu-plugins and wp-content/uploads for PHP files you did not put there.

You can also check a plugin's known flaws in the WPScan vulnerability database before you decide what to do (WPScan vulnerability database).

If a plugin does not appear on the Plugins screen but its files are still in wp-content/plugins, treat that as a serious warning. A plugin that hides is never a good sign.

What should you do if you already installed one?

Do not just deactivate it. Deactivating leaves the files on your server, and a backdoor in another file can reactivate the problem.

  1. Take a backup first, so you keep a record of what was there.
  2. Delete the whole plugin folder from wp-content/plugins.
  3. Delete any related files in wp-content/mu-plugins and any stray PHP files in wp-content/uploads.
  4. Check Users, then All Users, for administrators you did not create, and remove them.
  5. Change the passwords for every administrator, your hosting account, and your database.
  6. Replace the plugin with a clean copy from WordPress.org or the vendor's own site, or remove it for good.
  7. Run a full scan with a security plugin, and run an outside scan with Sucuri SiteCheck (Sucuri SiteCheck).

Even a vendor's own package can carry malware, which is why a clean reinstall matters. In October 2026, some copies of Rank Math SEO PRO version 3.0.123 downloaded between October 15, 2026 at 20:02 UTC and October 16, 2026 at 07:12 UTC contained malware.

Rank Math released version 3.0.124 as the clean replacement (Wordfence advisory).

Rank Math told sites that activated an affected package to treat the site as compromised, because updating alone would not remove hidden files or accounts. The same rule applies after a nulled plugin.

If you find changes you cannot explain, ask a professional cleaner for help. Backdoors often come in pairs, and one missed file brings the infection back.

Are free plugins and GPL downloads the same as nulled?

No. A free plugin from WordPress.org is not nulled. Its author publishes it there, updates it, and the directory lists its version history.

GPL is a license, not a safety check. Many premium plugins are GPL licensed, so sharing their code is not always a copyright breach. But a GPL label on a download site does not prove the file is unchanged.

What matters is the source, not the label. A file from WordPress.org or the vendor's own site comes from the author. A file from a download site comes from a stranger.

Free and premium plugins differ in support, updates, and features, and the free version often covers what a small site needs (free vs premium WordPress plugins).

How can you get premium features without a nulled copy?

Start with the free version of the plugin from WordPress.org. Many premium plugins have a free version with the core features, and you can check whether it covers your need before paying.

Look for a different free plugin that covers the same job. The directory lists alternatives, and a smaller free plugin that does one thing well often beats a nulled copy of a large one.

Check the vendor's own pricing page for a cheaper plan or a single-site license. Premium plugin prices vary widely, and a single-site license is often far cheaper than an agency plan (how much premium WordPress plugins cost).

Also check what renewals cost before you buy, since a low first-year price can rise later (plugin license renewal prices explained).

If a plugin is abandoned, replace it rather than hunting for a free copy elsewhere. The checks for spotting an abandoned plugin take a few minutes (how to find abandoned WordPress plugins).

What mistakes should you avoid?

Avoid these habits, because each one leaves a door open for the next infection.

  • Installing a nulled copy “just to try it” and then forgetting it is there.
  • Entering a real license key into nulled files. A key does not clean altered code.
  • Trusting one clean scan as proof. Dormant backdoors can sleep through a scan.
  • Deleting only the visible plugin and leaving files in mu-plugins or uploads.
  • Downloading from a site because it looks professional. A polished page proves nothing about the files.
  • Reusing the same backup to restore a hacked site without checking the backup first.

Frequently asked questions

Can a nulled plugin work fine for months?

Yes. A backdoor can stay dormant until a specific web request wakes it, so the plugin can work normally for months while the hidden code waits. A site that looks fine is not proof that it is clean, which is why you should check the plugin's source and version rather than trusting how it behaves.

Is it illegal to use nulled WordPress plugins?

It depends on the plugin's license and where you live. Many premium plugins are GPL licensed, so copying the code is not always a copyright breach, but the copy can still break the vendor's terms and misuse its trademarks. The security risk is separate from the legal question, and it applies even when the license allows sharing.

Can a security scan prove a nulled plugin is clean?

No. A scan checks files against known malware signatures, and a new or dormant backdoor may not match any of them. A clean scan is a good sign, not proof. The only reliable check is the file's source: if it did not come from WordPress.org or the vendor, you cannot confirm what is inside it.

What if I only use a nulled plugin on a staging site?

A staging site is still a risk. It often shares a database, passwords, or hosting account with the live site, and a backdoor there can reach the same files and credentials. Keep staging copies clean too, and use the free version of the plugin or a test license from the vendor instead.

Does deleting the plugin remove the backdoor?

Not always. Deleting the plugin folder removes that copy, but the backdoor may have left files in other folders, hidden admin accounts, or scheduled tasks. After deleting it, check your users, scan the whole site, and look for stray PHP files in the uploads and must-use plugin folders.

Where should I download WordPress plugins instead?

Get free plugins from the WordPress.org plugin directory and premium plugins from the vendor's own website. Those are the two sources WordPress's hardening guide recommends. If a vendor does not sell directly, use a seller the vendor names on its own site.

Sources

  1. The Wordfence 2020 WordPress Threat Report Wordfence
  2. Hardening WordPress WordPress.org
  3. State of WordPress Security in 2026 Patchstack
  4. WPScan Vulnerability Database WPScan
  5. Malware Found in Some Rank Math SEO PRO 3.0.123 Downloads Wordfence
  6. Sucuri SiteCheck Sucuri

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test