"We found that almost 60% of the UDP packets are sent towards the IP address 188.8.131.52 on port 15206 which makes up the largest amount of packets seen by our RRC. Most of these packets start their data section with 0x80, continue with seemingly random data and are padded to 172 bytes with an (again seemingly random) 2 byte value. Some sources (http://www.proxyblind.org/trojan.shtml) list the port as being used by a trojan called "KiLo", however information about it seem sparse."
I think I have an answer to that. Its not a trojan. On the SIP front we've been seeing some INVITE scans which start an RTP stream to IP 184.108.40.206 and port 15206. In fact RTP streams start with 0x80. Enough talk, lets take a look at a sample SIP message from these INVITE scans:
INVITE sip:email@example.com SIP/2.0
Via: SIP/2.0/UDP 220.127.116.11:3058;branch=ca4b60ae7ba821fREPLACEDjrgrg;rport
CSeq: 102 INVITE
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
o=sip 2147483647 1 IN IP4 18.104.22.168
c=IN IP4 22.214.171.124
m=audio 15206 RTP/AVP 10 4 3 0 8 112 5 7 18 111 101
a=silenceSupp:off - - - -
So what does this mean? According to the article, almost 60% of the traffic being sent to 126.96.36.199 consists of these RTP streams. The majority of the traffic is sent to 188.8.131.52 and is UDP traffic, meaning that the majority of Internet traffic being sent to the 1.1.1/24 is in fact RTP traffic generated by these scans.
The impression that I'm getting is that there's a lot of such INVITE scanning going on, and a large number of SIP entities on the Internet are responding to these scans by starting an RTP stream.
Sjur posted his analysis of this on his blog too.