Jump to content

False Positive: Spotify libegl.dll


skoivan
 Share

Recommended Posts

Kindly confirm, I believe this is a false positive.

 

-Scan Details-
Process: 0
(No malicious items detected)

Module: 1
Trojan.MalPack, <userpath>\APPDATA\ROAMING\SPOTIFY\LIBEGL.DLL, No Action By User, [4158], [564043],1.0.6755

Registry Key: 0
(No malicious items detected)

Registry Value: 0
(No malicious items detected)

Registry Data: 0
(No malicious items detected)

Data Stream: 0
(No malicious items detected)

Folder: 0
(No malicious items detected)

File: 1
Trojan.MalPack, <userpath>\APPDATA\ROAMING\SPOTIFY\LIBEGL.DLL, No Action By User, [4158], [564043],1.0.6755

Physical Sector: 0
(No malicious items detected)

WMI: 0
(No malicious items detected)


(end)

Link to post
Share on other sites

Quote

-Scan Details-
Process: 0
(No malicious items detected)

Module: 1
Trojan.MalPack, C:\PROGRAM FILES\WINDOWSAPPS\SPOTIFYAB.SPOTIFYMUSIC_1.88.353.0_X86__ZPDNEKDRZREA0\LIBEGL.DLL, No Action By User, [4159], [564043],1.0.6757

Registry Key: 0
(No malicious items detected)

Registry Value: 0
(No malicious items detected)

Registry Data: 0
(No malicious items detected)

Data Stream: 0
(No malicious items detected)

Folder: 0
(No malicious items detected)

File: 1
Trojan.MalPack, C:\PROGRAM FILES\WINDOWSAPPS\SPOTIFYAB.SPOTIFYMUSIC_1.88.353.0_X86__ZPDNEKDRZREA0\LIBEGL.DLL, No Action By User, [4159], [564043],1.0.6757

Physical Sector: 0
(No malicious items detected)

WMI: 0
(No malicious items detected)


(end)

Same thing detected for me too, but I see you've already reported it @skoivan so that's awesome to see the MBAM team is already on the case. :) 

 

 

Link to post
Share on other sites

30 minutes ago, cli said:

Thanks for reporting. This will be fixed in the next update.

Thanks for the confirmation.

 

Sorry, I'm not familiar how updates work... if I chose to quarantine the file and it's identified as a false positive, does it automatically get unquarantined on the next update?

Link to post
Share on other sites

  • Staff

 

Quote
33 minutes ago, skoivan said:

Thanks for the confirmation.

 

Sorry, I'm not familiar how updates work... if I chose to quarantine the file and it's identified as a false positive, does it automatically get unquarantined on the next update?

 

Please update and then unquarrantine the file.

Link to post
Share on other sites

It also reports the same thing for an dll file of the same name in the Wallpaper Engine program.

 

Malwarebytes
www.malwarebytes.com

-Log Details-
Scan Date: 9/10/18
Scan Time: 7:50 PM
Log File: 4af007b0-b554-11e8-aa44-4ccc6a2f7f54.json

-Software Information-
Version: 3.5.1.2522
Components Version: 1.0.441
Update Package Version: 1.0.6755
License: Premium

-System Information-
OS: Windows 10 (Build 17134.228)
CPU: x64
File System: NTFS
User: 

-Scan Summary-
Scan Type: Custom Scan
Scan Initiated By: Manual
Result: Completed
Objects Scanned: 849674
Threats Detected: 2
Threats Quarantined: 2
Time Elapsed: 2 hr, 43 min, 7 sec

-Scan Options-
Memory: Enabled
Startup: Enabled
Filesystem: Enabled
Archives: Enabled
Rootkits: Enabled
Heuristics: Enabled
PUP: Detect
PUM: Detect

-Scan Details-
Process: 0
(No malicious items detected)

Module: 0
(No malicious items detected)

Registry Key: 0
(No malicious items detected)

Registry Value: 0
(No malicious items detected)

Registry Data: 0
(No malicious items detected)

Data Stream: 0
(No malicious items detected)

Folder: 0
(No malicious items detected)

File: 2
Trojan.MalPack, C:\PROGRAM FILES (X86)\STEAM\STEAMAPPS\COMMON\WALLPAPER_ENGINE\BIN\LIBEGL.DLL, Delete-on-Reboot, [4158], [564043],1.0.6755
Trojan.MalPack, C:\PROGRAM FILES (X86)\STEAM\STEAMAPPS\COMMON\WALLPAPER_ENGINE\DISTRIBUTION\BIN\LIBEGL.DLL, Delete-on-Reboot, [4158], [564043],1.0.6755

Physical Sector: 0
(No malicious items detected)

WMI: 0
(No malicious items detected)


(end)

Edited by thisisu
Link to post
Share on other sites

  • Staff
37 minutes ago, Jynxie said:

It also reports the same thing for an dll file of the same name in the Wallpaper Engine program.

Yes, but it was the same 1 rule that hit at least two different files. It has since been pulled from the database. Please update to:

MBAM2 Version: v2018.09.11.04
MBAM3 Version: 1.0.6761
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
 Share

  • 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.