Shep7000 Posted May 25, 2019 ID:1314258 Share Posted May 25, 2019 File name: TIMEDATE.CP_ SHA256: 9bd7592e4e1a9c960c37acb673cdfa7e4cd1d9a6767369654cd323cf43ebb219 SHA1: 2cba53a399a2408bdc01e6bdca68b81c56fecb3b MD5: 5213fc3407499e9b342918e3965fa84c File size: 41.4 KB ( 42405 bytes ) File type: CAB Detection ratio: 1 / 57 https://www.virustotal.com/en/file/9bd7592e4e1a9c960c37acb673cdfa7e4cd1d9a6767369654cd323cf43ebb219/analysis/1558769237/ TIMEDATE.7z MBScanLog.txt Link to post Share on other sites More sharing options...
Lesyk009 Posted May 25, 2019 ID:1314269 Share Posted May 25, 2019 I also got this: C:\I386\TIMEDATE.CP_ Link to post Share on other sites More sharing options...
humanoid45 Posted May 25, 2019 ID:1314321 Share Posted May 25, 2019 Same thing.....Trojan MalPack.GS....TimeDate.cpl Version 3.5.1.2522 Win XP Link to post Share on other sites More sharing options...
thisisu Posted May 25, 2019 ID:1314334 Share Posted May 25, 2019 Thanks for the reports. An update is going out to fix this. Link to post Share on other sites More sharing options...
thisisu Posted May 25, 2019 ID:1314342 Share Posted May 25, 2019 Fixed in: MBAM2 Version: v2019.05.25.06 MBAM3 Version: 1.0.10770 Link to post Share on other sites More sharing options...
Shep7000 Posted May 25, 2019 Author ID:1314346 Share Posted May 25, 2019 1 hour ago, thisisu said: Fixed in: MBAM2 Version: v2019.05.25.06 MBAM3 Version: 1.0.10770 Thank you! Link to post Share on other sites More sharing options...
ColdlyIndifferent Posted May 25, 2019 ID:1314350 Share Posted May 25, 2019 I'm was getting this with WinXP running on a VM both timedate.cpl and an associated cache.dll causing me to do a full system scan as the supposed trojan sounded extra nasty. So time wasted worrying and doing that not appreciated. However I can also confirm the later update in the day: v2019.05.25.06 appears to have fixed the problem. Thanks for that. Was this a WinXP 32bit only thing? I ask because I updated my host 64bit OS's Malwarebytes definitions at the same time and did my at least weekly quick scan at the same time and it did not flag up the same file(s) either from outside scanning the VM XP installation or indeed its own timedate.cpl files, present in both the System32 and SysWOW64 folders. The file concerned appears to be the OS clock so how on earth did that rather important system file end up getting identified as a trojan anyway? 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