Pikabot

Category: loader · Aliases: Pikabot, pika_bot, Win32/Pikabot, Trojan.Pikabot · Sample count (EMBER 2018): 850 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: LoaderStatus: Automated SignaturePlatform: WINDOWS, X86, X64Stage: Initial-Access, Execution, Persistence, Discovery, Command-And-ControlFirst seen: 2023Actor: TA577 ↗Industry: manufacturing, technology, financial_services, professional_servicesMotivation: Financial Extortion & Enterprise Ransomware Staging🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
Pikabot is an evasive, modular malware loader that emerged in early 2023, widely recognized by threat intelligence analysts as one of the primary successors to Qakbot following Operation Duck Hunt.

Table of Contents

Overview

Pikabot is an evasive, modular malware loader that emerged in early 2023, widely recognized by threat intelligence analysts as one of the primary successors to Qakbot following Operation Duck Hunt. Operated by sophisticated threat actors associated with initial access broker TA577, Pikabot functions as a two-stage delivery mechanism designed to establish clandestine persistence, profile enterprise network environments, and inject secondary payloads including Cobalt Strike, Black Basta, and enterprise ransomware. Pikabot features extensive anti-analysis defenses, including anti-debug checks, anti-virtual machine routines, and API hashing via custom MurmurHash variants. It verifies that system language settings do not match Eastern European or Russian locales before proceeding with payload decryption. Distribution occurs primarily through hijacked email thread-injection campaigns (malicious reply-chain phishing) delivering password-protected ZIP archives containing weaponized JavaScript, VBScript, or Microsoft Software Installer (.msi) droppers that execute via rundll32.exe. In May 2024, Pikabot infrastructure was targeted during Europol's Operation Endgame, disrupting international command nodes across Germany, the Netherlands, and Ukraine.

Known aliases

Threat reports may refer to this family under multiple names:

Threat Actor Attribution

Attribution is probabilistic, not a science. Each link below states its confidence level and the evidence behind it.

→ Explore all Threat Actor & APT Campaign Profiles

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Derived From / Upstream Ancestry: Qakbot

Known Derivatives & Downstream Variants: Pikabot V1.0 (2023) · Pikabot Modular V2 (Stripped Loader 2024)

MITRE ATT&CK Techniques

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

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

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

MITRE D3FEND™ Defensive Countermeasures

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

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-BDABinary De-obfuscation & UnpackingAnalyzeT1027Utilize memory dump scanners and entropy inspection to unpack encrypted stagers during process creation.
D3-PIADProcess Injection Analysis & DetectionDetectT1055Monitor cross-process thread creation (CreateRemoteThread) and asynchronous procedure calls (QueueUserAPC).
D3-WAFWeb Content Filtering & InspectionFilterT1071.001Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles.
D3-SDASystem Discovery AnalysisDetectT1082Alert on rapid enumerations of systeminfo, hostname, and registry hardware trees in short intervals.
D3-NTINetwork Traffic InspectionDetectT1105Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols.
D3-FSFile Sandboxing (Attachment Detonation)IsolateT1566.001Detonate macro-enabled documents, ISOs, and password-protected archives inside an isolated hypervisor.

Exploited Vulnerabilities (CVEs)

This malware family is documented weaponizing the following common vulnerabilities and exposures:

Command & Control (C2) and Network Profile

How this family talks to its operators. C2 traffic can often identify a family even when its code and configuration are hard to analyse. Ports and patterns are historical and change between campaigns, so use them as hunting leads rather than block-only rules.

ProtocolsHTTPS, HTTP
Observed ports443, 80, 2222
Identifiable from traffic aloneMedium

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

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_PIKABOT_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Pikabot"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "pikabot" ascii wide nocase
        $s2 = "pikabot" ascii wide nocase
        $s3 = "pika_bot" ascii wide nocase
        $s4 = "win32/pikabot" ascii wide nocase
        $s5 = "trojan.pikabot" 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 - Pikabot (Loader) Execution & Triage
id: 9ac6e771-055d-562d-9243-1f50a975b723
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Pikabot 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/pikabot
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-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.loader
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1566_001
- attack.t1055
- attack.t1027
- attack.t1082
- attack.t1071_001
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

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_PIKABOT_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Pikabot 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 = "pikabot" 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
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

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

  1. Isolate endpoints executing anomalous rundll32.exe processes with external network connections.
  2. Block inbound email attachments containing password-protected archive files from external senders.
  3. Deploy endpoint detection alerts for unexpected MurmurHash memory resolution in user-mode processes.
  4. Implement multi-layered perimeter firewall blocks on ports commonly utilized by Pikabot C2 (e.g. 2222).

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

  1. Never extract or execute password-protected attachments delivered via reply-chain emails without out-of-band verification.
  2. Avoid allowing unrestricted outbound network traffic from rundll32.exe and regsvr32.exe binaries.
  3. Do not disable macro security or Office Protected View controls.

References & External Analysis

Frequently Asked Questions

What is Pikabot malware?

Pikabot is an evasive modular loader and backdoor that emerged in 2023, designed to profile networks and deliver secondary ransomware and Cobalt Strike beacons.

What threat group distributes Pikabot?

Pikabot is primarily operated and distributed by initial access broker TA577 and affiliated ransomware-as-a-service staging crews.

How was Pikabot disrupted by law enforcement?

In May 2024, Europol, the FBI, and European law enforcement disrupted Pikabot command infrastructure during the landmark Operation Endgame action.

How does Pikabot spread via email?

Pikabot spreads through hijacked email reply chains, inserting itself into ongoing business conversations with password-protected ZIP files.

What anti-analysis techniques does Pikabot utilize?

Pikabot checks for virtual machine artifacts, verifies system language settings against exclusions, and dynamically resolves APIs using MurmurHash.

How do I remove the Pikabot Loader from Windows?

Manual removal of Pikabot 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 Pikabot a virus or a Loader?

Pikabot is classified as a Loader. Unlike traditional viruses that infect files, modern malware like Pikabot typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.

What are the main symptoms of a Pikabot infection?

Symptoms of Pikabot 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 Loaders

Want to prevent Pikabot and similar threats from compromising your organization? Read our comprehensive defensive guide: Think You've Been Hacked? What To Do First.

📣 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.

Need help with an active incident? Published by the SystemHelpdesk team.

Machine-readable

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