ALERT VoIP.ms Accounts Compromised

[wardmundy]

You may recall that users reported accounts being compromised at VoIP.ms a number of years ago. Well, just a heads up. We've had sub-accounts there for more than a decade without an issue. And then this week two of them attempted to make foreign calls which we've had blocked. So... if you have old VoIP.ms subaccounts that you thought didn't get compromised by the earlier breach, think again.

FIX: Change ALL of your sub-account passwords. Where possible, add an IP address filter to each subaccount that requires a match with the PBX on which you have registered your trunk. Better yet, use IP address authentication and avoid the problem entirely.

 

[tbrummell]

I have International disabled as well, but I've created/deleted/created so many sub-accounts that my passwords have definitely been changed since the "breach". You know, the one that never happened. LoL And I also use IP filtering, so I'm covered, I hope.

 

[wardmundy]

Certainly appears that their entire database was compromised. Don’t recall ever getting an alert to change passwords until this attempt was made. Makes me think the database must be for sale somewhere.

 

[atsak]

Certainly appears that their entire database was compromised. Don’t recall ever getting an alert to change passwords until this attempt was made. Makes me think the database must be for sale somewhere.

Very likely, as I see the password I used to use there attempted across my SIP managed platforms from time to time and have for the last few years actually.

 

[billsimon]

FIX:

Better fix: be done with VoIP.ms. This is not the first major breach - not that you'd know it, since they refuse to acknowledge the previous one.

 

[tbrummell]

Better fix: be done with VoIP.ms. This is not the first major breach - not that you'd know it, since they refuse to acknowledge the previous one.

I wouldn't say it's a new breach, unless of course Ward never changed/re-created sub accounts since the 1st one happened. Which, given the wording of his post, he didn't...

 

[wardmundy]

Mine were the original main account and one of my oldest subaccounts.

 

[atsak]

Better fix: be done with VoIP.ms. This is not the first major breach - not that you'd know it, since they refuse to acknowledge the previous one.

If I dumped every service provider I had that had sercurity breaches I couldn't do anything, same for ones who don't ack the issues sometimes (hello Adobe). They are the only sub carrier who properly terminates Canadian Toll Free. You otherwise need the big guys with minimums and so on.