msherwood

Administrators
  • Content count

    625
  • Joined

  • Last visited

3 Followers

About msherwood

  • Rank
    Staff

Contact Methods

  • Website URL
    https://twitter.com/michaelsherwood

Profile Information

  • Location
    SJC ✈️ TBD

Recent Profile Visitors

3,504 profile views
  1. With the 4.1.19 update, Malwarebytes Staff signatures were broken. To fix, please do the following: Go here: https://forums.malwarebytes.com/settings/?area=signature Remove old sig Paste: https://www.malwarebytes.com/images/staff.png Press Ctrl + right-click on MB staff image, Edit image In the Link URL field, paste: https://www.malwarebytes.com/ Click update, then save This has been fixed. If you're still seeing this, force refresh the page.
  2. You're too fast!
  3. 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!
  4. Got it, thanks.
  5. @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?
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. Yep, all related. We've been actively working with IPS all day.
  11. Thanks @Aura and @David H. Lipman. We've shared all of the above with IPS.
  12. We are tracking this but need your help. If you're seeing any types of slow downs, please share the link and what you were doing (e.g. searching "malware stuff", browsing a specific section) here.
  13. Closing this per our PM conversation. Result: @att.net addresses are currently not receiving emails from us. He's going to stick with @outlook.com for now.
  14. I sent a new test directly from me. Please respond to that.
  15. I just sent you a test email. I also edited your post so your email isn't public.