Kolabc

Category: worm · Aliases: Kolabc, Worm:Win32/Kolabc, Trojan.Kolabc, Worm.Win32.Kolab, Win32/Kolabc, Kolab Worm, Worm:Win32/Kolab · Sample count (EMBER 2018): 143 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: WormStatus: Automated SignaturePlatform: WINDOWS_PEStage: Defense Evasion, ImpactFirst seen: 2009Actor: Unknown / CybercriminalIndustry: Healthcare, Critical Infrastructure, EnterpriseMotivation: Botnet Operations🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 10, Windows 7, Windows XP
Executive Summary
Worm:Win32/Kolabc (commonly identified across threat telemetry as Trojan.Kolabc, Worm.Win32.Kolab, or Win32/Kolabc) is a resilient, self-propagating Windows network worm and botnet agent.

Table of Contents

Overview

Worm:Win32/Kolabc (commonly identified across threat telemetry as Trojan.Kolabc, Worm.Win32.Kolab, or Win32/Kolabc) is a resilient, self-propagating Windows network worm and botnet agent. Operating as a modular malware platform, Kolabc propagates across local network subnets by searching for unprotected SMB shares and infecting removable storage devices (USB thumb drives) via crafted autorun.inf files and weaponized LNK shortcuts. Once installed on a victim workstation, Kolabc injects malicious threads into trusted system processes such as svchost.exe or explorer.exe, establishes persistence via the Windows Run registry keys, and connects to remote IRC or HTTP command-and-control infrastructure. Controlled endpoints receive commands to download secondary malware payloads—including banking trojans and ransomware—relay spam emails, or launch coordinated distributed denial-of-service (DDoS) flood attacks.

Known aliases

Threat reports may refer to this family under multiple names:

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: Win32 Ircbot / Worm Modular Lineage

Known Derivatives & Downstream Variants: Worm:Win32/Kolabc.A · Worm:Win32/Kolabc.B · Trojan.Kolabc.Gen

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-MFAMulti-factor AuthenticationHardenT1056.001Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless.
D3-NTINetwork Traffic InspectionDetectT1105Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols.
D3-SCMWindows Service Creation MonitoringDetectT1543.003Verify service binary image signatures and restrict standard users from creating or modifying service definitions.

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_KOLABC_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Kolabc"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "kolabc" ascii wide nocase
        $s2 = "kolabc" ascii wide nocase
        $s3 = "worm:win32/kolabc" ascii wide nocase
        $s4 = "trojan.kolabc" ascii wide nocase
        $s5 = "worm.win32.kolab" ascii wide nocase
        $s6 = "win32/kolabc" ascii wide nocase
        $s7 = "kolab worm" ascii wide nocase
        $s8 = "worm:win32/kolab" 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 - Kolabc (Worm) Execution & Triage
id: 7541542f-c22b-52d1-916d-a4cfef806d07
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Kolabc 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/kolabc
- 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.worm
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1091
- attack.t1021_002
- attack.t1055
- attack.t1071_001
- attack.t1489
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_KOLABC_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Kolabc 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 = "kolabc" 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. Instantly isolate the endpoint from the network to sever the attacker's interactive, remote-control session.
  2. Capture a full forensic memory image of the machine to extract the decrypted Kolabc payload and its C2 configuration.
  3. Audit the Windows Task Scheduler, Registry Run keys, and Windows Services to identify and remove the Kolabc persistence mechanisms.
  4. Assume total endpoint compromise; perform a clean OS rebuild and force global password resets for all accounts that accessed the machine.

What to Avoid

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

  1. Do not leave the machine connected to the network during triage; the attacker has live access and will likely destroy evidence or move laterally.
  2. Avoid relying solely on static file deletion, as the injected processes will likely just recreate the dropped binaries.

References & External Analysis

Frequently Asked Questions

What is Kolabc malware?

Kolabc is a network worm and botnet client that spreads via USB drives and network shares, allowing attackers to execute commands, launch DDoS attacks, and download secondary payloads.

How does Kolabc propagate across systems?

Kolabc infects removable flash drives with autorun.inf scripts and weaponized shortcuts, and scans local subnets for open or poorly secured SMB network shares.

What malicious tasks does a Kolabc botnet perform?

Compromised systems participate in distributed denial-of-service (DDoS) attacks, relay massive spam email volumes, and download auxiliary banking Trojans or ransomware.

How does Kolabc evade security monitoring?

Kolabc injects its payload code into legitimate Windows processes like svchost.exe and explorer.exe, masking its network traffic within standard operational activities.

How do organizations remediate Kolabc infections?

Organizations should disable USB autorun, enforce network segmentation on SMB ports 445/139, run endpoint anti-malware scans, and rotate local administrator credentials.

How do I remove the Kolabc Worm from Windows?

Manual removal of Kolabc 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 Kolabc a virus or a Worm?

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

What are the main symptoms of a Kolabc infection?

Symptoms of Kolabc 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 Worms

Want to prevent Kolabc and similar threats from compromising your organization? Read our comprehensive defensive guide: Worm & Virus Protection.

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