Brutus

Category: tool · Aliases: Brutus Password Cracker, Brutus AET · Sample count (EMBER 2018): 0 · Enrichment: curated_sourced · Updated: 2026-08-01
Category: ToolSeverity: MEDIUMStatus: Automated SignaturePlatform: WINDOWS_PEStage: Initial Access, ExecutionFirst seen: 2000Actor: Unknown / CybercriminalIndustry: Global / Opportunistic, Telecommunications, Information TechnologyMotivation: Credential Access🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 7
Executive Summary
Brutus is a widely recognized and versatile password-cracking utility that has been utilized by both security professionals and malicious actors for over two decades.

Table of Contents

Overview

Brutus is a widely recognized and versatile password-cracking utility that has been utilized by both security professionals and malicious actors for over two decades. Operating primarily on Windows systems, Brutus is categorized as a remote password cracker that specializes in brute-force and dictionary attacks against various network services. It natively supports protocols such as HTTP (Basic Authentication), FTP, POP3, Telnet, and SMB. What sets Brutus apart is its customizable nature, allowing users to define specific authentication sequences and import extensive wordlists. While its age means it lacks support for modern cryptographic standards and secured protocols like HTTPS, it remains an effective tool against legacy systems and misconfigured servers. Its existence underscores the critical need for strong password policies and the implementation of multi-factor authentication (MFA) across all services.

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: Legacy_Network_Authentication_Bruteforcers

Known Derivatives & Downstream Variants: Brutus_Aet2 · Brutus_Fast

MITRE ATT&CK Techniques

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

TechniqueNameTacticOfficial Spec
T1110Brute ForceCredential AccessATT&CK ↗
T1078Valid AccountsDefense EvasionATT&CK ↗
→ Explore the complete 226-Technique ATT&CK Threat Matrix

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-MFAMulti-factor AuthenticationHardenT1078Enforce mandatory phishing-resistant FIDO2 multi-factor authentication across all external access portals.
D3-ALAccount Lockout PolicyHardenT1110Enforce progressive rate limiting and account lockout policies to prevent credential brute-force attacks.

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_BRUTUS_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Brutus"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "brutus" ascii wide nocase
        $s2 = "brutus password cracker" ascii wide nocase
        $s3 = "brutus aet" 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 - Brutus (Tool) Execution & Triage
id: ad5301c7-b60f-529d-a6b3-f77b7cd75b29
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Brutus 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/brutus
- 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.tool
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1110
- attack.t1078
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_BRUTUS_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Brutus 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 = "brutus" 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 affected endpoints from the network immediately to sever unauthorized command and control communication.
  2. Identify and terminate active Brutus binaries and associated parent-child process chains.
  3. Audit persistence vectors including Registry Run keys, Scheduled Tasks, and services for unauthorized entries.
  4. Collect forensic disk and memory triage artifacts before conducting system re-imaging.

What to Avoid

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

  1. Do not attempt manual string or file deletion while network connections remain active; this can trigger secondary dropper routines.
  2. Avoid restoring from backups without verifying that the backup snapshot predates initial Brutus installation.

References & External Analysis

Frequently Asked Questions

What is Brutus in the context of cybersecurity?

Brutus is a legacy remote password-cracking tool used to perform brute-force and dictionary attacks.

What protocols does Brutus support?

It supports several older protocols, including FTP, POP3, Telnet, and basic HTTP authentication.

Is Brutus still effective today?

While largely ineffective against modern, secure systems, it can still compromise legacy or misconfigured services.

Who uses the Brutus tool?

It has been used historically by both penetration testers for security auditing and attackers for malicious access.

How can systems defend against tools like Brutus?

Defenses include implementing account lockout policies, using strong passwords, and enabling Multi-Factor Authentication (MFA).

How do I remove Brutus from Windows?

Manual removal of Brutus 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 Brutus a virus or a Tool?

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

What are the main symptoms of a Brutus infection?

Symptoms of Brutus 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 Tools

Want to prevent Brutus 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 Threat Intelligence Team.

Machine-readable

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