New 'Fickle Stealer' Malware Written in Rust Employs UAC Bypass to Exfiltrate Sensitive Data

Rust-Based 'Fickle Stealer' Malware Bypasses UAC to Steal Crypto Wallets and Browser Data

HIGH
June 21, 2026
5m read
MalwareData BreachPhishing

Related Entities

Products & Tech

PowerShell WindowsRustAnyDeskDiscordFileZillaSignalSkypeSteam

Other

Fickle StealerTelegram

Full Report

Executive Summary

Security researchers have identified a new, multi-faceted information stealer named Fickle Stealer. This malware is notable for being written in the Rust programming language, a choice that aids in evasion due to its complex assembly output. Fickle Stealer is distributed through various means, including VBA droppers and link-based downloads. A key component of its attack chain is a PowerShell script used to bypass Windows User Account Control (UAC), allowing it to execute its main payload with elevated privileges. The malware is designed to steal a vast range of data, from cryptocurrency wallets and browser credentials to session data from popular applications. The exfiltrated data is sent to a Telegram bot, demonstrating a trend of threat actors abusing legitimate cloud services for C2 operations.


Threat Overview

Fickle Stealer represents a growing class of sophisticated info-stealers that are flexible and difficult to detect. The infection begins when a user interacts with a malicious dropper, which can be a macro-enabled document or a link to a malicious executable.

Upon execution, the malware's first major action is to run a PowerShell script (e.g., bypass.ps1) to perform a UAC bypass using T1548.002 - Bypass User Account Control. This allows the main stealer payload to run without triggering a security prompt for the user. The stealer component, which is protected by a packer, performs anti-analysis checks to ensure it's not in a sandbox. It then proceeds to harvest data from a wide array of targets on the victim's machine.

Technical Analysis

Fickle Stealer's attack chain is modular and effective:

  • Distribution: Uses multiple vectors including VBA droppers, VBA downloaders, and direct executable downloads.
  • Defense Evasion:
    • UAC Bypass: Leverages a PowerShell script to elevate privileges without user interaction.
    • Anti-Analysis: Checks for virtual machines, sandboxes, and debuggers before executing its main logic.
    • Written in Rust: The choice of Rust makes manual reverse engineering more challenging compared to malware written in C/C++.
  • Data Collection: The stealer payload is comprehensive, targeting:
    • Cryptocurrency Wallets: Scans for wallets such as AtomicWallet, Exodus, Electrum, Bitcoin, Ethereum, and ZCash (T1552.001 - Credentials In Files).
    • Web Browsers: Steals cookies, passwords, and autofill data from Chromium-based (Chrome, Edge) and Gecko-based (Firefox) browsers (T1555.003 - Credentials from Web Browsers).
    • Applications: Targets session and credential data from AnyDesk, Discord, FileZilla, Signal, Skype, Steam, and Telegram.
    • File Grabbing: Can search for and exfiltrate specific file types (.txt, .pdf, .docx) based on a configuration received from its C2 server.
  • Command and Control & Exfiltration: Uses the Telegram Bot API for both C2 and data exfiltration (T1102.001 - Command and Control: Web Service). This allows it to blend in with legitimate network traffic, making it harder to block.

Impact Assessment

A successful infection by Fickle Stealer can lead to severe consequences for both individuals and organizations. The theft of credentials can result in:

  • Financial Loss: Direct theft of funds from cryptocurrency wallets.
  • Account Takeover: Compromise of email, social media, and other online accounts, leading to identity theft and further fraud.
  • Corporate Espionage: Theft of sensitive documents and communication data from applications like Signal and Telegram.
  • Further Compromise: Stolen credentials (e.g., from FileZilla or AnyDesk) can be used to gain deeper access into corporate networks, leading to a more significant breach.

The use of Telegram for exfiltration means that even if the initial infection is contained, the stolen data is already in the hands of the attacker.

IOCs — Directly from Articles

No specific Indicators of Compromise (IOCs) such as IP addresses, domains, or file hashes were provided in the source articles.

Cyber Observables — Hunting Hints

Security teams can hunt for Fickle Stealer using the following clues:

  • PowerShell Execution: Monitor for PowerShell processes executing scripts with names like bypass.ps1 or u.ps1. Look for PowerShell commands that attempt to modify registry keys related to UAC or use reflective injection techniques.
  • Network Traffic: Look for outbound HTTPS connections to api.telegram.org. While this is a legitimate domain, traffic originating from unexpected processes or user workstations could be malicious.
  • File System Activity: Monitor for rapid file access to directories associated with cryptocurrency wallets (e.g., %APPDATA%\Exodus) or browser profiles.
  • Process Behavior: Look for processes that enumerate a large number of files and directories, then make a network connection, which could be indicative of the data staging and exfiltration process.

