Brontok

Overview

Brontok (widely recognized across cybersecurity history as Rontokbr, Worm:Win32/Brontok, and W32.Rontokbro@mm) is a landmark, highly disruptive mass-mailing computer worm first surfacing in 2005 from Indonesian authors. Brontok propagates aggressively by scanning local drives for email addresses, utilizing an internal SMTP engine to blast infected messages with deceptive attachment names, and replicating to removable USB drives and shared network folders. Once resident, Brontok disables Windows Registry Editor (regedit), Task Manager, and Folder Options, and actively terminates system utility windows containing strings like 'regedit' or 'cmd', triggering immediate system reboots if users attempt diagnostics. The worm creates multiple startup entries across Windows Run keys, displays socio-political manifestos in browser windows, and launches ping-flood distributed denial-of-service attacks against designated websites.

Known aliases

Threat reports may refer to this family under multiple names:

• Worm:Win32/Brontok
• Worm:Win32/Brontok@mm
• W32.Rontokbro@mm
• Email-Worm.Win32.Brontok
• Rontokbr

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: Historic Win32 Mass-Mailing Worm Architectures

Known Derivatives & Downstream Variants: Brontok.A · Brontok.B@Mm · Rontokbro.Gen

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:

• T1036.005: Monitor for executable files running from unusual paths or with deceptive names. Use EDR to detect process masquerading.
• T1566.001: Scan email attachments for malicious macros, scripts, or suspicious archive files.

MITRE D3FEND™ Defensive Countermeasures

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

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.

• 0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e
• 1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f

Delivery vectors

• photo.zip.exe
• document_card.scr

Persistence mechanisms

• %AppData%\locmgr.exe
• %UserProfile%\Start Menu\Programs\Startup\Empty.pif

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_BRONTOK_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Brontok"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "brontok" ascii wide nocase
        $s2 = "worm:win32/brontok" ascii wide nocase
        $s3 = "worm:win32/brontok@mm" ascii wide nocase
        $s4 = "w32.rontokbro@mm" ascii wide nocase
        $s5 = "email-worm.win32.brontok" ascii wide nocase
        $s6 = "rontokbr" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Brontok (Worm) Execution & Triage
id: a0756648-151b-5f7f-a234-677335b2e37f
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Brontok 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/brontok
- 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.t1566_001
- attack.t1091
- attack.t1562_001
- attack.t1547_001
- attack.t1498
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_BRONTOK_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Brontok 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 = "brontok" 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. Quarantine the endpoint immediately to halt the outbound mass-mailing campaign and prevent the worm from traversing mapped network shares.
2. Enforce egress firewall rules blocking outbound TCP port 25 from all endpoints, forcing all email traffic through authorized corporate mail relays.
3. Disable AutoRun/AutoPlay enterprise-wide via Group Policy to halt Brontok's propagation via USB drives.
4. Utilize offline registry editing tools or EDR to reverse the registry modifications that disabled `regedit.exe` and `cmd.exe`.

What to Avoid

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

1. Do not insert a clean USB drive into the infected machine to transfer tools; Brontok will immediately infect the drive.
2. Avoid assuming the threat is contained just by stopping the spam; the worm actively disables AV, leaving the machine vulnerable.

References & External Analysis

• Microsoft Defender Security Intelligence - Worm:Win32/Brontok@mm
• Kaspersky Securelist - Email-Worm.Win32.Brontok Analysis
• Search "brontok" on VirusTotal (External Analysis)
• Search "brontok" on Any.Run (Sandbox Sandbox)
• Search "brontok" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Worm)

Explore other documented threats in the same operational category:

• Benjamin
• Mogoogwi
• Vbs_Worm_Generator
• Beebone
• Conficker
• Blasterx
• Netsky
• Vobfus

Machine-readable

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