Loki

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 the MITRE ATT&CK framework:

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.

Generated Detections (Boilerplate)

These YARA and Sigma rules are auto-generated based on the family name and aliases. They must be heavily tuned before deployment in a production environment.

YARA Rule

rule MALWARE_WIN_LOKI {
    meta:
        description = "Detects Loki (trojan)"
        author = "SystemHelpdesk Boilerplate Generator"
        date = "2026-07-06"
    strings:
        $s1 = "loki" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Sigma Rule

title: Suspicious Loki Activity
id: e64cfa3fd59e32df57003c7401f48c99
status: experimental
description: Detects generic indicators of the loki malware family.
logsource:
    category: process_creation
    product: windows
detection:
    selection:
        Image|endswith:
            - '\cmd.exe'
            - '\powershell.exe'
        CommandLine|contains:
            - "*loki*"
    condition: selection
level: medium

Containment & Response Steps

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

1. 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.
2. Isolate the endpoint to prevent further exfiltration or the downloading of secondary payloads (LokiBot can sometimes act as a downloader).
3. Identify the C2 domain/IP from network logs and block it across the enterprise; use this to hunt for other infected machines.
4. 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.

1. 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.
2. 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)

Frequently Asked Questions

Related Families (Category: trojan)

Explore other malware families in the same category:

• Redator
• Pclnt
• Faketool
• Tibs
• Bindjpg

Machine-readable

Get this profile as JSON: https://jordan123234-malware-families-explorer.static.hf.space/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.