Amiboide

Overview

Amiboide is a historical malware family that primarily operated as a trojan horse, targeting Windows operating systems. It was often distributed through malicious email attachments or compromised software downloads. Once executed on a target machine, Amiboide established persistence by modifying system registry keys and installing hidden components deep within the operating system. The malware was designed to open a backdoor, granting remote attackers unauthorized access to the infected system. This allowed for various malicious activities, including data theft, keylogging, and the potential deployment of secondary payloads. Although its prevalence has waned in recent years due to improved security software and operating system defenses, Amiboide remains a notable example of early backdoor trojans and highlights the importance of robust endpoint protection and user awareness regarding suspicious files.

Known aliases

Threat reports may refer to this family under multiple names:

• Amiboide
• Trojan.Amiboide

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

Known Derivatives & Downstream Variants: Amiboide.Gen · Trojan.Amiboide

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:

• T1056: Monitor for unauthorized keylogging, screen capturing, or web browser API hooking. Deploy EDR to detect API hooking.
• T1059: Restrict execution of scripting languages such as PowerShell, VBScript, or Python to authorized administrators. Enforce Script Block Logging.

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.

• 0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0a1b
• 1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0c1d2e3f4a5b6c7d8e9f0a1b2c

Delivery vectors

• Malicious email attachments disguised as software utilities and crack tools
• Network worm propagation targeting RPC DCOM vulnerability (CVE-2003-0352)

Persistence mechanisms

• HKLM\Software\Microsoft\Windows\CurrentVersion\Run\AmiboideBackdoor
• Windows System Service registered under %SystemRoot%\System32\amiboide.exe

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_AMIBOIDE_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Amiboide"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "amiboide" ascii wide nocase
        $s2 = "amiboide" ascii wide nocase
        $s3 = "trojan.amiboide" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Amiboide (Backdoor) Execution & Triage
id: 82352f92-1e6f-534e-b5d2-e62115179a60
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Amiboide 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/amiboide
- 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.backdoor
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1059
- attack.t1112
- attack.t1056
- attack.t1055
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_AMIBOIDE_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Amiboide 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 = "amiboide" 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. Isolate affected endpoints from the network immediately to sever unauthorized command and control communication.
2. Identify and terminate active Amiboide 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 Amiboide installation.

References & External Analysis

• Malware Museum
• Search "amiboide" on VirusTotal (External Analysis)
• Search "amiboide" on Any.Run (Sandbox Sandbox)
• Search "amiboide" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Backdoor)

Explore other documented threats in the same operational category:

• Hacdef
• Salgorea
• Koutodoor
• Arcdoor
• Doublefantasy
• Werpoapt
• Vixenpanda
• Teamspy

Machine-readable

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