Can a Trusted WordPress Plugin Turn Malicious? How Supply Chain Attacks Work
A WordPress plugin you've trusted for years can turn malicious through a routine update. We explain the three ways it happens: hijacked developer accounts, plugin sales to bad actors and breached vendor download systems. We walk through real cases from Display Widgets to Gravity Forms, plus the warning signs and hardening steps that matter most.
At a glance
The short version
This infographic sums up the article on one page. Save it, share it with your team, or read on for the detail and the sources behind it.
In this article · 8 sections · 8 min
- 01What a supply chain attack means for a WordPress site
- 02Three ways a trusted plugin turns malicious
- 03Why “just keep everything updated” isn’t the whole answer
- 04Warning signs to watch for
- 05Hardening steps that reduce your exposure
- 06If you suspect a plugin has been compromised
- 07Why expert oversight matters for a public website
- 08Key takeaways
Yes, a WordPress plugin you have used safely for years can turn malicious through an ordinary-looking update. It usually happens in one of three ways: an attacker takes over the developer’s account, someone buys the plugin and changes the code, or the vendor’s download system is breached. You can’t remove this risk entirely, but you can make your site much harder to hit and much quicker to recover. Below we explain how these attacks work, what real incidents looked like, and the steps that make the most difference.
What a supply chain attack means for a WordPress site
Most WordPress security advice is about keeping attackers out of your site. A supply chain attack skips that step. The attacker compromises something you already trust, such as a plugin, a theme or the developer’s update channel, and then lets the normal update process deliver the malicious code to you.
That is why these attacks are effective. The code comes from the official source, it arrives as a routine update, and most site owners have no reason to question it. Your firewall and login protections can be working perfectly and still not stop it, because nothing ever broke in. You invited the update.

Three ways a trusted plugin turns malicious
1. Hijacked developer accounts
Developers who publish on WordPress.org have accounts with “commit access,” which means they can push new versions to every site that runs their plugin. If an attacker gets into one of those accounts, they can publish an update that looks legitimate.
That is what happened in June 2024. An attacker took over five WordPress.org developer accounts with commit access. The developers had reused passwords that had already shown up in outside data breaches, and the attacker used the accounts to add malicious code to their plugins. The first case to come to light was Social Warfare. On June 24, 2024, the Wordfence Threat Intelligence Team found that the plugin had been infected with malware through the official WordPress repository.
The response showed how seriously the ecosystem takes this kind of incident. The WordPress.org Plugin, Security and Meta teams paused new plugin releases, dealt with the most likely affected accounts first and then contacted the remaining plugin authors. The root cause, though, was password reuse, the same habit that puts many small business accounts at risk.
2. Plugin ownership changes
Plugins are bought and sold like any other small software business. Most sales are harmless. Sometimes, though, the buyer’s real interest is the installed base, meaning thousands of sites that will accept whatever the next update contains.

One early example is from 2017. The original author sold the Display Widgets plugin, which had about 200,000 active installs. The new owner released versions with a backdoor that let them publish spam content on sites running the plugin, and WordPress.org eventually removed it permanently. Getting rid of it was not simple. WordPress.org removed the plugin several times between June 22 and September 8, 2017, and each time the attacker put it back.
A more recent case shows how patient these buyers can be. According to Patchstack, the EssentialPlugin company was sold on Flippa in 2025 to a buyer called “Kris,” whose first commit added a backdoor to all of the company’s plugins. Patchstack says the backdoor was later activated across more than 20 plugins to install malware on thousands of WordPress sites. The malicious code was pushed in September 2025 under a harmless-looking commit message: “Check compatibility with WordPress version 6.8.2”.
The waiting was deliberate. Austin Ginder of Anchor Hosting reported that the altered plugins stayed dormant for eight months to avoid quick detection. During that time, thousands of WordPress users installed them before the backdoor was activated, and more than 30 plugins were later shut down.

3. Compromised vendor download systems
Premium plugins usually aren’t distributed through WordPress.org. They come from the vendor’s own website and update servers, and those systems can be targeted as well.
In July 2025, Gravity Forms, a premium plugin its maker says is used on more than 5 million sites, briefly contained a backdoor after a supply chain attack. Rocketgenius CEO Carl Hancock said only manual downloads were affected, not automatic updates. Specifically, the affected versions were 2.9.11.1 and 2.9.12, and only copies downloaded manually or installed through Composer between July 10 and July 11, 2025. Installs and updates done through the built-in plugin updater were not affected.
This was not a one-off. Over about 12 months, three premium plugins (BuddyBoss, Gravity Forms and Groundhogg) were hit by supply chain compromises. That pattern shows attackers deliberately going after vendors’ update and download systems.

