Gemius

Overview

Executive Summary

Infection Vector and Technical Capabilities

• Persistent Cross-Site Tracking: Gemius utilizes sophisticated tracking techniques (including fingerprinting and persistent LSOs) to track users across multiple unaffiliated domains, building a comprehensive profile of their browsing habits.
• Data Exfiltration: The scripts silently collect significant amounts of telemetry, including IP addresses, browser configurations, screen resolutions, and detailed clickstream data, exfiltrating this to remote analytic servers.
• Adware Bundling: In some instances, explicit "survey" or "measurement panel" software from Gemius or its affiliates is bundled with other freeware applications, operating persistently in the background to monitor system and network activity.

Threat Assessment

Incident Response and Remediation

• Privacy Policy Enforcement: The presence of Gemius tracking highlights the need for robust endpoint privacy controls. Deploy enterprise-wide browser policies (via Group Policy) to enforce Strict Tracking Prevention and block third-party cookies.
• Network Level Blocking: To completely eliminate the telemetry, network administrators should add known Gemius tracking domains to DNS sinkholes or firewall blocklists.
• Targeted Uninstallation: If a local Gemius software component (like a "measurement panel") was installed via a software bundle, it should be removed using standard enterprise software management tools or anti-malware scanners configured to detect PUPs.

Known aliases

Threat reports may refer to this family under multiple names:

• Riskware.Gemius
• Adware.Gemius
• PUP.Tracking.Gemius

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:

• T1059.001: Restrict execution of PowerShell. Enforce PowerShell Constrained Language Mode and Script Block Logging.
• T1071.001: Implement web filtering and SSL/TLS inspection to detect malicious command and control (C2) traffic hiding in HTTP/HTTPS.
• 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_GEMIUS_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Gemius"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "gemius" ascii wide nocase
        $s2 = "riskware.gemius" ascii wide nocase
        $s3 = "adware.gemius" ascii wide nocase
        $s4 = "pup.tracking.gemius" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Gemius (Advanced Threat) Execution & Triage
id: a3e06af0-04a2-59af-81f0-cf0c99f547d0
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Gemius malware family. Detects proxy execution, reflective DLL loading,
  and remote command injection associated with modular enterprise backdoors.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/gemius
- https://malware-families-catalog.systemhelpdesk.com/defensive/backdoor-rat-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.advanced-threat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1539
- attack.t1185
- attack.t1059_001
- attack.t1055
- attack.t1071_001
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \powershell.exe
    - \cmd.exe
    - \rundll32.exe
    - \regsvr32.exe
    CommandLine|contains:
    - DownloadString
    - IEX(
    - '/s /n /u /i:'
    - sc create
    - start-process
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

rule MALWARE_WIN_GEMIUS_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Gemius 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 = "gemius" 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. Enforce forensic network isolation on all suspected endpoints while maintaining an out-of-band telemetry conduit to capture live Gemius adversary activity.
2. Perform full memory dumps across identified staging nodes to extract memory-only implants, kernel rootkit hooks, and decrypted Gemius C2 infrastructure IP/domain lists.
3. Review Active Directory domain controller authentication logs for anomalous Kerberos ticket requests (Pass-the-Ticket, Golden Ticket) and unauthorized DCSync operations associated with Gemius.
4. Block all confirmed C2 domains, dynamic DNS endpoints, and proxy IP addresses across perimeter firewalls, proxies, and DNS security gateways.
5. Conduct an enterprise-wide sweep across surrounding subnets for secondary webshells, WMI event subscriptions, or remote execution tooling left behind by Gemius operators.

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 Gemius 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 Gemius 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 "gemius" on VirusTotal (External Analysis)
• Search "gemius" on Any.Run (Sandbox Sandbox)
• Search "gemius" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Advanced Threat)

Explore other documented threats in the same operational category:

• Rubar
• Grenam
• Torntv
• Oneclick
• Mobogenie
• Fakesysdef
• Russoturisto
• Primecasino

Machine-readable

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