Browser verification tile linked to a clipboard and command window, with a gold pause symbol.
Tech & Cybersecurity

ClickFix explained: when a fake CAPTCHA asks you to run a command

You open a page to read a guide or download a document. A verification box appears. It looks like another routine check, until it asks you to open a command window and paste something into it.

That change in the task deserves your attention. ClickFix is a technique that persuades people to run malicious instructions while believing they are completing a check or fixing a technical problem.

This guide explains the pattern, gives you a fictional example to assess and shows what to do depending on how far you have interacted with a suspicious prompt. You do not need to understand the command to recognise the risk.

What is ClickFix?

ClickFix is a form of social engineering: manipulating someone into taking an action that helps an attacker. The request may be presented as a fake CAPTCHA, a failed download or a browser error. A CAPTCHA is a check intended to distinguish human activity from automated bots.

The attacker’s aim is to move you from interacting with a webpage to running instructions on your device. A command is a written instruction a computer can execute. Command tools such as PowerShell on Windows and Terminal on a Mac have legitimate uses, but that does not make instructions supplied by an unexpected webpage trustworthy. Read Microsoft’s explanation of ClickFix.

Why this is worth understanding now

On 2 September 2026, New Zealand’s National Cyber Security Centre (NCSC) warned about compromised websites displaying fake verification pages. A previously genuine website can be altered to serve a malicious prompt. Familiarity with the site is therefore not enough to justify running its instructions. Read the September 2026 alert.

Mac users also need to recognise the pattern. Microsoft documented a macOS campaign in August 2026 that used fake download and verification requests. Some visitors saw deceptive prompts while others received different, apparently harmless content, making the activity harder to inspect consistently. Read the macOS campaign research.

For readers, the useful lesson is to assess the action being requested. A convincing logo or a colleague’s different experience of the page does not explain why a browser check needs access to a command tool.

How a fake check becomes a device action

The details vary, but the sequence commonly has three parts:

  1. A page presents a problem or verification request.
  2. It supplies text and asks you to move into a command tool.
  3. Running the instruction can download or launch malicious software.

1. The page supplies a reason to continue

Purpose: Notice the problem the page wants you to solve.

The prompt might say that a document cannot open or a security check has failed. Its apparent solution is positioned as a small step towards the thing you already wanted to do.

2. The instructions move outside the browser

Purpose: Recognise when the request changes from a check to device control.

The page may place text on your clipboard, the temporary store used for copying and pasting. It then tells you to open a command tool and paste that text. You may not have deliberately selected the command yourself.

3. Running the text can start the infection

Purpose: Distinguish copying an instruction from executing it.

Execution means the computer acts on the instruction. It may retrieve malware, which is software designed to cause harm. Some campaigns deliver information stealers that can take passwords or browser session data. Session data can help an attacker use an existing signed-in account.

The Swiss NCSC described this sequence in February 2026. Its advice includes using your browser’s own update controls and avoiding commands from unfamiliar sources. Read the Swiss guidance on fake verification and repair requests.

Try this fictional verification prompt

Imagine you are following a tutorial for a small portfolio project. Before the example loads, the page displays this message:

“Complete verification to continue”

“Verification could not finish. Copy the verification text, open your computer’s command window and run it to unlock the tutorial.”

This is an invented teaching example. It contains no executable command, download or real service branding.

Before continuing, ask three questions:

  • What did I come here to do? Read a tutorial, not change how my computer runs.
  • What is the page now asking me to do? Execute instructions outside the webpage.
  • What independently supports that request? A message asserting that verification failed is not evidence that this action is needed.

The decision point is the requested action. You can stop without decoding the text, identifying the attacker or proving that the page is malicious.

What to do after a suspicious prompt

Your next step depends on what happened. Be accurate when describing it to someone helping you. Seeing a prompt, copying its text and running a command are different events.

You saw the prompt and stopped

Purpose: Leave the questionable request and use a trusted route.

Close the page without following its repair instructions or using support details displayed in the prompt. For a suspected browser update problem, open the browser’s own settings. On a work device, report the page through your organisation’s usual route.

The prompt alone does not establish that your device is infected. If you are concerned about a suspicious link or download, the UK NCSC recommends running a full scan with your existing antivirus software. Read the NCSC’s advice after interacting with a scam.

Text was copied or pasted, but not run

Purpose: Keep the instruction from being executed.

Do not run it to see what happens. If it is sitting in a command tool, close that tool without executing the text. Replace suspicious clipboard contents by copying a harmless word from a document you trust.

Tell your support team whether the text was merely copied, pasted, or possibly executed. If you cannot tell, say so. You do not need to experiment to give a useful report.

You ran the command, or are unsure

Purpose: Get help with both the device and potentially exposed accounts.

For a work device, contact your IT or security team immediately through a known route, using another device if needed. Give them the approximate time, the page you visited and what you did. Follow their containment and recovery instructions.

For a personal device, use trusted security support and follow the NCSC’s infected-device recovery guidance. Open your existing security software directly rather than downloading a “cleaner” offered by the suspect page. A scan can help, but it does not guarantee that an executed command caused no harm.

Use a device you trust to follow the affected services’ account-recovery instructions. This can include changing compromised passwords, checking account settings and signing out other sessions. Removing malware does not itself recover information already stolen. Read the NCSC’s account-recovery steps.

Make the warning useful to your team

A warning such as “be careful online” leaves people to guess what careful means. A more useful team conversation names the action and the support route.

A five-minute team check

  • Show the fictional prompt above and ask what changes when it requests a command tool.
  • Confirm where colleagues should report a suspicious page or an accidental execution.
  • Agree who can help check unfamiliar technical instructions.
  • Ask your security team which device protections and restrictions are appropriate for your environment.

Make it easy to report a mistake. “I ran something and I am not sure what it did” gives a support team a starting point. Shaming someone for speaking up makes the next incident harder to discover.

Practise the judgement with Spot the Scam

Pause, check and find trusted support

Coded Female’s Spot the Scam gives you eight fictional situations per round, drawn from a bank of 20. It practises broader scam recognition, including fake technical-support pop-ups and requests for access.

As you play, identify what the message wants you to do and which route could verify the request independently. Use a hint when you need one and read the explanation after answering.

The game uses fictional messages and simulated choices. It does not require you to run commands or contact the people described.

Keep one question close

Why does this webpage need me to run instructions on my device? Ask that before following an unexpected verification or repair prompt.

For your next practical step, find and save your trusted support route now. If you work in a team, use the fictional prompt at your next short check-in and make sure everyone knows where to get help.

Sources and further reading

Sources checked on 14 October 2026. The tutorial and verification prompt are original fictional teaching examples. The featured image is a conceptual illustration. This article does not describe an incident at Coded Female.

Leave a Reply

Your email address will not be published.