Micah,
Thanks for the explanation. As I thought about this, I realized that
if I go to the trouble of a VirusTotal scan, I ought to switch to the
big picture and take all the engines there into account. On truly
dubious items I probably will just take the local ClamAV's report on
face value and nuk
Your results locally could differ from VirusTotal a little even if you just had
VirusTotal re-scan the file. I believe they are running ClamAV v0.99.2 and
there are is some slight variation between that and the latest 0.99.3-beta2 but
there isn’t much and it should be for the better. Of course
I began doing so with the first hit, then at the bottom of the page I
saw the notice to first update the sigs with freshclam. Freshclam runs
on an hourly schedule here, so I saw little need to do so, but for
completeness I did, and it showed no updating, and said the sigs were
up to date. The machi
On Fri, Jan 12, 2018 at 08:31 PM, Paul B. wrote:
> I just ran a scan on my root drive, and had 3 hits. I ran each of them
> by VirusTotal, and each VT had ClamAV reporting them as Clean. The
> output here was:
>
> /home/paul/.config/vivaldi/Default/Extensions/kbmfpngjjgdllneeigpgjifpgocmfgmb/5.10.
I just ran a scan on my root drive, and had 3 hits. I ran each of them
by VirusTotal, and each VT had ClamAV reporting them as Clean. The
output here was:
/home/paul/.config/vivaldi/Default/Extensions/kbmfpngjjgdllneeigpgjifpgocmfgmb/5.10.1_0/foreground.entry.js.map:
Html.Exploit.CVE_2017_8738-633
