Sugar

Category: ransomware · Aliases: Ransom:Win32/Sugar, Ransom.Encoded01, Win32/Sugar, Encoded01 · Sample count (EMBER 2018): 80 · Enrichment: curated_sourced · Updated: 2026-10-15
Category: RansomwareStatus: Automated SignaturePlatform: WINDOWS_PEStage: Defense Evasion, ImpactFirst seen: 2021Actor: Unknown / CybercriminalIndustry: Healthcare, Critical Infrastructure, EnterpriseMotivation: Financial Extortion🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 8.1
Executive Summary
Sugar (tracked across cybersecurity threat intelligence feeds under aliases including Sugar Ransomware, Encoded01, and Ransom.Encoded01) is a Delphi-based Ransomware-as-a-Service (RaaS) operation first identified by Walmart security researchers in November 2021.

Table of Contents

Overview

Sugar (tracked across cybersecurity threat intelligence feeds under aliases including Sugar Ransomware, Encoded01, and Ransom.Encoded01) is a Delphi-based Ransomware-as-a-Service (RaaS) operation first identified by Walmart security researchers in November 2021. Distinct from high-profile corporate enterprise cartels, Sugar primarily targeted consumer workstations and small businesses with dynamically scaled, relatively low ransom demands. Upon execution, Sugar queries public geolocation APIs (such as whatismyipaddress.com and ip2location.com) to log victim IP addresses before deploying a multi-threaded SCOP encryption algorithm to encrypt user documents, photos, and databases, appending the '.encoded01' extension. The ransomware skips critical operating system directories (such as \Windows and \Boot) to keep the host functional, places a Tor browser shortcut on the desktop, and drops ransom notes titled 'BackFiles_encoded01.txt' directing victims to dark web payment portals on sugarpanel.space that mirror the visual aesthetics of REvil and Cl0p.

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: Commercial Delphi Ransomware Strains

Known Derivatives & Downstream Variants: Sugar.Encoded01 · Sugar.Raas

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-NDFNetwork Data FilteringIsolateT1048Inspect non-standard port traffic and block unauthorized ICMP or DNS tunneling protocols at the network perimeter.
D3-PBAProcess Spawn AnalysisDetectT1059.003Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe.
D3-FAEDFile Alteration Early DetectionDetectT1486Deploy canary files and monitor mass rename/encryption I/O spikes to terminate ransomware threads immediately.
D3-SPPService Protection PoliciesHardenT1489Configure strict DACLs on Windows Service Control Manager to prevent unauthorized termination of antivirus and backup services.
D3-VSSVolume Shadow & Snapshot HardeningHardenT1490Block execution of vssadmin.exe and wmic shadowcopy delete; maintain air-gapped immutable backup repositories.

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_SUGAR_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Sugar"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "sugar" ascii wide nocase
        $s2 = "ransom:win32/sugar" ascii wide nocase
        $s3 = "ransom.encoded01" ascii wide nocase
        $s4 = "win32/sugar" ascii wide nocase
        $s5 = "encoded01" 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 - Sugar (Ransomware) Execution & Triage
id: 5496a1cb-47ca-545f-80bf-c24c5b70def0
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Sugar malware family. Detects volume shadow copy deletion, boot status
  tampering, and recovery inhibition characteristic of modern ransomware operations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/sugar
- 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.ransomware
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1486
- attack.t1059_003
- attack.t1547_001
- attack.t1082
- attack.t1016
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \vssadmin.exe
    - \wmic.exe
    - \wbadmin.exe
    - \bcdedit.exe
    CommandLine|contains:
    - delete shadows
    - shadowcopy delete
    - resize shadowstorage
    - recoveryenabled no
    - ignoreallfailures
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: critical

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_SUGAR_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Sugar 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 = "sugar" 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. Immediately sever the infected endpoint and any mapped network segments from the corporate network to halt the spread of the encryption process.
  2. Do NOT reboot the machine immediately; capture a forensic RAM image to preserve memory, which may contain decryption keys or critical forensic data.
  3. Identify the initial access vector (e.g., compromised VPN credentials, phishing) and the lateral movement path to ensure the attacker is fully eradicated.
  4. Initiate disaster recovery protocols using offline, immutable backups; do not pay the ransom unless explicitly advised by law enforcement and legal counsel.

What to Avoid

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

  1. Do not connect any external drives or network shares to the infected machine, as the ransomware will immediately attempt to encrypt them.
  2. Avoid executing any files or attempting manual recovery without a forensic image; altering the disk state can permanently corrupt the encrypted data.

References & External Analysis

Frequently Asked Questions

What is Sugar Ransomware (Encoded01)?

Sugar is a Delphi-based ransomware family that encrypts consumer and small business files with the .encoded01 extension.

Which encryption algorithm is utilized by Sugar?

Sugar uses the SCOP encryption algorithm paired with public/private keys to lock victim data.

How does Sugar determine the victim's ransom amount?

The ransom demand is dynamically calculated based on the total quantity and volume of files encrypted.

What ransom note is dropped by Sugar Ransomware?

It drops 'BackFiles_encoded01.txt' containing instructions and links to Tor negotiation portals.

How can victims recover from a Sugar infection?

Isolate the computer, terminate the ransomware process, clean malware binaries, and restore files from offline backups.

How do I remove the Sugar Ransomware from Windows?

Manual removal of Sugar 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 Sugar a virus or a Ransomware?

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

What are the main symptoms of a Sugar infection?

Symptoms of Sugar 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 Ransomwares

Want to prevent Sugar and similar threats from compromising your organization? Read our comprehensive defensive guide: Ransomware Containment & Incident Response.

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