Jump to content

treed

Staff
  • Content Count

    1,666
  • Joined

  • Last visited

Community Reputation

35 Excellent

8 Followers

About treed

  • Rank
    Staff

Recent Profile Visitors

18,336 profile views
  1. On migration via Setup Assistant or Migration Assistant, I honestly have no idea what would happen. I don't think that's a test case we've run, AFAIK. Normally, if you were to try to activate on too many devices, you'd get an error message and would immediately know. But I have no idea what would happen with a migration. And if you had enough seats on your license to support another device, I'm honestly not sure if the migrated software would show up as Premium, or if it would see that it's running on a different device and revert to free. These are things we'll need to test. However
  2. Is this consistent, or just that first time? About how much longer does the scan take? Also, are you comparing manual scans with scheduled scans, or manuals scans now with manual scans when you were doing them in version 4.6?
  3. Nope, I don't think it's an issue, just a change in reporting. If the counts changed for browser extensions (for example, reporting on all the files present inside an extension rather than counting each extension as one), having 14 extensions on the system could easily cause such a change. However, I'm going to verify this with the dev team on Monday. Just to confirm with you, the scan didn't take longer than previously, right?
  4. ? Did it miss something that you think it should have detected? If so, what was that?
  5. I see the same thing here. I'm guessing that the way it's reporting the number of objects when scanning browser extensions has changed with the improvements to that code. Do you have a large number of browser extensions on your system, or a few very large browser extensions?
  6. We have released Malwarebytes for Mac 4.7 into the beta channel today, so you should get it if you have the "Beta application updates" setting turned on. There's nothing really visibly new in this release, but we made some significant optimizations and improvements to the scan engine for detecting browser extensions. The code is both more efficient and more accurate. The biggest thing we'd like to hear about is any issues you see with scanning, and a general feel for how fast you think scans are now vs before. If you've been having CPU usage issues, does this beta solve that, only he
  7. In general, MWB is an abbreviation folks like you and I understand, but average users don't often know what that means, unfortunately.
  8. We generally recommend against them. They can fix some uncommon issues, like corrupted caches. However, that doesn't happen often - I've never seen caches become corrupt on any of my machines, and I believe if your caches get corrupt, there's probably some other issue at play. On the other hand, routinely removing caches, log files, etc, is actually not good. Caches are there to keep your computer running fast, and if you remove them they'll just get re-created (which takes time). Logs can contain important diagnostic information, so if you're removing those, it can remove the ability to
  9. Carl, Yup, looks like it must have been installed on your Mac at some point, but the plist files were never removed. For folks who do use Cocktail, we've got an update out that will ensure those files don't get detected any more. To ensure you've got the latest database update, choose Update Protection from the Malwarebytes menu bar icon.
  10. It looks like this is based on rules we recently added related to OSX.OSAMiner. One of those changes was to add detection of a launch agent plist file that attempts to directly run an AppleScript command via the "osascript -e" command. This is highly suspicious behavior, seen with OSX.OSAMiner, and very similar to other past malware that runs complicated shell scripts directly via a launch agent or daemon plist. In this case, it looks like this is detecting legitimate plist files belonging to the Cocktail software, which are exhibiting the same behavior. We'll investigate and see wha
  11. Malwarebytes for Mac does indeed detect the OSAMiner components described by Sentinel One. We did notice that the scripts from Sentinel One's write-up were fairly old and don't all seem to actually be functional at this point. We added detection anyway, just to be on the safe side, keying on behaviors that we suspect should be in newer versions of the malware. We're also actively searching for newer variants, and will update the rules as needed.
  12. Thanks for the feedback! The problem with changing the name is that there can be multiple content blockers, from multiple different apps, and there needs to be some differentiator. The icon may not be enough, as users new to Malwarebytes may not recognize it. (We've definitely noticed that less tech-savvy users often have difficulty identifying apps by icon only.) We actually struggled with this decision for a while before settling on this one... it's not ideal, but it's the option that works best for the largest number of users.
  13. If you do not have access to the iOS beta, please request access by sending me a direct message and I'll get you invited. To participate in the iOS beta, you will need: An iOS device (iPhone, iPad, or iPod Touch) running iOS 13.0 or higher A copy of the TestFlight app on that device, downloaded from the App Store A Privacy license key We will provide you with a time-limited key for testing the beta, though you can also use your own Privacy key if you already have one Reporting issues Before you install, be sure to familiarize yourself with the list o
  14. If you find an issue with the beta, first make sure that the issue you're reporting is not on the list of known issues. If it is not already known, please post a new topic on this forum. In your post, make sure to include: A description of the issue Screenshots of the issue, especially error messages (if possible) Version of iOS Steps to reproduce the issue Is the issue reliably reproducible? Making sure that diagnostic mode is enabled in advance (in the app's settings) will also help, in case we need to request logs. Thank you for your assistance!
  15. The following are known issues with the Malwarebytes Privacy for iOS beta: VPN connection may occasionally drop Internet may occasionally drop when VPN is on, with loss of network access iPhone SE: after switching between tabs some UI issues may occur. Forcing the app close and re-opening it can be used as a workaround
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.