Detection & Response

  1. PowerShell Logging: Enable advanced PowerShell logging (Script Block Logging and Module Logging) to capture the content of executed scripts. This will reveal UAC bypass attempts and other malicious activities. This is a form of D3FEND's Process Analysis.
  2. EDR/XDR: Use an EDR solution to detect suspicious process chains, such as a Microsoft Office application spawning powershell.exe. The EDR should also be able to detect fileless attacks and UAC bypass techniques.
  3. Network Egress Filtering: Block or alert on all outbound connections to the Telegram API (api.telegram.org) from corporate assets, unless there is a legitimate business need. This is a direct application of D3FEND's Outbound Traffic Filtering.
  4. User and Entity Behavior Analytics (UEBA): UEBA platforms can help detect anomalous file access patterns or network connections that deviate from a user's normal baseline behavior.

Mitigation

  • Restrict PowerShell: If not required for administrative tasks, use AppLocker or other application control solutions to restrict or disable PowerShell execution for standard users (M1038 - Execution Prevention).
  • UAC Configuration: Set User Account Control to its highest setting ("Always notify"). While bypasses exist, this can prevent simpler techniques.
  • Email Security: Block macro-enabled documents from external sources at the email gateway.
  • Credential Protection: Encourage the use of hardware wallets for storing significant amounts of cryptocurrency. Use password managers with MFA to protect online accounts (M1032 - Multi-factor Authentication).
  • User Training: Educate users about the dangers of enabling macros in documents from untrusted sources (M1017 - User Training).

Timeline of Events

1
June 21, 2026
This article was published

MITRE ATT&CK Mitigations

Use application control solutions like AppLocker to restrict the use of PowerShell for non-administrative users.

Mapped D3FEND Techniques:

Deploy an EDR that can detect and block malicious PowerShell execution and UAC bypass techniques based on behavior.

Mapped D3FEND Techniques:

Block outbound connections to known malicious services or services commonly abused for C2, such as the Telegram API, from corporate endpoints.

Mapped D3FEND Techniques:

Educate users on the risks of enabling macros in documents and downloading files from untrusted sources.

D3FEND Defensive Countermeasures

To specifically counter Fickle Stealer, security teams must implement robust process analysis via an EDR solution with advanced PowerShell logging. Enable PowerShell Script Block Logging (Event ID 4104) to capture the full content of scripts, which will expose the UAC bypass techniques used by bypass.ps1. Create detection rules that alert on suspicious process chains, particularly a Microsoft Office application spawning powershell.exe, which in turn attempts to modify the registry or perform reflective loading. Furthermore, monitor for processes that rapidly access sensitive user directories associated with browsers (%LOCALAPPDATA%\Google\Chrome\User Data) and crypto wallets (%APPDATA%\Exodus), followed by an outbound network connection. This sequence is a strong indicator of an info-stealer's collection and exfiltration behavior.

Given Fickle Stealer's reliance on the Telegram API for data exfiltration, network-level controls are highly effective. Implement a strict egress filtering policy that blocks all outbound connections from workstations to api.telegram.org. This can be done at the perimeter firewall or via a web proxy. For organizations that have a legitimate business use for Telegram, rules should be scoped as narrowly as possible, perhaps allowing access only from specific marketing machines and denying it from all others, especially servers and developer workstations. This simple but effective rule cuts off the malware's ability to send stolen data back to the attacker, significantly mitigating the impact of an infection.

Harden endpoints by restricting the attack surface available to Fickle Stealer. Use application control policies, such as Windows AppLocker or Defender Application Control, to prevent PowerShell from being executed by standard users. Set PowerShell's execution mode to Restricted or AllSigned for users who do not require scripting capabilities. Additionally, configure Microsoft Office applications via Group Policy to block all macros from the internet. This prevents the initial infection vector if the malware is delivered via a malicious document. Finally, ensure Windows UAC is configured to the highest level ('Always notify') to provide an additional layer of defense against privilege escalation attempts, even though advanced bypasses exist.

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

Fickle StealerInfoStealerRustMalwarePowerShellUAC BypassCryptocurrency

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.