ChaosBot Rust Malware Uses Discord API for Covert Command and Control

ChaosBot Rust Malware Uses Discord API for Covert Command and Control

Threat Group – Unknown operator using the moniker chaos_00019
Threat Type – Rust based backdoor and remote access trojan
Exploited Vulnerabilities – Valid accounts T1078, phishing T1566, DLL sideloading T1574.001, ETW suppression T1562.001, WMI lateral movement T1047
Malware Used – ChaosBot and Fast Reverse Proxy client
Threat Score – 8.0 🔴 High
Last Threat Observation – 14 October 2025


Overview

ChaosBot is a novel Rust based backdoor that combines stealthy execution with redundant command and control. It was first identified by a threat response team during an investigation in a financial services environment in late September 2025. The operators abuse valid VPN and directory credentials to gain initial access and then move laterally with WMI. They also run targeted phishing that delivers shortcut files which bootstrap the payload through PowerShell while a banking themed decoy document distracts the user.

ChaosBot executes via DLL sideloading through a legitimate Microsoft Edge component placed in a public user directory. It blinds endpoint telemetry by patching Event Tracing for Windows at runtime. The backdoor maintains control through two channels. It uses Discord’s HTTPS API for low volume tasking and small exfiltration. It also deploys Fast Reverse Proxy for high throughput persistent access over a dedicated egress port to cloud infrastructure. This dual channel design increases resilience and enables quieter hands on keyboard operations.


Validation of Threat Identity and Scope

  • The threat family name is derived from the primary operator profile chaos_00019. A secondary handle lovebb0024 has been observed.
  • Initial victim evidence originates from a financial services customer with lure content themed for Vietnamese users. Targeting is not considered exclusive to that locale.
  • Confirmed TTPs include valid account abuse for Cisco VPN and Active Directory, WMI based lateral execution, DLL sideloading through an Edge helper binary, ETW patching to suppress telemetry, and web service C2 through Discord.

Required Immediate Actions

These actions are prioritised to interrupt active operations and prevent recurrence.

Priority Remediation Table

PriorityActionObjectiveNotes for Validation
1Enforce phishing resistant MFA on all VPN and privileged directory logonsBreak valid account abuse T1078Verify no exclusions and disable legacy authentication paths
2Block egress to 18.162.110.113 and alert on TCP 7000Disrupt FRP tunnel C2 T1090.003Add specific detections for long lived 7000 sessions from workstations
3Sweep endpoints for public folder implantsIdentify high fidelity host IOCsSearch for msedge_elf.dll and identity_helper.exe in Public\Libraries and node.exe and node.ini in Public\Music
4Restrict Discord to sanctioned hosts or block API usage from non browser processesReduce web service C2 T1102.002Profile normal business use and alert on headless API calls
5Disable sideloading paths through application controlContain execution and persistenceDeny Edge helper execution from user writable paths using WDAC or AppLocker
6Patch Cisco ASA and FTD to current releases and harden VPN portalsReduce infrastructure exposureEven if credentials were abused in this incident, address contemporaneous critical flaws to lower parallel risk

Attack Vectors

Initial Access and Lateral Movement

Valid accounts T1078
The operator used compromised Cisco VPN credentials and an over privileged Active Directory service account to enter and propagate. The use of a broadly permissioned service identity constitutes a direct failure of least privilege and enables very rapid fan out.

Phishing T1566
A shortcut attachment triggers obfuscated PowerShell to download and launch the backdoor while displaying a banking themed decoy PDF to mask execution. This provides an alternative path when credential access fails.

WMI lateral execution T1047
After initial entry the operator leverages WMI to remotely spawn command shells and PowerShell on multiple hosts. This reduces noise compared to interactive sessions and accelerates deployment. Analysts should hunt for WmiPrvSE.exe spawning cmd.exe or powershell.exe with parameters that indicate remote execution and file placement in public directories.


Technical Mechanics and Defence Evasion

DLL sideloading T1574.001
The malicious DLL msedge_elf.dll is executed through a legitimate Microsoft Edge helper binary identity_helper.exe (the PWA Identity Proxy Host). Both are staged in C:\Users\Public\Libraries which is often less scrutinised by policy.

ETW suppression T1562.001
ChaosBot patches ntdll’s EtwEventWrite by overwriting the prologue with an instruction sequence that forces immediate non logging returns. This blinds rules that rely on event based telemetry and requires defenders to pivot to memory integrity, image load monitoring, and network analytics.

Anti analysis T1497.001
The binary checks for MAC address prefixes associated with common virtualisation platforms and exits when a match is found. This prevents full behaviour exposure during automated detonations.


Persistence and Command and Control

ChaosBot maintains redundant C2 for resilience and flexibility.

Fast Reverse Proxy T1090.003
The backdoor downloads a client binary and configuration into C:\Users\Public\Music then launches it with a PowerShell command that sets output encoding and starts node.exe with a configuration file. The tunnel communicates over TCP port 7000 to an AWS hosted endpoint.

