Jump to content

Recommended Posts

Last week Malwarebytes found over 50k of pup.optional.adblocker detections during heuristics scanning.  Ran 3 other programs which found no issues. Saw another post with similar issues and you posted that the newest database update would correct it.  I waited a couple of days and installed latest update, still finds 2 detections...


 


I don't have access to the pc at the moment for the log file, but I have a screen shot.


c:\program files (x86)\stdole2.tlb


HKLM\software\wow6432node\microsoft\windows\currentversion\shareddlls|c:\program files(x86)\std..... 


 


Can you help?


 


Thank you,


James


post-171148-0-63728400-1407947687_thumb.

Link to post
Share on other sites

I was able to obtain the log....

 

Malwarebytes Anti-Malware
www.malwarebytes.org
 
Scan Date: 8/13/2014
Scan Time: 7:35:51 AM
Logfile: MalwareScan08-13-14.txt
Administrator: Yes
 
Version: 2.00.2.1012
Malware Database: v2014.08.13.03
Rootkit Database: v2014.08.04.01
License: Trial
Malware Protection: Enabled
Malicious Website Protection: Enabled
Self-protection: Disabled
 
OS: Windows 7 Service Pack 1
CPU: x64
File System: NTFS
User: ********
 
Scan Type: Threat Scan
Result: Completed
Objects Scanned: 511609
Time Elapsed: 21 min, 44 sec
 
Memory: Enabled
Startup: Enabled
Filesystem: Enabled
Archives: Enabled
Rootkits: Disabled
Heuristics: Enabled
PUP: Enabled
PUM: Enabled
 
Processes: 0
(No malicious items detected)
 
Modules: 0
(No malicious items detected)
 
Registry Keys: 0
(No malicious items detected)
 
Registry Values: 1
PUP.Optional.AdBlocker, HKLM\SOFTWARE\WOW6432NODE\MICROSOFT\WINDOWS\CURRENTVERSION\SHAREDDLLS|C:\PROGRAM FILES (X86)\STDOLE2.TLB, 1, , [d5428442c4b7f83e94496c6d738f12ee]
 
Registry Data: 0
(No malicious items detected)
 
Folders: 0
(No malicious items detected)
 
Files: 1
PUP.Optional.AdBlocker, C:\Program Files (x86)\stdole2.tlb, , [d5428442c4b7f83e94496c6d738f12ee], 
 
Physical Sectors: 0
(No malicious items detected)
 
 
(end)
Link to post
Share on other sites

  • Root Admin

Well until Rich returns I'll just say that where that file is located is more than likely why it was flagged even if it was a good file.

No files belong in the root folder like that.

 

C:\PROGRAM FILES (X86)\STDOLE2.TLB

 

If you look on all Windows computers regardless of XP, Vista, Windows 7, Windows 8, Server 2003, etc etc.. There are NO files in the parent root folder for that directory:  C:\PROGRAM FILES (X86)

That alone is reason enough to flag the file as a potential threat.

 

You can upload the file to www. virustotal.com and have them scan it but as said even if it comes back clean it does not belong in that folder period.

Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.