Executive SummaryRisk level: High
What happened

LeakNet ransomware gains initial access via the ClickFix technique – compromised websites display fake error messages that trick users into running commands – and uses a Deno-based in-memory loader to execute code without writing files to disk.

Who is affected

Users who visit compromised sites and follow fake 'fix' instructions, and their organizations.

Why it matters

Social-engineering access plus fileless, in-memory execution evades file-based detection and complicates forensics.

Immediate recommended actions

  • Train users never to paste/run commands from website error prompts.
  • Hunt for Deno and unexpected script interpreters running with broad permissions.
  • Monitor web proxy/DNS for malicious loader domains.
  • Maintain offline backups and an updated incident-response plan.
How to read this report. Items are labelled by confidence: Confirmed stated as fact in the source, Reported described by the source, Potential analyst inference, and Requires Validation to be confirmed in your environment. Where the source lacks detail this is stated as “Not specified in the source material”.

Key Technical Findings

Vulnerability / Campaign Type

Ransomware (LeakNet) using ClickFix social engineering and a fileless Deno loader.

Affected Systems

Endpoints whose users execute the ClickFix commands.

Initial Access Vector

ClickFix via compromised websites showing fake error messages.

Execution Method

Deno-based in-memory loader executes code in memory (T1086-adjacent scripting).

Persistence

Not specified in the source material.

Privilege Escalation

Not specified in the source material.

Defense Evasion

Fileless, in-memory execution to bypass file-based detection.

Credential Access

Not specified in the source material.

Lateral Movement

Not specified in the source material.

Data Exfiltration

C2 over web protocols (T1071.001).

Impact Level

High – data encryption with ransom demands.

Technical Background

LeakNet’s ClickFix tactic compromises legitimate sites to display fraudulent error messages, then convinces users to run ‘fix’ commands that download and execute the ransomware. A Deno-based in-memory loader runs code directly in memory, avoiding disk artifacts and complicating forensic investigation, with C2 over web protocols (T1071.001).

The combination of human-driven access and fileless execution defeats many file-based controls. Defenses center on user awareness (never run website-provided commands), behavioral detection of script interpreters, and egress monitoring.

Attack Chain Analysis

  1. Initial Access

    ActivityClickFix: fake error prompts on compromised sites.

    EvidenceUsers running pasted commands.

    TelemetryProxy logs, EDR command lines.

    Detection opportunityFlag interpreters launched from browser-adjacent activity.

  2. Execution

    ActivityDeno in-memory loader runs code.

    Evidencedeno run with broad permissions.

    TelemetrySysmon EID 1, EDR.

    Detection opportunityAlert on deno –allow-all and fileless execution.

  3. Command and Control

    ActivityCommunicate over web protocols (T1071.001).

    EvidenceOutbound to loader/C2 domains.

    TelemetryProxy/DNS.

    Detection opportunityMonitor for connections to malicious domains.

  4. Impact

    ActivityEncrypt files and demand ransom.

    EvidenceMass encryption.

    TelemetryEDR/FIM.

    Detection opportunityAlert on rapid mass file changes.

Deep Technical Behavior Analysis

The defining behaviors are ClickFix social engineering and fileless Deno execution. Because little touches disk, command-line and behavioral telemetry (script interpreters with broad permissions, browser-to-shell sequences) and egress monitoring provide the best detection.

Specific loader domains and indicators are not specified in the source material and require validation.

Indicators of Compromise

No indicators of compromise were provided in the source material.

Indicators of Behavior

Behavioral indicators to hunt for even when atomic IoCs are limited (Potential — validate against your baseline).

Behavioral Indicator Description Data Source Confidence
Anomalous PowerShell execution Encoded/obfuscated commands, download cradles, or unusual parent-child process lineage. Sysmon EID 1, PowerShell 4104 Potential
Suspicious child process lineage Office or web/service processes spawning script hosts or shells. Sysmon EID 1, EDR Potential
Security log clearing Event log cleared or audit policy changed to hinder visibility. Windows Security 1102, 4719 Potential
New service / scheduled task creation Unexpected persistence via services or tasks. Security 7045, 4698; Sysmon Potential
Web shell-like activity New/modified server-side scripts in writable web paths; anomalous POSTs. Web access/error logs, FIM Potential
Abnormal 403/404/500 patterns Enumeration or exploitation attempts against endpoints. Web server logs, WAF Potential
Beaconing to rare destinations Periodic outbound connections to newly-seen domains/IPs or direct-IP C2. Proxy, firewall, DNS logs Potential
Unusual DNS queries High-entropy or rare domains; possible tunneling. DNS resolver logs Potential
Authentication anomalies Spraying/stuffing, impossible travel, or MFA fatigue patterns. IdP/VPN logs, Azure AD/Okta sign-ins Potential

Detection Engineering Guidance

Defensive detection logic (Potential — tune to your environment). No exploit code is included; logic is for hunting and alerting only.

T1071.001 — Application Layer Protocol: Web Protocols
  • ObjectiveDetect C2 over web protocols
  • Suspicious patternBeaconing to rare destinations
  • Data sourceProxy, firewall, DNS
  • False positivesAdmin tooling/automation; baseline before alerting.
  • ResponseTriage host, validate scope, preserve evidence, contain if confirmed.
