CmdID / Files

authfwcfg.dll

Windows Defender Firewall with Advanced Security Configuration Helper file version info

Library on Windows 2 known copies with hashes 1 Sigma rule names it

Is it the real authfwcfg.dll?

file version info and known copies

Installed inC:\Windows\system32\
C:\Windows\SysWOW64\

Signed byMicrosoft Windows

ProductMicrosoft Windows Operating System, Microsoft Corporation

DescriptionWindows Defender Firewall with Advanced Security Configuration Helper

2 known copies

10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\SysWOW64\authfwcfg.dll · signed by Microsoft Windows

SHA-256584c99c097d82a35a4d6d91070bc0673c91546436d7d814db9ba43e6c582bc84SHA-1554ed14a569d91dfdfe31cd3ad832fc5181560d4MD540bcf215f5dffed6108659ae91f99bf9

10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\authfwcfg.dll · signed by Microsoft Windows

SHA-256e4576c2c520e96a9d6b9d8905823258e81795156db10a70730f4934ba78961d7SHA-165d357f5a9f9716281743f30a0f730e522868ae3MD51e1e236b416d810cb9736073d68e17eb

From the file’s version info and the copies recorded by xCyclopedia (MIT). A copy in another folder, signed by someone else or with another hash is not necessarily malicious, but it is worth a closer look. In Ceplin, "<hash>".whatis() says which known copy an MD5, SHA-1 or SHA-256 is.

What detects it

Sigma rules that name authfwcfg.dll

When it is loaded

highPotential System DLL Sideloading From Non System LocationsNasreddine Bencherchali (Nextron Systems)

CmdID evaluates Sigma’s process creation rules against a command line. These watch what a command line does not show: a library or a driver loading, a file written, the registry, another process opened, event logs. They are listed as Sigma has them, at SigmaHQ.