search for: voipabus

...ave the time to post them all. So for now, posting VoIP Abuse addresses straight to Twitter. So, anyone trying to compromise a pbx, is now autoposted on an hourly basis to Twitter. Still working on pulling, have about 4 machines linked up now, will mop em up during the week. http://twitter.com/#!/voipabuse Now, you can concoct a quick script off of it, e.g.: links -dump "http://twitter.com/voipabuse"|awk '/attacker/{print "iptables -A INPUT -s "$2" -j DROP"| "sort -u"}' Will get a quickie soon from my Acme's, nCites, etc. when I have time. For...

...ith mobile phone theft in the UK a few years back - stories abounded with tales of rooms full of mobiles, calling premium rate numbers belonging to the thieves, and so on) Anyway, SV is easy to thwart with good practices and tools like fail2ban, svcrash.py, sites like http://www.infiltrated.net/voipabuse/ and so on. As far as I'm concerned, it's history. It's understood and with a few simple procedures we can protect ourselves against it. It's yesterdays news. Why are we still bleating on about it? Gordon

Hi, Given the recent increase in SIP brute force attacks, I've had a little idea. The standard scripts that block after X attempts work well to prevent you actually being compromised, but once you've been 'found' then the attempts seem to keep coming for quite some time. Older versions of sipvicious don't appear to stop once you start sending un-reachables (or straight