RustyBuer is a Rust-based rewrite of the Buer malware family designed to preserve compatibility with existing Buer command-and-control infrastructure while improving evasion against detections focused on earlier C-based builds. It functions primarily as a first-stage malware-as-a-service loader or downloader used to establish an initial foothold on Windows systems and retrieve additional payloads. Observed follow-on payloads have included Cobalt Strike Beacon, and Buer operators have been assessed in some cases to support access-as-a-service activity by selling or transferring compromised access to other threat actors. RustyBuer has also been discussed in reporting on tooling associated with actors linked to the TrickBot ecosystem.
Observed delivery has relied on phishing campaigns themed as shipping notices, with victims lured to malicious Microsoft Office documents. Infection required user interaction to enable macro execution, after which the document dropped and launched the Rust-based payload. Campaigns used a Windows Shell DLL application-bypass technique involving trusted system components to reduce endpoint detection opportunities, and persistence was established through startup shortcut creation.
RustyBuer includes anti-analysis and regional filtering logic. Documented behavior includes virtual-machine checks and locale checks intended to avoid execution in certain CIS environments. During beaconing, the malware collects host profiling data such as operating system version, architecture, privilege level, computer and user context, processor information, disk usage, and Active Directory domain details, then transmits this information to its controllers over HTTP(S). Server responses can instruct the malware to download and execute additional payloads.
Campaigns distributing RustyBuer affected organizations across a wide range of industry verticals, consistent with its role as broadly distributed initial-access malware rather than sector-specific tooling.
1 distinct threat actor Mallory has associated with this family across public reporting. Open in Mallory to see the full evidence chain and overlapping campaigns.
...after the discovery of NimRod/Nimza and RustyBuer which are both being leveraged by actors associated with the TrickBot crew.
26 distinct techniques documented for this family, organized by ATT&CK tactic.
The campaigns generally used DHL-themed phishing emails to distribute malicious Word or Excel documents.
The loader uses emails with Word attachments containing macros to download the next stage.
They contained a link to a malicious Microsoft Word or Excel document download that used macros to drop the new malware variant.
A notable aspect of Buer Loader’s arrival is its use of malicious Microsoft Word and Microsoft Excel documents containing an embedded VBA macro that creates a process via WMI.
The C2 functions are handled via HTTP(S) POST requests.
This leads to a Base64-encoded command that is executed by PowerShell.
Further inspection of the command being executed by cmd.exe shows the full base64 command.
They contained a link to a malicious Microsoft Word or Excel document download that used macros to drop the new malware variant.
RustyBuer was embedded directly into the document macro and required user interaction to initiate the infection.
the beacon response can be configured to use one of two options provided to the operator for achieving persistence. These options are to either use a shortcut (LNK) that runs on startup or create a RunOnce registry key.
Once RustyBuer is dropped, it establishes persistence by using a shortcut (.LNK) file which runs at startup.
the beacon response can be configured to use one of two options provided to the operator for achieving persistence. These options are to either use a shortcut (LNK) that runs on startup or create a RunOnce registry key.
Once RustyBuer is dropped, it establishes persistence by using a shortcut (.LNK) file which runs at startup.
the macro function itself is obfuscated using Hex-encoded strings that must be concatenated, reordered, and decoded.
It is observed that a signed XLL file delivers Buer Loader.
This macro leveraged an Application Bypass (Windows Shell DLL via LOLBAS) to evade detection from endpoint security mechanisms. Example Script execution: rundll32.exe shell32.dll,ShellExec_RunDLL C:\ProgramData\OfficeSignCheck.exe
Anti-analysis features Checks for virtual machines.
Buer Loader also uses code obfuscation techniques... Additionally, the loader makes use of several time-based evasion techniques: Reading the Windows installation date; Querying the system time; Using long sleep periods to make dynamic analysis difficult.
Using long sleep periods to make dynamic analysis difficult.
The GetProcessHeap and IsDebuggerPresent functions are used to detect if the malware is being debugged.
One of the notable changes made by Buer Loader was the purchase of Sectigo OV Code Signing certificates. This allowed for a new delivery mechanism, observed as the use of a signed XLL file, to deliver Buer Loader.
A Rust crate ... is used to retrieve system information that is to be sent in an HTTP POST request to the C&C.
Another functionality that this loader contains is to enumerate processes or threads and query a list of all running processes by using CreateToolhelp32Snapshot and ProcessInformation.
These requests contain encrypted system information from the infected machine.
One such functionality is to query local or system time, or GetSystemTimeAsFileTime as seen in Figure 13.
Anti-analysis features Checks for virtual machines.
Buer Loader also uses code obfuscation techniques... Additionally, the loader makes use of several time-based evasion techniques: Reading the Windows installation date; Querying the system time; Using long sleep periods to make dynamic analysis difficult.
Using long sleep periods to make dynamic analysis difficult.
The GetProcessHeap and IsDebuggerPresent functions are used to detect if the malware is being debugged.
With respect to infrastructure, the C&C functionality for Buer Loader is handled by HTTPS POST requests.
Proofpoint researchers observed RustyBuer distributing Cobalt Strike Beacon as a second-stage payload in some instances.
The requests use the following to encrypt or encode the information: Base64, Hex encoding, RC4 encryption.
42 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Values are masked here and available in full in Mallory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.