Look2Me

Overview

Executive Summary

Infection Vector and Technical Capabilities

• Winlogon Injection (DLL Hooking): Its defining characteristic is injecting its malicious DLL directly into `winlogon.exe` (a critical Windows subsystem process). This ensures the adware is loaded immediately upon user login, before most security software can initialize.
• Aggressive Self-Defense: Look2Me actively monitors the registry and file system. If a user or antivirus attempts to delete its files or registry keys (often located in `HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify`), the injected process instantly recreates them.
• Browser Hijacking and Pop-ups: Once embedded, it constantly spawns hidden Internet Explorer instances, generates intrusive pop-up ads (often for fake antispyware), and redirects search engine traffic to affiliate-monetized domains.

Threat Assessment

Incident Response and Remediation

• Safe Mode or Offline Removal: Due to its injection into `winlogon.exe`, standard removal attempts while Windows is running normally are almost always futile. Removal typically requires booting into Safe Mode or using an offline, bootable antivirus rescue disk.
• Specialized Removal Tools: Standard AV often struggles with Look2Me's persistence. Specialized anti-rootkit utilities (like the historically used 'L2Mfix' or modern equivalents) are required to safely unhook the DLL from `winlogon.exe` without crashing the operating system.
• System Re-imaging (Recommended): Given the depth of the OS hooking and the age of the malware (suggesting a severely unpatched system), a complete bare-metal wipe and OS re-installation is the most secure and reliable remediation method.

Known aliases

Threat reports may refer to this family under multiple names:

• Adware.Look2Me
• Spyware.L2M
• Win32/Look2Me.Rootkit

MITRE ATT&CK Techniques

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

Tactical Mitigations

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

• T1185: Enforce strong MFA and use browser isolation or hardened browsers for sensitive financial or administrative portals to defeat session hijacking.

MITRE D3FEND™ Defensive Countermeasures

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

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:

rule MALWARE_WIN_LOOK2ME_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Look2Me"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "look2me" ascii wide nocase
        $s2 = "adware.look2me" ascii wide nocase
        $s3 = "spyware.l2m" ascii wide nocase
        $s4 = "win32/look2me.rootkit" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Look2me (Trojan) Execution & Triage
id: 3474a763-9cd7-599f-8a7b-31c5f9e3a150
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Look2me 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/look2me
- 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.t1547_004
- attack.t1055_001
- attack.t1562_001
- attack.t1185
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

rule MALWARE_WIN_LOOK2ME_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Look2Me 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 = "look2me" 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.

1. Sever network connectivity for the flagged endpoint to terminate persistent command-and-control (C2) communication channels and stop Look2Me from retrieving secondary stage payloads.
2. Capture process memory triage to detect and terminate malicious threads injected by Look2Me into legitimate system processes such as explorer.exe or svchost.exe.
3. Audit Windows Registry Run keys (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) and Task Scheduler entries to locate and purge Look2Me persistence hooks.
4. Deploy updated enterprise EDR detection signatures and conduct an out-of-band endpoint scan to isolate dropped binaries and staged payloads.
5. Rotate all credentials, domain user passwords, and session cookies active on the system during the Look2Me execution timeframe.

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 incident is resolved simply because an antivirus tool removed the initial Look2Me dropper; always verify that secondary payloads and persistence hooks have been eradicated.
2. Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Look2Me until memory triage is complete.
3. Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.

References & External Analysis

• Search "look2me" on VirusTotal (External Analysis)
• Search "look2me" on Any.Run (Sandbox Sandbox)
• Search "look2me" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Trojan)

Explore other documented threats in the same operational category:

• Aauto
• Hooker
• Mmorpg
• Kranet
• Rasoon
• Cashfiesta
• Keyboy
• Bisonal

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/look2me.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.