Discord web service C2 T1102.002
The malware authenticates with a bot token, validates through a user query, creates or uses a channel named with the victim hostname, and polls for commands. Supported commands include shell for command execution, download for secondary payloads, and scr for screenshot capture with file upload to the channel.

Table 1 ChaosBot C2 and Persistence Configuration Artifacts

Artifact TypeDescriptionValue or LocationNotes
Malicious DLLChaosBot payloadC:\Users\Public\Libraries\msedge_elf.dllExecuted by the Edge helper loader
Legitimate loaderEdge PWA Identity Proxy HostC:\Users\Public\Libraries\identity_helper.exeAbused for DLL sideloading
Sideloading pathExecution directoryC:\Users\Public\LibrariesUser writable and less policed
FRP client binaryPersistence and C2 tunnelC:\Users\Public\Music\node.exeHigh throughput channel for operators
FRP configurationClient configuration fileC:\Users\Public\Music\node.iniLaunched with node.exe -c
FRP egress portOutbound TCP port7000Monitor for long lived sessions
Known C2 addressFRP remote host18.162.110.113Cloud hosted endpoint
Discord C2 endpointsWeb service API usagediscord dot com slash api slash v10 slashFocus on API usage from non browser processes
Operator monikerThreat actor handlechaos_00019Secondary handle lovebb0024

Known Indicators of Compromise

File Hashes

There are a lot of ChaosBot IoCs so I have created a separate page to view them:

https://cybersecsentinel.com/chaosbot-iocs/

Accounts and Handles

TypeValuePurpose
Operator profilechaos_00019Discord operator account
Secondary handlelovebb0024Reported secondary account
Compromised identityserviceaccountOver privileged AD account used for WMI execution

Detection Engineering

Host focused actions

  • Detect identity_helper.exe execution from user writable paths with image load events and block execution through application control.
  • Detect msedge_elf.dll loads by the Edge helper process.
  • Alert on WmiPrvSE.exe spawning command interpreters or PowerShell with remote execution arguments.
  • Monitor memory integrity for unexpected modifications to ntdll export prologues. Any hook on EtwEventWrite is high signal.

Network focused actions

  • Block and alert on 18.162.110.113 and investigate any prior connections from endpoints.
  • Alert on outbound TCP 7000 to unknown destinations from workstations and VDI pools.
  • Profile Discord usage. Alert on API heavy patterns from non browser processes or from hosts where Discord is not sanctioned.

File and content focused actions

  • Create pre execution YARA signatures for the ETW patch motif and for anti virtual machine OUI checks where available.
  • Flag systems where identity_helper.exe co resides with an unsigned DLL in Public libraries.

Mitigation and Prevention

Mitigation Checklist for Gap Analysis

AreaControlWhat Good Looks LikeEvidence to Gather
User awarenessTargeted education on shortcut and script luresStaff recognise .lnk risks and report decoysTraining records and simulated phishing results
Email filteringBlock shortcut and script based attachmentsGateway rejects .lnk and scripts by policySEG policy exports and quarantine logs
Antivirus protectionEDR with memory integrity and module allow listingAlerts on ETW patching and sideloading from Public pathsEDR policy baselines and recent detections
Two factor authenticationMFA on VPN and all privileged accountsPhishing resistant factors enforced with no bypassesConditional access and VPN policy exports
Log monitoringHigh fidelity process creation and PowerShell loggingWMI spawned shells and FRP launches are alertedSIEM rules and recent alert reviews
Regular updatesTimely patching of Cisco ASA and FTD and browsersCurrent code levels with emergency advisories appliedDevice compliance reports and change tickets
Application controlWDAC or AppLocker allow listsSigned binaries restricted to approved locationsWDAC policy XML and enforcement scope
Network egressLeast privilege outbound policyDiscord restricted to approved hosts and API calls monitoredFirewall rules, proxy logs, and exception lists

Risk Assessment

Threat score 8.0 🔴 High

  • Stealth and resilience. The use of Rust, ETW suppression, signed binary sideloading, and dual C2 channels increases survivability and reduces early detection.
  • Speed to impact. Valid account access combined with automated WMI based fan out can establish broad coverage before containment.
  • Exposure landscape. Contemporary critical issues on remote access appliances elevate the likelihood of parallel access paths and credential theft.
  • Operational intent. Capability set and operator workflow indicate sustained access for reconnaissance and data theft with a clear path to follow on actions.

Conclusion

ChaosBot represents a modern enterprise backdoor that privileges stealth, speed, and redundancy. It exploits identity weaknesses, executes through a trusted loader in a permissive location, silences host level telemetry, and splits control between a popular web service and a reverse proxy tunnel. Defenders should assume partial logging blindness on affected hosts and compensate with memory integrity checks, strict execution controls, identity hardening, and egress monitoring. Immediate MFA enforcement, Cisco remote access patching and hardening, enforcement of application allow lists, and active hunts for the public folder artefacts and FRP patterns are expected to materially reduce risk.


Sources