There has been an increase in the number of Asterisk IP PBX's being hacked for the purposes of placing free phone calls via those hacked IP PBX's and in turn through the VoIP account that is used from that IP PBX, causing customers' accounts to be charged without their knowledge.


Please note that NeuTrafiX is not responsible for preventing unwanted physical or remote access to your Asterisk IP PBX. If your Asterisk IP PBX is compromised then you will be responsible for any damage caused.


The compromise of the IP PBX's we have seen all appear to have been caused by these common issues:


  1. The IP PBX not being fire-walled, and being open to the entire Internet for extensions on that IP PBX to register to it.
  2. Weak passwords on the IP PBX's extensions allowed automated brute force attacks to find the password for 1 or more extensions.
  3. We've seen an increase of this with our own customers, anecdotal evidence of it happening more frequently at some of our competitors, as well as anecdotal evidence of automated bot-nets being used to locate and automatically attempt to hack IP PBX's.
  4. Asterisks has throttling mechanism to limit the number of auto-recharge transactions and loss to a customer that can occur on an account if a customer's equipment/software should be compromised, but for the security of your Asterisk IP PBX server; we recommend you the following changes;
  5. Change the 5060 default sip port of your server to a different one and make sure to configure the extension clients accordingly as well.
  6. If you don't have any remote extensions, allow access to your servers for local user extensions only. You can find here ( an example to limit SIP traffic to and from a peer to a certain IP or network.
  7. If you have remote extensions, change the passwords with stronger passwords for these extensions.
  8. If you are an advanced user, use tools to protect your server from random password attacks like Fail2Ban. Fail2ban scans log files and ban IP addresses that make repeated, unsuccessful password attempts.
  9. Update your server to the latest version for security fixes.