Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah
-
@DustinB3403 said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
So I guess we're to assume that the lack of a response from @proteksupport means that something major is occurring with their client(s).
To be fair, this place is fast. They are not likely used to forums moving this quickly.
-
@scottalanmiller said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
@DustinB3403 said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
So I guess we're to assume that the lack of a response from @proteksupport means that something major is occurring with their client(s).
To be fair, this place is fast. They are not likely used to forums moving this quickly.
Fast compared to SpiteWorks, sure I suppose.
-
@DustinB3403 said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
@scottalanmiller said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
@DustinB3403 said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
So I guess we're to assume that the lack of a response from @proteksupport means that something major is occurring with their client(s).
To be fair, this place is fast. They are not likely used to forums moving this quickly.
Fast compared to SpiteWorks, sure I suppose.
MMm it depends what you are talking about.
-
@dbeato said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
@DustinB3403 said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
@scottalanmiller said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
@DustinB3403 said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
So I guess we're to assume that the lack of a response from @proteksupport means that something major is occurring with their client(s).
To be fair, this place is fast. They are not likely used to forums moving this quickly.
Fast compared to SpiteWorks, sure I suppose.
MMm it depends what you are talking about.
Fast response times.
Not so fast deleting comments made by people that SpiteWorks thinks that they can make money off of.
-
@DustinB3403 said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
@dbeato said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
@DustinB3403 said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
@scottalanmiller said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
@DustinB3403 said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
So I guess we're to assume that the lack of a response from @proteksupport means that something major is occurring with their client(s).
To be fair, this place is fast. They are not likely used to forums moving this quickly.
Fast compared to SpiteWorks, sure I suppose.
MMm it depends what you are talking about.
Fast response times.
Not so fast deleting comments made by people that SpiteWorks thinks that they can make money off of.
That's a different story, very few of my posts are moderated but I try to do as fast responses as I can. I barely have time to post on both places
-
Is there a public news article about this MSP or has one of their clients contacted you @scottalanmiller
-
@StuartJordan said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
Is there a public news article about this MSP or has one of their clients contacted you @scottalanmiller
The latter based on the OP.
-
@StuartJordan said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
Is there a public news article about this MSP or has one of their clients contacted you @scottalanmiller
This IS the public news article
Yes, we know about it first hand.
-
@scottalanmiller thanks for clarifying, I just looked at the op again..
"So we heard from customers of Protek Support" - I was skimming I must admit.
It is interesting that we only talked about this yesterday or the day before about that reddit link I posted.
-
@StuartJordan said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
@scottalanmiller thanks for clarifying, I just looked at the op again..
"So we heard from customers of Protek Support" - I was skimming I must admit.
It is interesting that we only talked about this yesterday or the day before about that reddit link I posted.
No kidding. Really weird that we were discussing it so recently.
-
@dbeato said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
I think that if it was VPN, still bad practice to have VPN from MSP or any other systems that unprotected. MSPs should not need to have VPN to customers at all.
And vendors wonder why I won’t let them VPN into my network.... ha
-
I Hope the MSP and client(s) manage to sort everything out. I can't help thinking this will be quite damaging for the provider and wouldn't like to see people loose clients and potentially their jobs.
Lessons are always learned when something serious happens like this though. -
@Dashrender said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
@dbeato said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
I think that if it was VPN, still bad practice to have VPN from MSP or any other systems that unprotected. MSPs should not need to have VPN to customers at all.
And vendors wonder why I won’t let them VPN into my network.... ha
Amen to that.
-
Looks like up until a few days ago they were really active on Twitter. And then went silent around when the supposed issue began.
https://twitter.com/proteksupport
Their last posts before going silent were all about security and avoiding things like ransomware.
-
@EddieJennings said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
@RojoLoco said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
@Reid-Cooper I would NEVER hire or even consider an MSP that paid a ransom. That means they are incapable or unwilling to make and test backups, so that's a hard no.
I've seen a situation where the ransomware ate most of the backups.
True, that is entirely possible... but the other part of paying the ransom is that you're really just painting a big bullseye on yourself. Once the bad guys know you will pay, the spearphishing will increase dramatically. I wouldn't hire an MSP that was a known ransom payer.
-
@RojoLoco said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
@EddieJennings said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
@RojoLoco said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
@Reid-Cooper I would NEVER hire or even consider an MSP that paid a ransom. That means they are incapable or unwilling to make and test backups, so that's a hard no.
I've seen a situation where the ransomware ate most of the backups.
True, that is entirely possible... but the other part of paying the ransom is that you're really just painting a big bullseye on yourself. Once the bad guys know you will pay, the spearphishing will increase dramatically. I wouldn't hire an MSP that was a known ransom payer.
Absolutely. Not only do you paint a target on yourself, but you justify the attack, and fund further attacks and research. It is bad all around.
Plus there is the huge risk that you pay and they don't release the files anyway.
-
Wonder if their RMM was the attack vector with that known ConnectWise / Kaseya depreciated integration?
-
@SmithErick said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
Wonder if their RMM was the attack vector with that known ConnectWise / Kaseya depreciated integration?
I would guess it is a decent chance.
-
Received my Cyberheist email from KnowBe4 about an hour ago and one article confirms that it was ConnectWise / Kaseya vulnerability from 2017 that was the vector.
-
@pmoncho said in Protek Support MSP Ransomware Hits Customers in Salt Lake City, Utah:
Received my Cyberheist email from KnowBe4 about an hour ago and one article confirms that it was ConnectWise / Kaseya vulnerability from 2017 that was the vector.
We had a thread about that last week here on ML. We know that ConnectWise had vulnerable DLLs on their Windows installs. But we don't know if that was the case here. But we do know that they advertise publicly that they use some ConnectWise stuff, so the chances are relatively high.
