- Treat a single Balada marker as a full compromise — check files, database, users and cron, not just the flagged page
- Remove rogue admin accounts at the database level if they are hidden from wp-admin
- Reinstall everything clean and close the specific plugin flaw the current wave used
- Rotate credentials — Balada reuses stolen logins to reinfect ‘cleaned’ sites
This post is part of our series on WordPress attacks in the last 10 years — one major attack per day, what it was, how to detect it, how to remove it and how to keep it out. This instalment covers Balada Injector (2017 — still running).
What happened
First tracked by Sucuri in 2017 and named by Doctor Web in 2023, Balada Injector is not one exploit but an operation. It watches vulnerability disclosures the way traders watch news: each fresh plugin flaw triggers a wave. In October 2023 it rode a TagDiv theme flaw into 9,000+ sites; in January 2024 it exploited the Popup Builder flaw (CVE-2023-6000) to create rogue admins on 7,100+ sites, and by March had infected 3,900+ more. Between waves it is quiet — which fools owners into thinking it ended.
Who was exposed: Sites running any recently-disclosed vulnerable plugin or theme; weak admin logins. Why it mattered: Sucuri estimates over 1 million sites infected since 2017 — including 17,000+ in a single month in 2023, 7,100+ in January 2024, and 149,000+ across 2024 alone.
How this attack works
Entry is whatever this month’s flaw is: a plugin vulnerability, a guessed or stolen admin password, or a stolen database login. The payload then injects malicious JavaScript into site files and the database, creates hidden administrator accounts, and sets up reinfection paths. Visitors get redirected to fake tech-support pages, fraudulent lottery wins and push-notification scams — the redirects are the revenue; your traffic is the product being sold.
Campaign malware differs from a single-plugin incident in one important way: it is a business, run in waves. Each wave weaponises whichever plugin or theme flaw was disclosed most recently, infects thousands of sites in days, then goes quiet until the next flaw. The payload also layers persistence — database injections, rogue admins, and backdoor files in more than one location — because the operators expect partial cleanups and profit from reinfecting the same sites repeatedly.
Signs your site has it — and how to confirm
- Visitors report redirects to lottery, tech-support or notification-permission scam pages that you cannot reproduce
- New administrator accounts you did not create, or the users_can_register setting mysteriously on
- Injected script tags pointing to unfamiliar domains in your pages’ source
- A remote scan (e.g. Sucuri SiteCheck) flags Balada where your plugin scan says clean
Search your domain on a remote scanner (for example Sucuri SiteCheck) and in Google with spam terms, fetch key pages as Googlebot, and grep your files and database for the campaign’s known patterns — injected scripts from unfamiliar domains, encoded payloads, and administrator accounts you did not create. Finding any one marker means treating the whole site as compromised, not just the page it appeared on.
Step-by-step removal and recovery
Immediate actions for this attack
- Treat a single Balada marker as a full compromise — check files, database, users and cron, not just the flagged page
- Remove rogue admin accounts at the database level if they are hidden from wp-admin
- Reinstall everything clean and close the specific plugin flaw the current wave used
- Rotate credentials — Balada reuses stolen logins to reinfect ‘cleaned’ sites
The full protocol
- Back up the infected site, labelled infected, before touching anything.
- Maintenance mode on — stop the campaign monetising your visitors while you clean.
- Remove the payload everywhere it persists: injected scripts in files and database, rogue admins, rogue cron jobs, mu-plugins you did not install, PHP in uploads.
- Reinstall core, theme and all plugins from clean sources; delete unused and nulled extensions — they are the usual entry for the next wave.
- Close the actual entry point: update the plugin the current wave exploited, or delete it if it is unmaintained.
- Rotate all credentials and regenerate salt keys; campaign operators keep stolen logins for reinfection.
- Rescan from outside WordPress (host’s server-side scanner) and verify as Googlebot before going live again.
How to prevent it
- Update plugins the day updates land; Balada’s waves are built from disclosure lists
- Delete unmaintained plugins — several waves exploited flaws in plugins with no fix coming
- 2FA on every admin account closes Balada’s password route
- File and database scanning together; Balada deliberately persists in both
The defences repeat across this whole series for a reason: kept-updated software, unique passwords with 2FA, the fewest possible plugins, backups stored off the server, and monitoring that looks at your site the way an attacker — or Google — does. Sites rarely fall to one exotic trick; they fall to one ordinary gap.
FAQs
Is Balada one virus or many?
One operation, many payloads. The injector’s code changes between waves and obfuscation is updated constantly, which is why signature-only scanners lag behind it.
I cleaned my site and Balada came back a month later. Why?
Either a persistence point survived — a rogue admin or database injection is the usual one — or the next wave re-entered through the same unpatched plugin. Both are fixable; the second means the entry plugin must go or be updated.
Which plugins does Balada target?
Whichever was disclosed most recently. Recent waves used TagDiv Composer and Popup Builder, but the list changes with every disclosure cycle.
Next in the series and the full timeline: WordPress Attacks in the Last 10 Years — the complete guide.
JunoBizz audits, cleans and hardens WordPress sites — cloaked spam, rogue admins, poisoned plugins and everything in this series. Get the checks run before Google finds the problem.
Talk to JunoBizz