• Content count

  • Joined

  • Last visited

About pbust

  • Rank

Profile Information

  • Location

Recent Profile Visitors

109,047 profile views
  1. You don't have to change the server executable or its execution method through UNC. All you have to change is the anti-exploit settings. Go to MBAE advanced settings, Application Behavior Protect, and disable the LoadLibrary Protection for Browsers.
  2. Unfortunately, you cannot exclude by MD5 for files executed through UNC. The workaround is to go to MB3 Protection settings, advanced anti-exploit settings, and disable the UNC LoadLibrary technique. This technique is disabled by default in our corporate products, so this problem should only appear in the consumer builds of Malwarebytes.
  3. The latest is 1.10. Go to the Management Console -> Policies -> Anti-Exploit -> enable the checkbox "automatically upgrade MBAE agents". The agents will then upgrade themselves from the Internet to the latest version.
  4. This should have been fixed a while back. Please update your MBAE version to the latest available to verify the fix.
  5. Try upgrading to 1.10 to see if the problem persists: https://forums.malwarebytes.com/topic/208007-betapreview-malwarebytes-anti-exploit-110-build-24/
  6. Yes, I know. All efforts lately by the bad guys are focusing on malspam tricks. Make sure anti-exploit is turned on. Related reading: https://blog.malwarebytes.com/threat-analysis/2017/08/locky-ransomware-adds-anti-sandbox-feature/ Stay safe!
  7. That's one of the tactics the latest ransomware malspam campaigns are using. That's a legit block of an attack. It was blocked before the powershell payload could even run (and before the ransomware was even attempted to be downloaded into the endpoints).
  8. 7-zip is not protected by the latest beta.

    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.).
  9. That's a hard block. You don't want to allow Word to perform those types of actions. Its one of the top 3 malspam infection vectors. The only way to allow it is to deactivate the Word shield, which we obviously don't recommend. Seems like the parent is Java. Could this be by some in-house or third-party application? If that's the case, I'd be having a conversation about basic security best practices with the vendor. I know this puts you between a rock and a hard place and am sorry for that, but unfortunately from our perspective allowing this type of Word behavior would practically equate to allowing our customers to become infected.
  10. Correct, network exploits like SMB/NetBios are outside the scope of MBAE. Btw IPS/IDS engines would also be blind to it at 0-day without a signature to apply to it.
  11. Sorry it took so long. The MB 3.1 beta has just been published here: https://forums.malwarebytes.com/topic/200230-new-beta-malwarebytes-3101716/ It includes the fix for the Office issue. FWIW I think you are all right. We've had a lot of issues in the past for how to deal with conflicts with betas and 3rd party software, but OTOH MSFT started throttling Win10 CU and MB3 should be compatible out of the gate. Let's keep it civil and thanks for keeping us honest.
  12. We're working through Microsoft Virus Initiative (MVI). As soon as we give them the build they'll point their support people to it.
  13. David, I can assure you we are giving this issue top priority.There are a couple of other big moving parts with the impending release of 3.1 which includes this fix and is almost code complete. As soon as we have the build we will post it here and release an automatic Component Update to the entire user base. Sorry for the problem this has caused all of you. It was triggered due to an unforeseen last minute change in the Win10 Creators Update. We have been in communication with Microsoft since the first time this was reported and are working with them on a daily basis to deploy the fix asap.
  14. We're two weeks away from the next scheduled release for MB3, but we'll be discussing an emergency AeSdk-only Component Update tomorrow. Please stand by and thanks for your patience.