TL;DR: DriveSurge routes ClickFix and FakeUpdates traffic through thousands of compromised sites, according to Silent Push. Pattern hunting for injected scripts, redirects, and browser prompts matters more than blocking single indicators.
Editorial analysis by NHI Mgmt Group, based on content published by Silent Push: “Meet DriveSurge: A New Threat Actor Using ClickFix and Fake Update Drive-By Attacks in Thousands of Compromised Sites”.
Key questions
Q: Why do fake browser update prompts and ClickFix flows remain effective?
A: They work because they convert routine user behaviour into execution.
Q: How should security teams detect a campaign that uses a traffic distribution system?
A: Track the infrastructure, not just the payload.
Q: What breaks when trusted websites are used to deliver malware through fake updates?
A: Reputation-based trust breaks first.
Practitioner guidance
- Hunt for injected web resources Look for unexpected externally loaded JavaScript, especially site-specific query strings, filename fingerprints, and redirect logic on otherwise legitimate websites.
- Block copy-paste execution paths Add detections for clipboard replacement, terminal launch from browser context, and users pasting commands that resolve to curl, bash, or base64 pipelines.
- Treat fake browser updates as execution events Escalate browser update prompts that lead to downloads of ZIP files, DLLs, or executables as malware delivery, not as nuisance pop-ups.
Bottom line: DriveSurge uses compromised websites and traffic steering to convert normal browsing into a malware delivery path.
Glossary terms: ClickFix, Traffic Distribution Service, Initial access broker, Trust-mirroring delivery
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
DriveSurge is best understood as an initial-access supply chain, not a single lure campaign. The report describes a broker-like model that combines compromised sites, traffic steering, fake updates, and downstream delivery. That matters because it turns web compromise into a reusable service layer for other threat actors. Practitioners should treat this as a distribution ecosystem whose value lies in access conversion, not only payload execution.
A few things that frame the scale:
- 28% of secrets incidents now originate outside code repositories, in Slack, Jira, and Confluence, and are 13% more likely to be categorised as critical than code-based leaks, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: What should teams do when a compromised site starts serving fake updates or terminal fixes?
A: Treat it as an incident involving both web compromise and endpoint exposure. Contain the affected site, block the delivery infrastructure, and review endpoints for downloaded archives, executed scripts, and persistence attempts. If the lure reached developer or admin users, widen the review to privileged workstations because the impact can quickly move from browser session abuse to broader compromise.
👉 Read our full editorial: DriveSurge shows how ClickFix campaigns scale through compromised sites