Why “just keep everything updated” isn’t the whole answer
Every one of these attacks reached sites through an update or a fresh download, which can make it seem like updating is the problem. It isn’t. Outdated plugins with known vulnerabilities remain one of the most common ways WordPress sites get compromised, so you should keep updating.
The fix is to pair updates with awareness. Know what you have installed, know who maintains it, keep backups you can roll back to, and watch for changes you didn’t expect. Updates fix known holes. Awareness and recovery planning protect you when the update is the hole.
Warning signs to watch for
None of these proves a plugin is malicious, but each one is a reason to look more closely:
- The author or company name changes in the plugin listing, or the support forum mentions new ownership.
- The plugin disappears from WordPress.org or is marked as closed. Removals often follow security problems.
- An update changes much more than its changelog says, especially when it’s labeled as a simple “compatibility” fix.
- New admin users appear that nobody on your team created.
- Unfamiliar pages, links or spam content show up, sometimes visible only to search engines or logged-out visitors.
- Your host or security scanner flags modified files or unexpected outbound connections.
- A long-quiet plugin suddenly starts releasing updates after months of silence.
Hardening steps that reduce your exposure
You can take most of these steps in an afternoon. A few need ongoing attention.

- Audit your plugins and themes. List everything installed, including inactive items. Delete anything you no longer use. Deactivated plugins still sit on your server and can still be updated.
- Prefer fewer, well-maintained plugins. Every plugin is a vendor you’re trusting. If one plugin can do the job of three, fewer is usually better.
- Download only from official sources. Use WordPress.org or the vendor’s own built-in updater. Never use “nulled” or redistributed copies of premium plugins.
- Keep reliable, off-site backups. Make sure you can restore to a point before a bad update. Test a restore at least once so you know it works.
- Use unique passwords and two-factor authentication on your WordPress admin, hosting account and any plugin vendor accounts. The 2024 incident started with reused passwords, and the same habit can expose your site.
- Limit administrator accounts. Give people the lowest role they need, and remove accounts for staff or contractors who have moved on.
- Use file-change monitoring or a security scanner so you’re alerted when core, plugin or theme files change unexpectedly.
- Follow security advisories from reputable WordPress security researchers so you hear about compromised plugins quickly.
If you suspect a plugin has been compromised
- Deactivate and remove the plugin. Don’t simply wait for the next update.
- Check for new admin users and remove any you don’t recognize.
- Change passwords for WordPress, hosting, FTP/SFTP and the database, and turn on two-factor authentication where it’s available.
- Scan your files for backdoors. Attackers often leave code behind elsewhere, so removing the plugin may not be enough.
- Restore from a clean backup if you’re unsure. Check that the backup predates the compromise.
- Bring in a professional if customer data, payment pages or bookings could be affected. Cleanup and any notification obligations depend on your situation.
Why expert oversight matters for a public website
These incidents share a frustrating feature: they look normal. A compatibility update, a change of maintainer or a quiet plugin can all be harmless, or they can be the start of a compromise. Telling the difference takes time, attention to security news, and comfort reading code and server logs. Most business owners, understandably, would rather spend that time running their business.
That is the real case for having a knowledgeable person responsible for your site’s security, whether that’s someone on your team, a trusted contractor or a managed hosting provider. You aren’t paying for magic protection. You’re paying for someone who notices early, responds quickly and keeps a clean backup ready. Hoke Designs has designed websites since 2007 and offers managed hosting. If you’d like help reviewing your plugin list or your recovery plan, our support desk at support.hokedesigns.com is a good place to start.
Key takeaways
- Trusted plugins can turn malicious through hijacked developer accounts, ownership changes or breached vendor download systems.
- Real cases range from Display Widgets in 2017 to the 2024 WordPress.org account takeovers and the 2025 EssentialPlugin and Gravity Forms incidents.
- Keep updating. Pair updates with a lean plugin list, official sources, tested backups, strong unique passwords and file monitoring.
- Watch for ownership changes, closed plugins, surprise admin users and updates that don’t match their changelogs.
- If something looks wrong, remove the plugin, rotate credentials, scan for leftovers and get professional help when customer data is involved.
If you’d like a second set of eyes on your site’s security, call (424) 209-8199 or send a message via our contact form, and a person will reply within one business day.
Images are presented for illustration purposes only.We use real photographs when we need to show what was happening at a real event.
Keep reading
More on Security
Is a Security Plugin Enough to Protect Your WordPress Site?
A security plugin runs inside WordPress, so it can be bypassed. Here's why plugins carry 96% of new WordPress vulnerabilities, and the five layers that protect…
How to Read a WordPress Vulnerability Report and Patch Fast
Serious WordPress flaws can be exploited within hours of disclosure. Here's how to read an advisory, what a CVSS score does and doesn't tell you, what…
How Card Skimmers Hide in WordPress Checkouts and Booking Forms
Magecart-style skimmers can copy every card typed into a WooCommerce or booking checkout while orders keep going through normally. This guide explains how they get in…
Hoke Designs
Questions about your own website?
Talk to the team that writes these articles and looks after dozens of sites every day. You’ll get a straight answer.


