Eric.freyssinet: Created page with "{{Publication |Botnet=Jabberbot, |CCProtocol=XMPP, |Year=2013 |Date=2013-01-30 |Editor=ESET |Link=http://www.welivesecurity.com/2013/01/30/walking-through-win32jabberbot-a-ins..."

2015-08-03T14:30:39Z

Created page with "{{Publication |Botnet=Jabberbot, |CCProtocol=XMPP, |Year=2013 |Date=2013-01-30 |Editor=ESET |Link=http://www.welivesecurity.com/2013/01/30/walking-through-win32jabberbot-a-ins..."

New page

{{Publication
|Botnet=Jabberbot,
|CCProtocol=XMPP,
|Year=2013
|Date=2013-01-30
|Editor=ESET
|Link=http://www.welivesecurity.com/2013/01/30/walking-through-win32jabberbot-a-instant-messaging-cc/
|Author=Alexis Dorais-Joncas,
|Type=Blogpost
|Abstract=Malware authors have a solid track record in regards to creative Command and Control protocols. We’ve seen peer-to-peer protocols, some custom (Sality), some standard (Win32/Storm uses the eDonkey P2P protocol). We’ve seen binary protocols (Win32/Peerfrag, aka Palevo). We’ve seen other custom protocols that leverage other standard protocols such as HTTP (Win32/Georbot), DNS (Morto) and IRC (Win32/AutoRun.IRCBot.AK). Others have leveraged popular web services such as Twitter (OSX/Flashback).
This analysis focuses on Win32/Jabberbot.A, a piece of malicious code that uses a different kind of protocol: theExtensible Messaging and Presence Protocol (XMPP), a protocol for instant messaging that is commonly known as the Jabber protocol.
}}

Walking through Win32/Jabberbot.A instant messaging C&C - Revision history

Eric.freyssinet: Created page with "{{Publication |Botnet=Jabberbot, |CCProtocol=XMPP, |Year=2013 |Date=2013-01-30 |Editor=ESET |Link=http://www.welivesecurity.com/2013/01/30/walking-through-win32jabberbot-a-ins..."