Top Banner
Case study #siwa Botnet Panel
24

Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

Mar 31, 2015

Download

Documents

Dandre Winters
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

Case study #siwa

Botnet Panel

Page 2: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

The #siwa botnet

• IRC Botnet monitored for 5 months (+/-)

• The name “#siwa” comes from the irc channel used by the involved malwares

Page 3: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

Some IRC backround

• IRC channels are moderated by channel operators• Chan OPs (@nick) have the rights to – give the @ to other users– change the channel topic– kick/ban people from the channel– etc

• The command +M (moderated) stands for only registered nicks (or @operatos) may talk in that channel.

Page 4: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

The Dorothy-Drone Log file

Page 5: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

0.2 cents Investigation

• Only operators can chage channel settings by use the MODE command. – lets grep “MODE” to see who are the operators

• Ok now we have the Operators (OPs), lets grep them to see what they said

Page 6: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

• 72.10.169.26:2293 --> :[email protected] MODE #siwa +o abc• 72.10.169.26:2293 --> :[email protected] MODE #siwa –M• 72.10.169.26:2293 --> :[email protected] MODE #siwa +o Burimi• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :u seee us eee• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :lol !• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :bots joining• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :.oper• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :i cant se bots• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :oper• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :d• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :d• 72.10.169.26:2293 --> :[email protected] MODE #siwa +o resit• 72.10.169.26:2293 --> :[email protected] MODE #siwa +o Burimi• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :4% join

#testing• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :4% join #testing• 72.10.169.26:2293 --> :[email protected] MODE #siwa +M

Page 7: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

• 72.10.169.26:2293 --> :[email protected] MODE #siwa +o abc• 72.10.169.26:2293 --> :[email protected] MODE #siwa –M

• 72.10.169.26:2293 --> :[email protected] MODE #siwa +o Burimi• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :u seee us eee

• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :lol !

• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :bots joining• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :.oper• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :i cant se bots• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :oper• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :d

• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :d

• 72.10.169.26:2293 --> :[email protected] MODE #siwa +o resit• 72.10.169.26:2293 --> :[email protected] MODE #siwa +o Burimi• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :4% join #testing• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :4% join #testing• 72.10.169.26:2293 --> :[email protected] MODE #siwa +M

Page 8: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

• 72.10.169.26:2293 --> :[email protected] MODE #siwa +o abc• 72.10.169.26:2293 --> :[email protected] MODE #siwa –M• 72.10.169.26:2293 --> :[email protected] MODE #siwa +o Burimi

• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :u seee us eee• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :lol !• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :bots

joining• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :.oper• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :i cant

se bots• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :oper• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :d• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :d• 72.10.169.26:2293 --> :[email protected] MODE #siwa +o resit• 72.10.169.26:2293 --> :[email protected] MODE #siwa +o Burimi• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :4% join #testing• 72.10.169.26:2293 --> :[email protected] PRIVMSG #siwa :4% join #testing• 72.10.169.26:2293 --> :[email protected] MODE #siwa +M

Page 9: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

:abc: u seee us eee:Burimi: lol !:Burimi: bots joining:Burimi!: .oper:Burimi!: i cant se bots:Burimi!: oper:Burimi!: d

Page 10: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

speculations

• It sounds like a customer service.....doesn’t it?

Page 11: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

something more?

• Lets see what happens when the moderation was removed ( MODE –M)

Page 12: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

Lets say...

• The string look likes :– ({IRCHOST} PRIVMSG #siwa :-04dcom2.04c- 3.

Raw transfer to {IPADDRESS} )• Buffer Overrun In RPC Interface Could Allow

Code Execution (MS03-026)• So in human gergon, it could mean that – {IRCHOST} has infected {IPADDRESS}

Page 13: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

Lets say...

• So in human gergon, it could mean that – {IRCHOST} has infected {IPADDRESS}– {IRCHOST} = :[email protected]

{NICK} ! ~ {USERHOST} @{HOSTNAME}

• By RFC, every irc userhost has to be UNIQUE– We could enumerate how many UNIQUE host are

infected

Page 14: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

Bonus (!?)

• Take a look at this line:• :[email protected] PRIVMSG #siwa :4%

join #testing– resit is the nickname of the Operator– admin.siwatech.com is its host name– ....SIWAtech.com !

• yes, the label that I used for this botnet! curious

– The timestamp of this command is “06/02/2009-20:53:54”– ...and the website is still reachable! (02/2011)

Page 15: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

The #siwa botnet

Page 16: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

#siwa C&C on the map

Page 17: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

Conclusions

• Botnet masters were conscious that someone was “spying” into their botnet.

Page 18: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

Conclusions

• Botnet masters were conscious that someone was “spying” into their botnet.– botmasters are not stupid.

Page 19: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

Conclusions

• Botnet masters were conscious that someone was “spying” into their botnet.– botmasters are not stupid.

• We saw only what they wanted to show us

Page 20: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

Conclusions

• Botnet masters were conscious that someone was “spying” into their botnet.– botmasters are not stupid.

• We saw only what they wanted to show us– could this information be reliable?

Page 21: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

Conclusions

• Botnet masters were conscious that someone was “spying” into their botnet.– botmasters are not stupid.

• We saw only what they wanted to show us– could this information be reliable? – Why they chose to show their botnet populations?• to show us their p0w3r?

Page 22: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

Conclusions

• Botnet masters were conscious that someone was “spying” into their botnet.– botmasters are not stupid.

• We saw only what they wanted to show us– could this information be reliable? – Why they chose to show their botnet populations?• to show us their p0w4h?• ...or just to deceive us?

Page 23: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

Conclusions

• Botnet masters were conscious that someone was “spying” into their botnet.– botmasters are not stupid.

• We saw only what they wanted to show us– could this information be reliable? – Why they chose to show their botnet populations?

• to show us their p0w3r?• ...or just to deceive us?

• We should be careful with conclusions...

Page 24: Case study #siwa Botnet Panel. The #siwa botnet IRC Botnet monitored for 5 months (+/-) The name #siwa comes from the irc channel used by the involved.

References

• My Bachelor Thesis –Pg. 89– http://www.honeynet.it/wp-content/uploads/

Dorothy/The_Dorothy_Project.pdf

• All the data are still available and are accessible to the Dorothy WGUI– send me an email for an account– [email protected]