nweissma Posted May 13, 2012 ID:550988 Share Posted May 13, 2012 avast scanned only "operating memory"; it yielded these seven "infecteds" (see attached).i mention that avast would not allow me to move these to chest.likely nothing to worry about -- i merely mention it and ask an mbam tech to explain. Link to post Share on other sites More sharing options...
fivealive Posted May 13, 2012 ID:550990 Share Posted May 13, 2012 you might want to report them as false positives to avast Link to post Share on other sites More sharing options...
AdrianH Posted May 13, 2012 ID:551046 Share Posted May 13, 2012 Hmm, I just recreated the same results. Strange that a full scan doesn't show this up yet a user created memory scan does. Link to post Share on other sites More sharing options...
Fatdcuk Posted May 13, 2012 ID:551048 Share Posted May 13, 2012 Hi guys and thanks for the reports.This most definetly is an Avast False Positive issue and not ours. Link to post Share on other sites More sharing options...
AdrianH Posted May 13, 2012 ID:551094 Share Posted May 13, 2012 DavidR at avast forum explains that this is not Avast reporting infections as such but that it is seeing virus signatures used by MBam.He explains it better than I could :It isn't showing the mbamservice.exe as infected, just that it is the process responsible for loading the data (unencrypted signatures) into memory and it is these signatures avast is detecting.The detections in memory are frequently other security applications loading unencrypted virus signatures into memory. Having set off a scan of memory by an antivirus application looking for virus signatures, don't be too surprised if it finds some in memory. Link to post Share on other sites More sharing options...
Fatdcuk Posted May 13, 2012 ID:551110 Share Posted May 13, 2012 That is fundlementally correct but an encrypted database has to be unecrypted in memory for our application to read it.Avast could fix this operational fp/issue just by whitelisting our service executable Link to post Share on other sites More sharing options...
pondus Posted May 13, 2012 ID:551206 Share Posted May 13, 2012 Avast could fix this operational fp/issue just by whitelisting our service executable or just leave avast settings at default.......as this only happens if you select "Scan memory"it is not unknown to avast forum.......if you search avast forum for "scan memory" or "detection in memory" you fined lots of info Link to post Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now