Skip to content

Original statistics

The ClickFix Index

Six measurements of ClickFix activity, computed from this site’s own record, defined in full on the methodology, and published under CC BY 4.0.

Statistics as of
2026-10-11
Published campaigns
61
Indicators on record
2,045
Sources credited
30
Licence
CC BY 4.0

1 · Median observed domain lifetime

Not yet measurable

— · 288 domains carry both dates

Days between the first date any source we hold reports observing a domain and the most recent date any source or re-check did.

Read it as a lower bound: live hosts have no end date, and we observe on report dates rather than continuously. How it is computed.

25th percentile
0 d
75th percentile
16 d
Longest observed
658 d
Seen on one day only
61.8%

Most of the 288 domains carrying both dates were seen on a single date, so the median across them is zero. A zero there measures how seldom anyone has looked twice, not how long a domain lives, so we withhold it until re-checking moves it off zero.

2 · New ClickFix domains observed per week

Each domain is counted once, in the week it entered the record — not once per report that mentions it.

New ClickFix domains observed per weekWeekly count of ClickFix domains entering the ClickFixReport record, by the week of first observation, covering 52 weeks ending 2026-09-07.New ClickFix domains observed per week52 weeks to 2026-09-07 · 275 domains0408012016012025-09-152025-11-242026-02-022026-04-202026-06-292026-09-07The ClickFix Index · CC BY 4.0clickfixreport.com/clickfix-index
Week commencing Monday. The window covers at most 52 weeks and ends at the most recent week containing an observation, not at today.

The last 12 weeks, as numbers

New ClickFix domains observed per week, most recent 12 weeks
Week commencingNew domainsRelative size
2026-06-220
2026-06-290
2026-07-060
2026-07-130
2026-07-200
2026-07-270
2026-08-030
2026-08-100
2026-08-170
2026-08-240
2026-08-310
2026-09-071

138 further domains were first observed before the window opens. 762 domains carry no first-observed date and are counted in no week.

3 · Lure-theme mix

The pretext the page uses to get a command pasted. A campaign can carry more than one, so the shares do not sum to 100.

lure theme recorded for 60 of 61 published campaigns · most common: Fake CAPTCHA verification

Lure-theme mix, by number of published campaigns
Lure-themeCampaignsShareRelative size
Fake CAPTCHA verification2948.3%
Fake browser verification challenge1220%
Fake software download page610%
Fake macOS utility or troubleshooting guide58.3%
Technology company impersonation46.7%
AI tool impersonation23.3%
Fake error dialog23.3%
Fake software update notice23.3%
Fake video conference page23.3%
Invoice or payment pretext23.3%
Online marketplace impersonation23.3%
Fake Discord server verification11.7%
Fake document repair prompt11.7%
Fake secure drive portal11.7%
Fake security update notice11.7%
Fake video game download11.7%
Fake Web3 application11.7%
Fake Windows Update screen11.7%
Government agency impersonation11.7%
Hotel guest belongings11.7%
Internet and cable provider impersonation11.7%
Pirated film streaming site11.7%
Spoofed Microsoft Office document11.7%
Tax authority impersonation11.7%

4 · Target operating-system split

Which platforms each campaign was reported to target. A cross-platform campaign counts under every platform its sources name.

target OS recorded for 61 of 61 published campaigns · most common: Windows

Target operating-system split, by number of published campaigns
Target operating-systemCampaignsShareRelative size
Windows5183.6%
macOS1727.9%
Cross-platform11.6%

5 · Execution-mechanism mix

How the pasted command actually ran — the Run dialog, a terminal, a script host. Recorded as a label, never as a runnable string.

execution mechanism recorded for 57 of 61 published campaigns · most common: Windows Run dialog

Execution-mechanism mix, by number of published campaigns
Execution-mechanismCampaignsShareRelative size
Windows Run dialog3357.9%
Clipboard injection3154.4%
PowerShell2950.9%
Terminal paste (macOS)1221.1%
mshta.exe814%
PNG pixel-data steganography loader47%
rundll32 DLL run over WebDAV35.3%
Windows Terminal paste-and-run35.3%
BITS transfer download23.5%
DLL sideloading23.5%
Deno runtime running remote JavaScript11.8%
FileFix11.8%
finger.exe payload retrieval11.8%
msiexec installing a remote MSI11.8%
Windows batch script11.8%

6 · Our own extraction error rate

The rate below is produced by a blind weekly audit and by nothing else: five already-published entries re-checked against their sources by a human with the original assessment hidden. We publish it whatever it says. No entry has been audited yet.

Measured error rate
not yet measured
Entries audited
—
Found wrong
—
Extractions refused
0

“Extractions refused” counts indicator rows a database trigger rejected because their exact string was not in the archived source, so a rising count means the constraint is working. How the audit works.

7 · Use these figures

All of it is CC BY 4.0. Quote the numbers, redraw the chart, sell the article — the conditions are attribution and the date the figures were computed, because they change.

Cite as

ClickFixReport, “The ClickFix Index”, dataset clickfix-index, retrieved 2026-10-11.

https://clickfixreport.com/clickfix-index

Published under CC BY 4.0. Reuse it, including commercially, with attribution. The date above is when this record last changed, not when you opened it — the page is a versioned record, so that is the date a reader needs to find what you saw.

Credit line for a chart or a screenshot

<a href="https://clickfixreport.com/clickfix-index">The ClickFix Index</a> — ClickFixReport, CC BY 4.0

Plain text: Source: ClickFixReport, The ClickFix Index, 2026-10-11 — clickfixreport.com/clickfix-index

There is no iframe embed: the chart is plain SVG in the page markup with its credit drawn inside, so screenshot it or rebuild it in your own house style.