pseudo: periodic outbound (low jitter) to newly-seen domain/IP
  with small uniform payloads => alert(level=medium)
Platform Log Source What to Look For Priority
Windows Security Event Log Logon (4624/4625), service (7045), task (4698), log clear (1102) High
Windows Sysmon Process creation (1), network (3), image load (7), LSASS access (10) High
Windows PowerShell Operational Script block logging (4104), module logging High
Endpoint EDR / Defender telemetry Process tree, persistence, tamper attempts High
Web Web server access logs Anomalous POSTs, new endpoints, web-shell-like requests High
Web Web server error logs Repeated 403/404/500 bursts on single endpoints Medium
Identity IdP / VPN logs Impossible travel, spraying, MFA fatigue High
Network DNS resolver logs Rare/high-entropy domains, tunneling Medium
Network Proxy / firewall logs Beaconing, direct-IP C2, exfil volume High

MITRE ATT&CK Mapping

Tactic Technique ID Technique Name Relevance Detection Opportunity Confidence
Command and Control T1071.001 Application Layer Protocol: Web Protocols Communications over web protocols to mask C2 traffic. Monitor HTTP/S traffic for anomalies. Reported
Execution T1086 PowerShell Execution of encoded PowerShell commands. Sysmon Event ID 1; check for unusual command-line arguments. Reported

Incident Response Guidance

  • Validate exposure and confirm whether the issue applies to your environment.
  • Preserve evidence (memory, disk, relevant logs) before remediation.
  • Isolate affected hosts/accounts if compromise is suspected.
  • Collect volatile data and review the log sources listed above.
  • Hunt for the indicators of behavior and any related atomic indicators.
  • Rotate potentially exposed credentials, keys, and session tokens.
  • Remove persistence (tasks, services, keys, web shells, cron, OAuth grants).
  • Patch affected systems; reimage where integrity cannot be assured.
  • Run post-remediation validation and a BAS/security-validation retest.

Remediation and Hardening

  • Patch affected systems and reduce internet-exposed services.
  • Enforce MFA and least-privilege for privileged and remote access.
  • Improve endpoint telemetry (Sysmon/EDR) and PowerShell logging.
  • Restrict script execution and constrain LOLBins where feasible.
  • Monitor persistence locations and disable unnecessary services.
  • Segment critical assets and review privileged accounts.
  • Rotate secrets and remove credentials from configuration files.
  • Tune SIEM/EDR detections, then validate controls after changes.

Business Risk

  • Service disruption: degraded or unavailable systems during compromise or recovery.
  • Data exposure: risk to sensitive, regulated, or customer data depending on scope.
  • Regulatory exposure: potential breach-notification and compliance obligations.
  • Financial impact: incident response, downtime, and potential extortion costs.
  • Brand and trust impact: reputational damage with customers and partners.
  • Operational continuity: ransomware can halt critical business processes until restored.
  • Identity blast radius: compromised accounts can expand access across cloud and SaaS.

Executive Takeaway

What leadership needs to know: Social-engineering access plus fileless, in-memory execution evades file-based detection and complicates forensics. Current assessed risk: High.

Prioritise: patching/exposure reduction, identity hardening (MFA, least privilege), and detection coverage for the techniques above.

Validate after remediation: re-test controls with breach & attack simulation to confirm the relevant techniques are now prevented or detected.

Validating Your Defenses with Valitrix

A proactive approach to cybersecurity involves continuously validating your defenses against sophisticated threats like LeakNet ransomware. The Valitrix Breach and Attack Simulation (BAS) platform emulates specific techniques outlined in the MITRE ATT&CK framework, including the tactics employed by LeakNet. By simulating these attacks in a controlled environment, organizations can assess their detection and prevention capabilities, ensuring that security measures are not only theoretical but practically effective against real-world scenarios.

Through automated testing that mimics actual adversarial behavior, Valitrix provides security teams with actionable insights into their current posture. This continuous validation process enables organizations to refine their defenses, ensuring they are resilient against evolving threats like LeakNet ransomware.

Key Takeaways

  • LeakNet ransomware utilizes ClickFix via compromised websites for initial access.
  • This tactic involves tricking users into executing malicious commands under false pretenses.
  • The Deno in-memory loader enhances the stealth of the ransomware, complicating detection efforts.
  • User education and proactive security measures are critical for defense against such advanced threats.

Frequently Asked Questions

What is ClickFix in the context of ransomware?

ClickFix is a social engineering tactic that misleads users into executing harmful commands by presenting fake error messages as legitimate issues needing resolution.

How does the Deno in-memory loader work?

The Deno in-memory loader enables ransomware to execute code directly in memory, evading detection from traditional security tools that focus on file-based analysis.

What can organizations do to protect against LeakNet ransomware?

Organizations should prioritize user education, rigorous website monitoring, deploying advanced endpoint protection, and maintaining an updated incident response plan to effectively mitigate risks associated with LeakNet ransomware.