Sampei_Nihira Posted June 30, 2017 ID:1139560 Share Posted June 30, 2017 OS Windos XP SP3: Link to post Share on other sites More sharing options...
infectedRooZies Posted July 2, 2017 ID:1139925 Share Posted July 2, 2017 Well, upgrade your operating system to Windows 10, and get Malwarebytes 3.1.2. Maybe helps you out. 1 Link to post Share on other sites More sharing options...
Sampei_Nihira Posted July 2, 2017 Author ID:1139953 Share Posted July 2, 2017 There are 3 bugs: 1) As described above. 2) No reference list "shields". 3) No pop-up at the program opening. Link to post Share on other sites More sharing options...
infectedRooZies Posted July 3, 2017 ID:1140159 Share Posted July 3, 2017 Why are there 3 bugs? Link to post Share on other sites More sharing options...
cutting_edgetech Posted July 4, 2017 ID:1140328 Share Posted July 4, 2017 The latest beta is not protecting WinRAR either. It's not injecting into WinRAR.exe. If you try adding WinRAR.exe to the Shields List it says it's already on the list, even though it's not visibly on the list anywhere. I reported the same problem about 2 years ago. I'm using Windows 10 X64. Link to post Share on other sites More sharing options...
Sampei_Nihira Posted July 4, 2017 Author ID:1140403 Share Posted July 4, 2017 8 hours ago, cutting_edgetech said: The latest beta is not protecting WinRAR either. It's not injecting into WinRAR.exe. If you try adding WinRAR.exe to the Shields List it says it's already on the list, even though it's not visibly on the list anywhere. I reported the same problem about 2 years ago. I'm using Windows 10 X64. Same problem. TH Cutting_Edgetech. Link to post Share on other sites More sharing options...
TheSeeker11 Posted July 5, 2017 ID:1140502 Share Posted July 5, 2017 On 01/07/2017 at 1:29 AM, Sampei_Nihira said: OS Windos XP SP3: Hard to imagine that you're overly concerned with security when you're running an OS that is no longer patched. Link to post Share on other sites More sharing options...
Sampei_Nihira Posted July 5, 2017 Author ID:1140595 Share Posted July 5, 2017 (edited) POS READY2009 (99,99% = XP) is supported. Edited July 5, 2017 by Sampei_Nihira Link to post Share on other sites More sharing options...
cutting_edgetech Posted July 6, 2017 ID:1140725 Share Posted July 6, 2017 On 7/4/2017 at 9:07 AM, Sampei_Nihira said: Same problem. TH Cutting_Edgetech. No problem. Link to post Share on other sites More sharing options...
cutting_edgetech Posted July 6, 2017 ID:1140726 Share Posted July 6, 2017 It seems Malwarebytes has been awful silent lately in regards to MBAE development. No responses to bugs by the developer lately. They must be keeping pbust busy working on Malwarebytes 3.0. I worry lack of development will make MBAE's user-base migrate to a different product like HMPA. Then Malwarebytes may decide there's no justification to support two separate products. I guess time will only tell. Link to post Share on other sites More sharing options...
Aura Posted July 7, 2017 ID:1141230 Share Posted July 7, 2017 On 05/07/2017 at 10:20 AM, Sampei_Nihira said: POS READY2009 (99,99% = XP) is supported. Not officially. https://betanews.com/2014/05/27/microsoft-warns-against-xp-update-hack-suggests-users-upgrade-to-windows-8-1-instead/ Link to post Share on other sites More sharing options...
Staff Rsullinger Posted July 7, 2017 Staff ID:1141269 Share Posted July 7, 2017 Hello Sampei_Nihira, The reason why you are not seeing it injected there or you are not able to add the shield (also what cutting_edgetech mentioned as well) is because 7zip/winrar/winzip apps are protected internally but they work differently from regular shields. So you won't see the normal behavior as you would with a regular mbae shield. This is something that has always been in the product. So you are still protected using those apps. I do apologize for the delay with this. I was getting the information clarified by our team to make sure I was giving you the correct information. Link to post Share on other sites More sharing options...
Sampei_Nihira Posted July 8, 2017 Author ID:1141391 Share Posted July 8, 2017 (edited) Hi Rsullinger, I do not think so for 2 reasons: 1) With Process Explorer you would see mbae.dll. 2) Rename the Exploit Test Tool (HPA3) as 7-zip/winrar/..............exe: https://www.hitmanpro.com/en-us/downloads.aspx The tests have failed. The conclusion is that there is no protection. Please check. TH. Edited July 8, 2017 by Sampei_Nihira Link to post Share on other sites More sharing options...
cutting_edgetech Posted July 9, 2017 ID:1141457 Share Posted July 9, 2017 On 7/7/2017 at 5:12 PM, Rsullinger said: Hello Sampei_Nihira, The reason why you are not seeing it injected there or you are not able to add the shield (also what cutting_edgetech mentioned as well) is because 7zip/winrar/winzip apps are protected internally but they work differently from regular shields. So you won't see the normal behavior as you would with a regular mbae shield. This is something that has always been in the product. So you are still protected using those apps. I do apologize for the delay with this. I was getting the information clarified by our team to make sure I was giving you the correct information. That is strange because when I reported this issue in the past, pbust looked into the problem, and i'm pretty sure I saw WinRAR being injected into in a later build after I reported it. This was like 1 1/2 years ago, or something like that. Maybe the protection mechanisms have been changed since then. Link to post Share on other sites More sharing options...
Sampei_Nihira Posted July 16, 2017 Author ID:1143161 Share Posted July 16, 2017 Up Link to post Share on other sites More sharing options...
Staff pbust Posted August 15, 2017 Staff ID:1153850 Share Posted August 15, 2017 On 7/8/2017 at 9:58 AM, Sampei_Nihira said: I do not think so for 2 reasons: 1) With Process Explorer you would see mbae.dll. 2) Rename the Exploit Test Tool (HPA3) as 7-zip/winrar/..............exe: Like Ron said, the internal shields for the compressor family works in a different way than regular shields. It cannot be tested the same way as the regular shields (i.e. looking for dll injection, renaming the tool, etc.). 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