Skip to content
Mastodon

Fake verification and ClickFix cleanup

Remove fake CAPTCHA malware—and the code that keeps bringing it back.

I clean fake “I’m not a robot,” fake Cloudflare verification, and ClickFix-style malware from WordPress files, database content, injected scripts, plugins, and persistence mechanisms.

Fake verification removed Injection source traced Persistence checked Caches purged and verified Review-ready website

Recognize the problem

Common fake CAPTCHA infection symptoms

One symptom does not always confirm a compromise, but several together deserve a careful investigation.

  • Visitors see a fake Cloudflare or reCAPTCHA screen
  • The page asks users to press Windows+R or paste a command
  • Only some visitors, devices, or referrers see the popup
  • The browser redirects after clicking “Verify” or “Allow”
  • Unknown JavaScript is injected into every page
  • The infection disappears temporarily after clearing cache
  • Security scanners report social engineering or phishing
  • The script returns after a theme or database cleanup

Scope of work

What fake CAPTCHA cleanup investigates

These campaigns commonly use layered injection and conditional display.

01

Injected JavaScript

Trace encoded, remote, conditional, and dynamically created scripts in files and rendered pages.

02

Database payloads

Inspect options, widgets, page content, templates, and plugin records that can inject the overlay.

03

Theme and plugin files

Check modified templates, fake plugins, mu-plugins, loaders, and compromised third-party code.

04

Persistence mechanisms

Review scheduled tasks, admin users, backdoors, remote includes, and code that restores the injection.

05

Caching and edge layers

Purge and verify WordPress, server, CDN, and browser caches after the malicious source is removed.

06

Warning recovery

Confirm visible symptoms are gone before handling Safe Browsing or vendor review steps.

How it works

A clear path from problem to recovery.

  1. 01

    Reproduce the conditional page

    Test devices, referrers, logged-out sessions, and rendered source to capture the malicious behavior.

  2. 02

    Trace the injection source

    Follow the script back through files, database, plugin hooks, remote loaders, and persistence.

  3. 03

    Remove and harden

    Clean the full chain, close the access point where possible, and purge affected caches.

  4. 04

    Retest and review warnings

    Verify clean rendering before submitting any external security review.

First-hand experience, visible evidence.

MD Pabel has worked on more than 4,500 hacked websites since 2018. Case studies and technical malware logs document the kinds of incidents behind that experience.

About MD Pabel

Common questions

Before we start.

Is fake CAPTCHA malware dangerous to visitors?+

Yes. Some variants redirect users, request notification permission, steal credentials, or persuade Windows users to run malicious commands through ClickFix-style instructions.

Why can I not see the fake CAPTCHA myself?+

Campaigns often target only logged-out visitors, mobile users, search traffic, certain countries, first visits, or uncached sessions to avoid detection by the site owner.

Can a security plugin remove it completely?+

A plugin may identify a known script, but the injection can also live in database content, custom code, fake plugins, scheduled tasks, remote loaders, or another compromised site in the account.