Hackers abuse Windows error reporting tool to deploy malware

Gandalf_The_Grey

Level 85
Thread author
Verified
Honorary Member
Top Poster
Content Creator
Well-known
Forum Veteran
Apr 24, 2016
7,745
6
81,428
8,389
54
The Netherlands
Hackers are abusing the Windows Problem Reporting (WerFault.exe) error reporting tool for Windows to load malware into a compromised system's memory using a DLL sideloading technique.

The use of this Windows executable is to stealthy infect devices without raising any alarms on the breached system by launching the malware through a legitimate Windows executable.

The new campaign was spotted by K7 Security Labs, which could not identify the hackers, but they are believed to be based in China.

The malware campaign starts with the arrival of an email with an ISO attachment. When double-clicked, the ISO will mount itself as a new drive letter containing a legitimate copy of the Windows WerFault.exe executable, a DLL file ('faultrep.dll'), an XLS file ('File.xls'), and a shortcut file ('inventory & our specialties.lnk').

WerFault is the standard Windows error reporting tool used in Windows 10 and 11, allowing the system to track and report errors related to the operating system or applications.

Windows use the tool to report an error and receive potential solution recommendations.

Antivirus tools commonly trust WerFault as it's a legitimate Windows executable signed by Microsoft, so launching it on the system won't usually trigger alerts to warn the victim.

When WerFault.exe is launched, it will use a known DLL sideloading flaw to load the malicious 'faultrep.dll' DLL contained in the ISO.
 
You should always disable Windows Error Reporting in services. Ii's been abuse by NSA and Now other APT groups for years. But the question is does this stop WerFault.exe from running or being vulnerable to sideloading? I'm not sure why it's needed these days, don't they have enough telemetry now through other means?
 
Last edited:
You should always disable Windows Error Reporting in services. Ii's been abuse by NSA and Now other APT groups for years. But the question is does this stop WerFault.exe from running or being vulnerable to sideloading?
No, it does not. You can even delete WerFault.exe from Windows. The attack uses WerFault.exe from the ISO.
There are thousands of signed executables vulnerable to DLL hijacking (when system DLL is used) and much more when a usual DLL sideloading is abused.
 
Last edited:
Interesting sample, tested with OSArmor (Basic Protection profile):

osa-test-werfault.png


And in case I disable the "Block execution of suspicious command-line string" rule, it is blocked by another rule:

osa-test-werfault2.png