Llac

Category: trojan · Aliases: Trojan:Win32/Llac, Trojan.Win32.Llac, Trojan:Win32/Llac.A, Trojan:Win32/Llac.B · Sample count (EMBER 2018): 104 · Enrichment: curated_sourced · Updated: 2026-10-15
Category: TrojanStatus: Automated SignaturePlatform: WINDOWS_PEStage: Initial Access, Execution, Credential Access, Collection, ExfiltrationFirst seen: 2013Actor: Unknown / CybercriminalIndustry: Global / Opportunistic, Consumer Endpoints, Corporate WorkstationsMotivation: Information Theft🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 7
Executive Summary
Llac (cataloged across security telemetry as Trojan:Win32/Llac, Trojan.Win32.Llac, and Trojan:Win32/Llac.A) is a stealthy information-stealing trojan and surveillance threat active across Windows platforms since 2013.

Table of Contents

Overview

Llac (cataloged across security telemetry as Trojan:Win32/Llac, Trojan.Win32.Llac, and Trojan:Win32/Llac.A) is a stealthy information-stealing trojan and surveillance threat active across Windows platforms since 2013. Designed primarily to harvest sensitive user credentials, browser autocomplete data, and system configurations, Llac is delivered via deceptive email attachments, trojanized key generators, and bundled freeware cracks. Upon execution on an endpoint, Llac verifies the execution environment, using anti-debugging routines to bypass basic sandbox analysis. It hooks Windows user input APIs to log keystrokes, extract saved passwords and cookies from installed web browsers (Google Chrome, Mozilla Firefox, Microsoft Edge), and harvest local system metadata including active process lists, IP configurations, and user privilege levels. The trojan secures persistence by adding autostart values to the Windows Registry Run keys (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) and establishes encrypted outbound HTTP communication with attacker-controlled command-and-control servers to exfiltrate stolen credentials and download secondary malicious payloads.

Known aliases

Threat reports may refer to this family under multiple names:

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Derived From / Upstream Ancestry: Classic Windows Password Stealers

Known Derivatives & Downstream Variants: Llac.A · Llac.B

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-BDABinary De-obfuscation & UnpackingAnalyzeT1027Utilize memory dump scanners and entropy inspection to unpack encrypted stagers during process creation.
D3-PIADProcess Injection Analysis & DetectionDetectT1055Monitor cross-process thread creation (CreateRemoteThread) and asynchronous procedure calls (QueueUserAPC).
D3-MFAMulti-factor AuthenticationHardenT1056.001Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless.
D3-SDASystem Discovery AnalysisDetectT1082Alert on rapid enumerations of systeminfo, hostname, and registry hardware trees in short intervals.
D3-NTINetwork Traffic InspectionDetectT1105Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols.
D3-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

Tiered Detection Rules (Cisco CAIRN Model)

Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:

Tier 1 Primitive Artifact Rule (Fast Triage)

Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.

rule MALWARE_WIN_LLAC_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Llac"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "llac" ascii wide nocase
        $s2 = "trojan:win32/llac" ascii wide nocase
        $s3 = "trojan.win32.llac" ascii wide nocase
        $s4 = "trojan:win32/llac.a" ascii wide nocase
        $s5 = "trojan:win32/llac.b" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Tier 2 Behavioral Context Rule (Process Chains & Sigma)

Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.

title: SystemHelpDesk Detection - Llac (Trojan) Execution & Triage
id: 58c2a0e1-e4ac-5439-ad45-3a2cdab6fb69
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Llac malware family. Detects suspicious execution from temporary user directories
  with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/llac
- https://malware-families-catalog.systemhelpdesk.com/defensive/downloader-dropper-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1056_001
- attack.t1055
- attack.t1105
- attack.t1547_001
- attack.t1082
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \cmd.exe
    - \powershell.exe
    - \cscript.exe
    - \wscript.exe
    CommandLine|contains:
    - AppData\Local\Temp
    - -WindowStyle Hidden
    - /e:jscript
    - bitsadmin /transfer
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: medium

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_LLAC_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Llac tradecraft"
        tier = "T3 - Attribution Fingerprint"
        confidence = "High (Confirmed Family Signature)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        // Core family identifier & heuristic payload signatures
        $attrib_str = "llac" ascii wide nocase
        $pe_magic = "MZ" ascii
        $net_marker = "http" ascii nocase
    condition:
        uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

  1. Immediately disconnect the endpoint from network and internet interfaces to halt credential exfiltration to the C2 server.
  2. Force credential resets for all email, banking, and enterprise accounts authenticated on the compromised host.
  3. Capture a memory dump to extract injected modules and identify active C2 IP addresses and exfiltration domains.
  4. Remove persistent registry run keys and scan storage drives using an offline antimalware scanner like Microsoft Defender Offline.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

  1. Do not allow the infected host to remain on the network, as the trojan continuously transmits keystroke logs and browser cookies.
  2. Avoid relying solely on file deletion, as active in-memory threads can regenerate persistence mechanisms upon user logon.

References & External Analysis

Frequently Asked Questions

What is the Trojan:Win32/Llac malware?

Llac is an information-stealing Windows trojan designed to log keystrokes, steal browser credentials, and exfiltrate host data.

How does Llac gain initial access to endpoints?

It is predominantly distributed through weaponized email attachments, software cracks, keygens, and deceptive freeware downloads.

What sensitive information does Llac target?

It targets browser-saved passwords, session cookies, cryptocurrency wallets, user keystrokes, and operating system metadata.

How does Llac achieve persistence on infected systems?

It writes autostart entries into HKCU\Software\Microsoft\Windows\CurrentVersion\Run masquerading as legitimate software.

What containment actions are recommended for Llac?

Isolate the endpoint, revoke exposed account credentials, terminate malicious processes, and perform full offline remediation.

How do I remove the Llac Trojan from Windows?

Manual removal of Llac is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.

Is Llac a virus or a Trojan?

Llac is classified as a Trojan. Unlike traditional viruses that infect files, modern malware like Llac typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.

What are the main symptoms of a Llac infection?

Symptoms of Llac can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.

Protect Your Network Against Trojans

Want to prevent Llac and similar threats from compromising your organization? Read our comprehensive defensive guide: Banking Trojan Protection for Businesses.

📣 Threat Intel Correction or Update?

Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.

Need help with an active incident? Published by the SystemHelpdesk Threat Intelligence Team.

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/llac.json

Ecosystem & Interactive Environments

This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.