Author Topic: False Positive - RAM Scan  (Read 1678 times)

0 Members and 1 Guest are viewing this topic.

ArthurG

  • Guest
False Positive - RAM Scan
« on: October 04, 2012, 04:14:06 PM »
Hi there,

I was conducting a customized RAM Rootkit scan (to compare results with the boot scan). I wanted to see if something among the services was a potential rootkit.

However, I received a false positive with SuperAntiSpyware.exe (www.superantispyware.com) the free version. Just to verify my results, I did the same scan on three other computers (one I installed SuperAntiSpyware free version just prior to the scan) to compare results. Each displayed a similar issue (PID was different on each machine, but results were the same). (see image below).

I know SAS free version stays resident to conduct random check for program updates, ensure home page does not change, etc, and the full version does scheduled scans, definition updates, and maintains protection from spyware and such, but I didn't know if anyone else reported the issue from a RAM scan.


Offline Pondus

  • Probably Bot
  • ****
  • Posts: 37529
  • Not a avast user
Re: False Positive - RAM Scan
« Reply #1 on: October 04, 2012, 05:04:19 PM »
well.....you have done what a million others have done...... a custom scan and selected "scan memory"

the short story DO NOT use the scan memory setting as it give some weird results

if you searc the forum for    scan memory / memory scan / detection in memory

you should find a ton of info about why not

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89053
  • No support PMs thanks
Re: False Positive - RAM Scan
« Reply #2 on: October 04, 2012, 05:47:57 PM »
1. It isn't saying SuperAntiSpyware.exe is infected, just that it is the 'Process - 2700' responsible for loading that data into the memory block.

2. It isn't a false positive as you have asked avast to scan memory for viruses, etc. and it has found some in the form of unencrypted virus signatures loaded into memory by SAS.

SAS free also stays resident so that you can do a context memory (right click) scan on a file to do that it has preloaded some signatures in memory.

Same as buying an attack dog, don't be surprised if it bites someone.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.3.6108 (build 24.3.8975.762) UI 1.0.801/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security