Loki
Table of Contents
Overview
TrojanSpy:Win32/Loki (universally known as **LokiBot**) is one of the most prevalent, enduring, and dangerous information stealers on the cybercriminal market. Sold cheaply on underground forums, LokiBot is designed for the rapid, automated exfiltration of a massive variety of sensitive data, including web browser passwords, cryptocurrency wallets, FTP credentials, email accounts, and SSH keys. It is a favored tool for both low-level cybercriminals and advanced APT groups as an initial data-gathering mechanism.
Understanding LokiBot (Information Stealer)
To an end-user, a LokiBot infection is completely silent; the malware executes, steals the data in seconds, and often terminates itself to avoid detection. For a SOC analyst, LokiBot is a severe credential compromise event. Because it targets so many different applications, a single infection can lead to the compromise of the user's personal bank accounts, corporate VPN access, and server infrastructure (via stolen FTP/SSH keys).
Execution and Credential Harvesting Mechanics
LokiBot is heavily distributed via malicious spam campaigns (malspam) containing weaponized Office documents (macros) or archived executables (`T1566.001`). It is also frequently dropped by exploit kits. Upon execution, it uses Process Hollowing (`T1055.012`), often injecting its payload into a legitimate Windows process like `vbc.exe` or `explorer.exe`. Once running in memory, LokiBot iterates through a massive hardcoded list of target applications (Chrome, Firefox, Outlook, FileZilla, PuTTY, Bitcoin Core, etc.), querying their specific credential storage locations and decrypting the stored passwords (`T1555`). It packages the stolen data into a compressed archive and exfiltrates it to a C2 server via HTTP POST requests (`T1048.003`), often accompanied by a distinct user-agent string and unique hardware ID profiling the infected machine.
Indicators of Compromise & Impact
The impact is catastrophic credential loss leading to immediate account takeovers and lateral movement. Host-based IoCs include EDR alerts for 'Suspicious Process Hollowing' and rapid, unauthorized access to browser SQLite databases (like `Login Data`) and email credential stores. Network IoCs include outbound HTTP POST traffic containing specific URL patterns (e.g., `fre.php` or `five/fre.php`) associated with default LokiBot C2 panels.
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
| Technique | Name | Tactic | Official Spec |
|---|---|---|---|
T1555.003 | Credentials from Password Stores: Credentials from Web Browsers | Credential Access | ATT&CK ↗ |
T1055.012 | Process Injection: Process Hollowing | Defense Evasion | ATT&CK ↗ |
T1048.003 | Exfiltration Over Alternative Protocol: Exfiltration Over Unencrypted/Obfuscated Non-C2 Protocol (HTTP POST) | Exfiltration | ATT&CK ↗ |
T1566.001 | Phishing: Spearphishing Attachment | Initial Access | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1566.001: Scan email attachments for malicious macros, scripts, or suspicious archive files.
MITRE D3FEND™ Defensive Countermeasures
Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-NDF | Network Data Filtering | Isolate | T1048.003 | Inspect non-standard port traffic and block unauthorized ICMP or DNS tunneling protocols at the network perimeter. |
D3-PHA | Process Hollowing Analysis | Detect | T1055.012 | Inspect unbacked executable memory regions (PAGE_EXECUTE_READWRITE) for replaced PE image headers inside legitimate host processes. |
D3-CVH | Credential Vault Hardening | Harden | T1555.003 | Enable DPAPI master key audit logging and isolate browser SQLite database files within virtualization-based security containers. |
D3-FS | File Sandboxing (Attachment Detonation) | Isolate | T1566.001 | Detonate macro-enabled documents, ISOs, and password-protected archives inside an isolated hypervisor. |
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_LOKI_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Loki"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "loki" 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 - Loki (Trojan) Execution & Triage
id: 4e6b8f88-3d6b-50de-9ecf-e0cc6963633b
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Loki 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/loki
- 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.t1566_001
- attack.t1048_003
- attack.t1555_003
- attack.t1055_012
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: mediumTier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_LOKI_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Loki 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 = "loki" 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
}Containment & Response Steps
Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.
- Assume ALL credentials stored on the machine (browsers, email, FTP, SSH, crypto wallets) have been compromised. Force immediate, enterprise-wide password resets for the user.
- Isolate the endpoint to prevent further exfiltration or the downloading of secondary payloads (LokiBot can sometimes act as a downloader).
- Identify the C2 domain/IP from network logs and block it across the enterprise; use this to hunt for other infected machines.
- Audit VPN and external portal logs for the recently stolen credentials to detect immediate attempts at lateral movement by the attackers.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not assume the network is safe just because the AV deleted the initial dropper; LokiBot harvests and exfiltrates credentials in a matter of seconds.
- Avoid relying solely on file-based scanning; memory forensics is often required to analyze the hollowed process and extract the LokiBot C2 configuration.
References & External Analysis
- Search "loki" on VirusTotal (External Analysis)
- Search "loki" on Any.Run (Sandbox Sandbox)
- Search "loki" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Loki and what threat category does it belong to?
Loki is classified as a Trojan. Documented across security telemetry, it is engineered to execute unauthorized operations, establish persistent footholds on target endpoints, and facilitate malicious campaigns targeting enterprise and individual environments.
How does Loki establish persistence and evade defensive controls?
Loki typically establishes persistence through registry run keys, scheduled tasks, or service installations, while evading signature-based antivirus solutions through code obfuscation, memory injection, or anti-analysis sandbox checks.
What are the essential incident response steps for mitigating a Loki compromise?
Security teams responding to Loki should immediately isolate affected endpoints from the network, perform memory triage to capture volatile forensic artifacts, audit registry and startup persistence mechanisms, revoke exposed user credentials, and restore systems from verified, clean backups.
What secondary payloads and staging behaviors are commonly associated with Loki?
Loki frequently operates as a loader or dropper designed to establish a foothold before downloading and executing secondary high-impact malware payloads. Depending on the threat actor's objectives, these dropped modules can range from ransomware and banking injects to modular infostealers and remote management backdoors.
How can security operations teams effectively detect and hunt for Loki across enterprise endpoints?
Defenders should hunt for Loki by deploying behavioral endpoint detection and response (EDR) rules that monitor suspicious process spawning (such as cmd.exe or powershell.exe spawned from office documents or temporary directories), anomalous outbound network connections from non-browser binaries, and unauthorized modifications to Windows Run keys and scheduled task registries.
How do I remove the Loki Trojan from Windows?
Manual removal of Loki 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 Loki a virus or a Trojan?
Loki is classified as a Trojan. Unlike traditional viruses that infect files, modern malware like Loki typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Loki infection?
Symptoms of Loki 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 Loki 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.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/loki.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.