Jump to content


  • Content Count

  • Joined

Everything posted by msherwood

  1. This is something different as @ksiemb posted before we did the upgrade. @ksiemb - can you further explain what you're experiencing and where exactly?
  2. We've completed the upgrade to Invision Community 4.2! If you come across any issues, please check the Known Issues & Workaround thread or post a new issue here.
  3. We are still on track for the Invision Community 4.2 update tomorrow morning (Monday, August 7). We are targeting downtime starting at 8a PDT and this will last ~15-30 minutes as we test and verify the update. We'll post info here once it's been completed and we're fully back online.
  4. Hi @whereisthesupport. Sorry to hear about your issues. We'd love a chance to make this right. Our Business Support team will be in touch very shortly on this.
  5. Hi @rawrabbit. Thanks for posting your concerns and feedback. Please know our Legal team is reviewing your inquiry and will get back to you early next week.
  6. UPDATE 6/29/2017 1045 PST: According to information uncovered within Malwarebytes Labs, we have determined that this ransomware variant is coded to erase a unique and randomly generated key that is used to encrypt the MFT (Master File Table). The destruction of the Salsa20 key makes it very unlikely that users can receive a working decryption key – even after paying the attackers ransom demands. For this reason, we warn any infected user who may be considering paying the ransom to beware. We have created a new entry on the Malwarebytes blog with the newly discovered information: EternalPetya
  7. Hi everyone. If you're experiencing today's issue of Web Protection being off and/or Malwarebytes not being able to perform a scan, we have pushed Update Package 1.0.1976 to resolve this. In some cases, an additional step of either rebooting the machine or just Malwarebytes is needed. If you're experiencing a different issue, please check out the Malwarebytes 3 section (here) and/or post a new thread with your issue (here). Edit: more information on the issue (here).
  8. Welcome to our community, @AtariBaby. Appreciate the feedback and information. On your first concern about our customer database and forum email addresses being compromised: at this time we are not aware of any breaches. For your reference, we did experience a breach in Nov 2014 (here) - it was a single server running the forums at that time. We took a precautionary step of issuing password resets to all users. We also moved the hosting of the forums to IPS (who did, and still does, provide the forums software). Separately and not related to our systems, one way your email could have
  9. We're super excited to announce availability of an update to both our MB-Check and MB-Clean utilities. For MB-Check, we've updated this to included both support for the latest Malwarebytes 3.1 as well as the ability to automatically collect log files. For MB-Clean, this has also been updated to support the latest Malwarebytes 3.1 as well as some other sweet enhancements. See above to get the latest versions as well as the detailed changelogs: MB-Check | MB-Clean
  10. Per your request, we've removed your account.
  11. Hi everyone, Here at Malwarebytes, your security is always our top priority. With the new features added in our forum software provider’s release (here), we will be implementing an enhanced password requirement for the Malwarebytes Forums.This change will affect both new users signing up to our forums and any users who update their password after today. We encourage all to adhere to this new policy. Passwords will be required to be “Strong” and there will be a password meter to guide you to this strength level. Per IPS, “The strength of a password is calculated using an alg
  12. We just pushed a new version (8.1.3): https://forums.malwarebytes.com/topic/199226-junkware-removal-tool-jrt-813-released/ Direct: https://downloads.malwarebytes.com/file/jrt/ @nukecad - let us know how it's working for you!
  13. We've got the build updated and it's with QA now. We're targeting the deployment of this new build within 24 hours. Again, if you're seeing this issue simply reboot your machine.
  14. We've figured this out. We're terminating "fontdrvhost" and that's causing the issues you're seeing. How to fix: reboot your system. We're working on an updated build and we'll publish that ASAP. Thanks again for the bug report!
  15. Hey @nukecad. We're still troubleshooting this one. We'll be in touch soon.
  16. As you may have noticed, the forums was down for a few hours today. Just as many other sites and services around the net, our forums provider (Invision Power Services) was also affected by the Amazon AWS outage. Read more about the AWS outage and see AWS Service Health Dashboard here. We're back in business!
  17. @David H. Lipman from IPS... Which theme is the user using? What screen resolution are they viewing the site with? Which browser are they using?
  18. Thanks for this, @David H. Lipman. We've got a couple of items open with IPS around the editor and posting right now. We'll add this to discussion.
  19. The post is locked so we can more easily keep track of and respond to individual feedback. Feel free to start a new thread and post your 3.0.6 findings within the Malwarebytes 3.0 forum.
  20. Hello @Confuzzled. Yahoo!'s two-factor authentication (2FA) codes can come from (408) 610-4900 (voice) as well as 837-401 (text). The scammers most likely spoofed the (408) 610-4900 number in an attempt to make you think it was Yahoo! I'm not sure what the 2FA phone number was pre Dec 15, 2016. Today it's what I just shared.
  21. We're aware and working with IPS on this. No planned updates. We'll share more information once we hear back from IPS and have this resolved. Locking this one.
  22. Yep, all related. We've been actively working with IPS all day.
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.