<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.botnets.fr/index.php?action=history&amp;feed=atom&amp;title=It%E2%80%99s_2012_and_Armageddon_has_arrived</id>
	<title>It’s 2012 and Armageddon has arrived - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://www.botnets.fr/index.php?action=history&amp;feed=atom&amp;title=It%E2%80%99s_2012_and_Armageddon_has_arrived"/>
	<link rel="alternate" type="text/html" href="https://www.botnets.fr/index.php?title=It%E2%80%99s_2012_and_Armageddon_has_arrived&amp;action=history"/>
	<updated>2026-10-23T22:12:27Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.11</generator>
	<entry>
		<id>https://www.botnets.fr/index.php?title=It%E2%80%99s_2012_and_Armageddon_has_arrived&amp;diff=2051&amp;oldid=prev</id>
		<title>Eric.freyssinet: 1 revision imported</title>
		<link rel="alternate" type="text/html" href="https://www.botnets.fr/index.php?title=It%E2%80%99s_2012_and_Armageddon_has_arrived&amp;diff=2051&amp;oldid=prev"/>
		<updated>2015-02-07T14:23:40Z</updated>

		<summary type="html">&lt;p&gt;1 revision imported&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{Publication&lt;br /&gt;
|Image=&lt;br /&gt;
|Legend=&lt;br /&gt;
|Document=&lt;br /&gt;
|Licence=&lt;br /&gt;
|Video=&lt;br /&gt;
|Link=http://ddos.arbornetworks.com/uploads/2012/03/Crypto-Armageddon-Blog.pdf arbornetworks.com (pdf)&lt;br /&gt;
|Author=Jeff Edwards, &lt;br /&gt;
|NomRevue=&lt;br /&gt;
|Date=March 6th 2012&lt;br /&gt;
|Editor=Arbor SERT&lt;br /&gt;
|Year=2012&lt;br /&gt;
|ISBN=&lt;br /&gt;
|Page=&lt;br /&gt;
|Abstract=Jeff Edwards, Research Analyst, Arbor Networks ASERT&lt;br /&gt;
Armageddon is one of several notable Russian malware families that are designed exclusively for DDoS attacks; it has &lt;br /&gt;
been on our radar screens for some time now.  Its primary competitors within the market of Russian DDoS vendors are Dirt &lt;br /&gt;
Jumper (a.k.a. RussKill), Darkness/Optima (a.k.a. Votwup), and ofcourse BlackEnergy.&lt;br /&gt;
We&amp;#039;ve noticed that the Armageddon code base has undergone some relatively rapid evolution lately, and the purpose of this &lt;br /&gt;
blog post is to report on some of the new functionality we have observed.  With this latest release, the bot uses some new &lt;br /&gt;
crypto protection to hide its features from casual observers; breaking this encryption revealed some interesting goodies...Arbor Networks  |  2&lt;br /&gt;
This paper is also intended to be the first in an upcoming series of articles that will provide a guided tour of the inner &lt;br /&gt;
workings of various crypto systems that are used by contemporary DDoS malware families in order to hide their &lt;br /&gt;
communications and sensitive data - and how to go about breaking them.&lt;br /&gt;
Breaking Armageddon&amp;#039;s Crypto&lt;br /&gt;
We use IDA Pro as our primary reversing tool, but since Armageddon is written in Delphi, we supplement IDA with the &lt;br /&gt;
excellent Interactive Delphi Reconstructor (IDR) tool.  IDR often does a pretty good job at automatically detecting &lt;br /&gt;
many/most of the classes, properties, and methods included in the various versions of the Delphi application framework.  It &lt;br /&gt;
also tends to work well for common third-party libraries such as the Synapse package that is often used by Delphi-based &lt;br /&gt;
malware to perform network operations, such as phoning home to command &amp;amp; control (C&amp;amp;C) servers, generating DDoS &lt;br /&gt;
flood traffic, etc.  One can often minimize the amount of time wasted digging through layer upon layer of Delphi function &lt;br /&gt;
calls by simultaneously opening the malware in both IDA and IDR, and using IDR as a reference to identify Delphi &lt;br /&gt;
functions, while doing the bulk of the analysis in IDA.&lt;br /&gt;
The sample bot that we will analyze in this post is 45,056 bytes in size with MD5 hash of &lt;br /&gt;
5ae3451b76c76c20e6fe58289bb8302c.  As usual, a great place to start the reversing of a bot is to run a strings&lt;br /&gt;
dump on the executable and identify any interesting clues therein.  Applying this approach to our Armageddon sample does &lt;br /&gt;
not yield much at first glance, except for about 45 strings that appear to be encrypted in some fashion; here are some &lt;br /&gt;
examples:&lt;br /&gt;
70D997203F8AD33CE175FA6CF7D5396A0739D0E8487BCE4568B40BAC92A1BE&lt;br /&gt;
A405ED14624D0D3258D403EC8ABD56B548961379C7&lt;br /&gt;
9B7AEB04381B284D43CF45B5&lt;br /&gt;
Earlier versions of Armageddon bots stored most of their sensitive strings in plain ASCII; this encryption is a new &lt;br /&gt;
development.  So it seems we must first reverse this crypto before the inner workings of the bot are revealed.&lt;br /&gt;
|Botnet=, &lt;br /&gt;
|Malware=Armageddon, Dirt Jumper, Darkness, BlackEnergy, &lt;br /&gt;
|CCProtocol=, &lt;br /&gt;
|Operation=, &lt;br /&gt;
|Keyword=Ddos, Reverse Engineering, &lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Eric.freyssinet</name></author>
	</entry>
</feed>