Micronames

Overview

Executive Summary

Distribution and Technical Behavior

• Browser Hijacking: Micronames alters the browser's default search engine, homepage, and new tab settings. All search traffic is redirected through an affiliate-linked search portal controlled by the adware operators to generate illicit ad revenue.
• Traffic Interception and Injection: The software frequently installs malicious browser extensions or a local proxy server to intercept unencrypted web traffic. It overlays legitimate websites with disruptive pop-ups, pop-unders, banner ads, and sponsored in-text hyperlinks.
• Data Harvesting: It continuously tracks the user's browsing history, search queries, and clickstreams, transmitting this telemetry to remote servers to serve highly targeted advertisements.

Risk Assessment

Mitigation and Removal Strategies

• Endpoint Scanning: Utilize a reputable enterprise-grade anti-malware solution to perform a deep system scan, targeting the Micronames executables, hidden scheduled tasks, and persistent registry keys used to maintain its hold on the browser.
• Browser Remediation: Manually inspect and remove any unknown or unauthorized extensions from all installed web browsers. Perform a complete factory reset of the browsers to clear the hijacked proxy and search settings.
• Application Control: Enforce strict application whitelisting policies to prevent standard users from executing unapproved software installers that are the primary vector for this adware.

Known aliases

Threat reports may refer to this family under multiple names:

• Adware.Micronames
• PUP.Micronames
• BrowserModifier:Win32/Micronames

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:

• T1566.002: Inspect email links for known malicious domains and use link-rewriting services for time-of-click analysis.

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_MICRONAMES_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Micronames"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "micronames" ascii wide nocase
        $s2 = "adware.micronames" ascii wide nocase
        $s3 = "pup.micronames" ascii wide nocase
        $s4 = "browsermodifier:win32/micronames" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Micronames (Trojan) Execution & Triage
id: f130e064-b156-5189-b1cd-f511401b4ef7
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Micronames 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/micronames
- 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_002
- attack.t1176
- attack.t1112
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_MICRONAMES_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Micronames 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 = "micronames" 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 Micronames from retrieving secondary stage payloads.
2. Capture process memory triage to detect and terminate malicious threads injected by Micronames 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 Micronames 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 Micronames 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 Micronames 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 Micronames 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 "micronames" on VirusTotal (External Analysis)
• Search "micronames" on Any.Run (Sandbox Sandbox)
• Search "micronames" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Trojan)

Explore other documented threats in the same operational category:

• Potao
• Injeber
• Sathurbot
• Schoolgirl
• Taranis
• Admedia
• Staser
• Redirected

Machine-readable

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