I have indeed emailed Emsisoft about this, as I noticed something interesting.
So, as an experiment, I uninstalled Avast using the clear tool and ran the same Emsisoft Emergency Kit (EEK) scan that found the “malware.” Nothing was found, which was expected.
Then I re-installed Avast and after a restart to load my settings file, I re-ran that same EEK scan with the same parameters, and nothing was found. I checked to see if the specific .dll file was still in the Program Files\Avast Software folder, and it indeed was in the same places under the ‘defs’ and ‘x86’ subfolders.
So I ran another EEK scan just of that Avast Software folder a couple of times, and it found nothing. Ok, cool.
But then I think maybe the EEK software remembered me skipping those two files in the first place, and maybe took that as me treating them as false positives (EDIT: I have been informed by Emsisoft that this is not the case. If a scan picks something up and you ignore it, it’ll show up again on the next scan). Probably not the case, but to be safe I deleted the EEK folder I had, and then got their Emergency Kit file to extract their files again on my computer (EEK doesn’t install on your computer, it just contains itself in a folder with the files you need). I re-ran the scan on the Program Files\Avast Software folder using EEK, and it came back clean.
Then Avast asked me to restart my computer with a pop up. So I go “uh oh” and restarted. I let my laptop sit while I went to a medical appointment, came back and ran the same EEK scan on the Program Files\Avast Software folder, and it found nothing.
So either Emsisoft’s Emergency scanner had a hiccup that one time, it remembers me skipping those files still and treats that as false positive (even though I didn’t mark them as such), or Emsisoft fixed the issue on their end with an update over the last 24 hours or so.
Thanks for reluctantly following me on this journey so far.