Learn as if you will live forever, live like you will die tomorrow.

   +1 555 87 89 56   80 Harrison Lane, FL 32547

HomeBlogWebsite SecuritySocGholish / FakeUpdates: The Fake Browser Update That Installs Malware

SocGholish / FakeUpdates: The Fake Browser Update That Installs Malware

⚡ The fix in short
  • Scan remotely as well as locally — this family hides from owners and from some local scans
  • Remove injected scripts from files AND database content; check posts, options and widgets
  • Reinstall core, theme and plugins clean; the injection point is usually a vulnerable plugin
  • Rotate credentials and audit admins — your site is a delivery asset, and operators protect their access to it

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 SocGholish (FakeUpdates) (2017 — disrupted June 2026).

What happened

SocGholish — also called FakeUpdates — has run since at least 2017. Its operators compromise websites and inject a JavaScript framework; visitors to those sites are shown a polished, browser-specific ‘your Chrome is out of date’ page. The ‘update’ they download is a remote-access trojan, and access to infected computers is sold onward — SocGholish has been linked as an initial-access route for ransomware operations including groups associated with LockBit and RansomHub. It took a multinational law-enforcement operation in June 2026, seizing over 100 servers and domains, to disrupt it.

Who was exposed: Compromised WordPress (and other CMS) sites used as delivery pages; the real victims are the sites’ visitors. Why it mattered: Sucuri’s remote scanner detected SocGholish on 143,242 sites in 2023 alone. In June 2026, Operation Endgame seized its infrastructure and cleaned 14,971 compromised WordPress sites.

How this attack works

The injected script profiles the visitor — browser, operating system, location — and decides whether to show the lure. Security researchers and site owners are deliberately shown nothing, which delays detection. The payload rotates domains and code constantly, so the same infected site serves different malicious files across a single day. For the site owner, the cruel detail is that nothing on the site looks broken: your pages work, your admin works, only your visitors are being hunted.

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 reporting a browser-update prompt on your site that you cannot reproduce yourself
  • Injected JavaScript in your theme, posts or widgets referencing unfamiliar domains, often obfuscated
  • A remote scan flags SocGholish/NDSW while your own browsing looks clean
  • Sudden appearance of script content in the wp_posts or options data you did not add

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

  • Scan remotely as well as locally — this family hides from owners and from some local scans
  • Remove injected scripts from files AND database content; check posts, options and widgets
  • Reinstall core, theme and plugins clean; the injection point is usually a vulnerable plugin
  • Rotate credentials and audit admins — your site is a delivery asset, and operators protect their access to it

The full protocol

  1. Back up the infected site, labelled infected, before touching anything.
  2. Maintenance mode on — stop the campaign monetising your visitors while you clean.
  3. 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.
  4. Reinstall core, theme and all plugins from clean sources; delete unused and nulled extensions — they are the usual entry for the next wave.
  5. Close the actual entry point: update the plugin the current wave exploited, or delete it if it is unmaintained.
  6. Rotate all credentials and regenerate salt keys; campaign operators keep stolen logins for reinfection.
  7. Rescan from outside WordPress (host’s server-side scanner) and verify as Googlebot before going live again.

How to prevent it

  • Keep every extension updated; compromised delivery sites are recruited through known flaws
  • Use a firewall that inspects injected content behaviour, not just known signatures
  • Monitor with a remote scanner on a schedule, because owner-side checks are designed to fail
  • Warn visitors fast if you confirm infection — their machines, not your pages, took the payload

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

If SocGholish was taken down in 2026, is it over?

Operation Endgame seized infrastructure and cleaned nearly 15,000 sites, but the technique — fake update lures on compromised sites — is copied by other groups (ClearFake works similarly). Keep the detection habits.

Does SocGholish steal my site’s data?

Its business is your visitors’ computers, not your database. But the compromise that lets it in gives the attacker full access, so clean as a full breach regardless.

Why didn’t my security plugin flag the injection?

The scripts are obfuscated, rotate domains, and are served conditionally. Behaviour-based and remote scanning catch more of this family than static signatures do.

Next in the series and the full timeline: WordPress Attacks in the Last 10 Years — the complete guide.

JUNOBIZZ WEBSITE SECURITY
Worried your site is already compromised?

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

© UiCore 2026. All Rights Reserved.