If you’ve spent any time digging through the installation directories of legacy enterprise software—think document management systems, ERP clients, or older OCR packages—you’ve likely stumbled across a file named ufscanner.dll . It sits there, often ignored, next to a sea of other DLLs. But this particular file has a story.
If unsigned or signed by an untrusted CA (e.g., “DigiCert Corp” with a 2024 date), treat as hostile. Legit exports: UF_OpenScanner , UF_CloseScanner , UF_StartScan , UF_StopScan . ufscanner.dll
| Family | Payload | Persistence mechanism | |----------------|---------------------------------------------|-------------------------------------------| | | Banking trojan, form grabbing | Registry Run key via UF_OpenScanner | | Emotet | Spreader module, mail harvesting | Scheduled task named “UFScanner” | | CobaltStrike | Beacon with scanner-themed sleep masks | Injected into wuauclt.exe | If you’ve spent any time digging through the
In the vast majority of legitimate cases—particularly in software from the late 1990s to early 2010s— The DLL was part of a modular scanner abstraction layer, primarily distributed by Unisys and later licensed to third-party document management vendors like Hyland (OnBase), Kofax, and EMC Captiva. If unsigned or signed by an untrusted CA (e
Depending on who you ask, ufscanner.dll is either a forgotten workhorse of peripheral integration or a subtle indicator of system compromise. In this post, we’ll tear down the mystery: what it is, why it exists, and how to tell the legitimate version from a malicious impostor. The first question is always: what does “UF” stand for?