Jump to content

pbust

Staff
  • Content Count

    3,372
  • Joined

  • Last visited

Posts posted by pbust


  1. 29 minutes ago, TheMSBob said:

    I had to modify the mbes-fixer.bat for corporate use to use C$ and not C% in the line, "net use Z: "\\%%a\C$" /user:"%%a\%LOCALADMIN%" "%PASSWORD%""

    Good catch, I fixed it already.

    Are you seeing the script delete the *.ref file successfully or is it failing in that step?


  2. Updated guidance, tools, and processes have been posted in the following post:

    Please refer to the new guidance for any and all situations where the previous guidance was failing.

    Thanks and again, sorry for all the troubles this is causing people. We are deeply sorry and continue to work throughout the weekend and night to make things right. If you are still affected, please feel free to reach out to me directly at pbustamante@malwarebytes.com.

     


  3. In the early morning of Saturday, January 27, 2018, a faulty Web Protection update was released which caused a connection issue for many of our customers. As a side effect of the web protection blocks, the product also spiked memory usage and possibly caused a crash. We triaged the issue quickly and pushed a protection update on Saturday, January 27, 2018 at 10:48a PST.

    The affected products were Malwarebytes 3 Premium, Malwarebytes Management Console (MBMC), and Malwarebytes Endpoint Protection (aka Malwarebytes Cloud Console). Malwarebytes for Mac, Android, AdwCleaner, Incident Response and Breach Remediation were not and are not affected. For a complete description and root cause analysis please click here.

    Please note endpoints were not affected if they were turned off before Saturday, Jan 27, 2018 and then were not turned back on until after Saturday, Jan 27, 2018 at 11am PST. For affected endpoints, this thread is intended as recovery guidance.

     

    Guidance below applies to corporate customers using the on-premise Malwarebytes Management Console (MBMC) as well as corporate customers using the cloud-based Malwarebytes Endpoint Protection (aka Malwarebytes Cloud Console). If you're a home user and/or Malwarebytes 3 Premium user, click here for details on how to recover your systems.

     

    For corporate customers running the on-premise Malwarebytes Management Console (MBMC)

    1. In the Malwarebytes Management Console, edit the Policy and disable real-time protection
    2. Once real-time is protection is disabled and your clients can communicate, highlight the endpoints on the Client tab and click the Update Database button at the top. This should fix it for most endpoints.
    3. If any endpoints fail to get the update, you will have to force an update. This can be done locally on the endpoint or remotely over the network.
      • Locally on the endpoint (logged in to the machine). You can point your endpoint users to do this themselves:
        1. Download and execute MBAM Rules Offline Updater
        2. Reboot the computer
      • Remotely over the network
        1. Make sure your machine is on a non-blocked IP (i.e. 10.x.x.x or 192.x.x.x). Blocked IP ranges are from 128.x.x.x to 191.x.x.x.
          *NOTE* It is recommended to not use your MBMC server for this task
        2. Download the following script and extract it to a folder on your computer
        3. Create a file named hostnames.txt in the same folder, adding one IP per line for each of your endpoint IPs. You can export a list of IPs with the faulty update from the Management Console (sort by update version, select affected ones, copy, and paste into notepad).
        4. If your internal DNS is not on a blocked IP range, you can feed hostnames.txt with hostnames instead of IPs
        5. Edit the script and type in the *LOCAL* admin username and password for endpoints (i.e. NOT the domain admin) in the first 2 lines
        6. Run the batch file, which will delete the faulty database file and schedule a reboot in 30 seconds
    4. Once all the machines are updated, turn on real-time protection in the Management Console Policy settings.
    5. If the Management Server SQL database grows heavily and takes up too much space, feel free to truncate the contents of the TBL_ClientSecurityLog and TBL_ClientSystemLog SQL tables. Detailed instructions can be found in this document. IMPORTANT: this will remove ALL detection history and is irreversible.

     

    For corporate customers running the cloud-based Malwarebytes Endpoint Protection (aka Malwarebytes Cloud Console)

    1. In the Malwarebytes Cloud Console, go to Settings -> Policy and disable Web Protection and Self-Protection (if enabled). Do this for all the Policies
    2. On the Endpoints section, choose "select all" and choose "Check for Protection Updates" from the Actions button. This should fix it for most endpoints.
    3. If any endpoints fail to get the protection updates, you will have to force an update. This can be done locally on the endpoint or remotely over the network.
      • Locally on the endpoint (logged in to the machine). You can point your endpoint users to do this themselves:
        1. Login to the machine and start a scan by right-clicking on the Malwarebytes traybar icon. This will force an update and fix the issue.
        2. Cancel the scan and reboot the machine. This should fix the problem in most cases.
        3. If the above doesn't work or the machine is unresponsive, download mbep-fixer.exe to your Desktop.
          1. If you want to deploy this over the network using SCCM or other similar platforms, you can use instead use mbep-fixer.msi.
        4. Execute mbep-fixer.exe. You will need to execute this as admin.
        5. Reboot.
      • Remotely over the network
        1. Make sure your machine is on a non-blocked IP (i.e. 10.x.x.x or 192.x.x.x). Blocked IP ranges are from 128.x.x.x to 191.x.x.x.
        2. Download the following script and extract it to a folder on your computer
        3. Create a file named hostnames.txt in the same folder, adding one IP per line for each of your endpoint IPs
        4. If your internal DNS is not on a blocked IP range, you can feed hostnames.txt with hostnames instead of IPs
        5. Edit the script and type in the *LOCAL* admin username and password for endpoints (i.e. NOT the domain admin) in the first 2 lines
        6. Run the batch file, which will delete the faulty database file and schedule a reboot in 30 seconds
    4. Once all machines are updated and connecting correctly, go to the Cloud Console, Settings, Policy, and enable Web Protection and Self-Protection again.

    If the above guidance does not help and you are a corporate customer, please contact corporate-support@malwarebytes.com for further support.


  4. What's the pop-up you are seeing? Is it a balloon notification from the system tray saying that "XYZ application is protected" or something to that effect? If this is the popup you are referring you, please check the Anti-Exploit settings, specifically the "Show system tray notification tooltips" checkbox.

     

    image.png.c0191e08c31683fe237281e547825026.png


  5. From here: https://forums.malwarebytes.com/topic/191650-malwarebytes-3-frequently-asked-questions/#comment-1077438

    Quote

     

    What is an antivirus replacement, and how can Malwarebytes 3.0 replace my antivirus?
    Antivirus replacements utilize signature-less and behavior-based detection technologies to catch the latest and most relevant threats, as opposed to anti-virus programs that rely on large databases of signatures that can quickly become outdated and are typically ineffective against many modern threats. In combination, all of our technologies can replace antivirus if a customer wishes to do so. Over 50% of our home user customers have already replaced their Symantec, McAfee, etc. with Malwarebytes Anti-Malware Premium. We believe in layered defense and built Malwarebytes 3.0 Premium to provide the right mix of proactive and signature-less technologies to combat modern threats and zero-day malware. The combination of our Anti-Malware, Anti-Exploit, Anti-Ransomware, Website Protection, and Remediation technologies provides better coverage against modern and zero-day threats than the traditional antivirus companies that charge more for less effective protection.

    Traditional antivirus vendors have struggled to keep pace with rapidly-changing malware, especially ransomware and data breaches where 0-hour protection has become the only meaningfully-relevant protection. In today’s modern threat world, where professional malware writers make their living engineering new ways to bypass protection, it is more important than ever to utilize signature-less technology and layered security to provide the greatest possible chance of defense. It is just as important to provide comprehensive remediation capabilities to clean up active malware when all else fails.

    Prior to Malwarebytes 3.0, our software was intended to be layered together with a traditional antivirus. Malwarebytes 1.x and 2.x contained only two primary layers of defense (Malware Protection and Website Protection) plus remediation, none of which is fully signature-less. But in Malwarebytes 3.0, with the addition of the three signature-less anti-exploit layers and the signature-less anti-ransomware layer, Malwarebytes defense against real-world threats has finally surpassed that of the traditional AVs.

    We didn’t originally expect to draw this conclusion. But after we developed the anti-exploit, anti-ransomware, and other Application Behavioral Protection technology in Malwarebytes 3.0, our researchers tested our performance against the full landscape of real-world threats and found we offered our users more comprehensive protection at a better price with Malwarebytes 3.0 than by recommending you buy a separate traditional AV. So we did it.

    For our users who do prefer to continue using a traditional antivirus alongside Malwarebytes, by all means please continue to do so. Malwarebytes will always maintain compatibility with all major security software on the market, both free and paid. In particular, Microsoft’s traditional antivirus Windows Defender is included by default and for free with Windows 8 and 10, and is a useful additional layer alongside Malwarebytes 3.0.

    So in summary, our recommendations are:

    • If you would prefer to use only one security product, choose Malwarebytes 3.0 Premium. Based on our testing, Malwarebytes 3.0 alone provides excellent protection against today’s threat landscape.
    • If you would prefer to pay for only one security product, choose Malwarebytes 3.0 Premium and add a free traditional antivirus like Windows Defender (pre-installed for free in Windows 8 and 10). Malwarebytes installs alongside Windows Defender by default, so this is the default configuration in Windows 8 and 10.
    • If you would prefer to pay for two security products, by all means feel free to do so. Malwarebytes is compatible with all major security products on the market.
     


     

     


  6. 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.).

     


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


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

     


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

     

     

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