Jump to content

Malwarebytes

Broken.SecurityProviders


3 replies to this topic

#1
JJJ

    New Member

  • Members
  • Pip
  • 2 posts
Good morning. I just updated to release 1.29 and ran MB. It identified one infection titled Broken.SecurityProviders that affected the Registry Data.

A previous post indicates that this is not a true infection but, instead, a correction to the underlying script. MalwareNet indicates that it is an infection. Can you help me determine:

- which of these two it is? And,

- if it is an infection, what kind of damage could it have done?

Thanx. --John

#2
Tigger93

    Forum Deity

  • Moderators
  • PipPipPipPipPipPip
  • 1,648 posts
  • Gender:Male
MalwareNET really doesn't list it as malware, however it probably shouldn't be listed there. It's not an infection, just fixing a key that was incorrectly set in a previous version of MBAM.

#3
JJJ

    New Member

  • Members
  • Pip
  • 2 posts
That's a relief! Thanx for the help TIgger 93!

#4
JeanInMontana

    Delete this account!!

  • Honorary Members
  • PipPipPipPipPipPip
  • 3,867 posts
  • Interests:would love to see some honesty around this site.

View PostJJJ, on Oct 19 2008, 08:34 AM, said:

Good morning. I just updated to release 1.29 and ran MB. It identified one infection titled Broken.SecurityProviders that affected the Registry Data.

A previous post indicates that this is not a true infection but, instead, a correction to the underlying script. MalwareNet indicates that it is an infection. Can you help me determine:

- which of these two it is? And,

- if it is an infection, what kind of damage could it have done?

Thanx. --John


It is not an infection and never was, however you should allow MBAM to repair it. There was a broken protection in the earlier version of MBAM and this fixes that.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users

Follow Us