Since our previous blog post, we continued to investigate whether or not SpyEye 1.3.x is indeed the result of the ZeuS-SpyEye merger. So far, we realized that the included documentation doesn’t say much about ZeuS. It only compared the behaviors of several options/configurations of the two malware families.
At present, we have only been able to identify three different versions in the wild:
- 1.3.04
- 1.3.05
- 1.3.09
As you can see, these versions are minor releases. Our underground research tells us that some minor bug fixes have been made in these versions though these are typically the same. If you are wondering if the SpyEye Toolkit comes with three control panels (two SpyEye control panels [CN1 and SYN1] and one ZeuS control panel), I can confirm that it does not do so. It only comes with the regular two SpyEye control panels. The database structures of SpyEye and ZeuS were different prior to 1.3.x and are still so. As such, a modification of the ZeuS panel is needed so both can share a single database. ZeuS and SpyEye malware are thus not registering themselves to the same control-and-command (C&C) server in the same way.
The SpyEye 1.3.x binary still behaves like previous SpyEye versions. The call-home request remains the same, except for the communication mode shown below.
[domain_name]/[folder]/gate.php?guid=5.1.2600[computer_name]&ver=10305&ie=6.0.2900.2180&os=
5.1.2600&ut=Admin&ccrc=88CFDFC7&md5=273c725a57e35b1e263d4f1
8fe21c5c7&plg=customconnector;mngr1_1&stat=online
The customconnector plug-in tells the bot which C&C server to communicate with. This plug-in was likely offered so cybercriminals can have several C&C servers listed for backup. In previous versions, this was not included in a plug-in but was part of a file named maincps.txt, which was part of the config file.
Obtaining the new version of SpyEye also differs from getting previous versions. You first get an email with a set of instructions. This is a form of two-factor authentication from the author. The email requires the interested party to send the nickname and email address he used to purchase SpyEye via Jabber. After sending this information, the SpyEye creator then sends the buyer a message that contains download links.
Several links are sent from which the buyer can download the different components of the toolkit. The following components have been uploaded to a free hosting site, each of which has been protected with a very strong password:
- !default pack.7z: Contains the main control panel (CN1), the builder, three plug-ins (bugreport, customconnector, and webfakes), and the documentation in Russian.
- Sedeb.7z: A .vdi file (VirtualBox). This is a Linux Debian system that has the formgrabber panel (SYN 1) installed for testing.
- !socks pack.7z: Contains a SOCKS 5 plug-in.
- !ftp pack.7z: Contains an FTP plug-in.
- !ffcertgrabber pack.7z: Contains a Firefox certificate grabber plug-in.
- !ccgrabber pack.7z: Contains a CC grabber plug-in.
![]() |
![]() |
While the SpyEye changes may be minor, the way Gribodemon communicates with his clients has drastically changed. He no longer communicates much through ICQ and prefers Jabber. He also talks less and has become more secretive. The changes in his behavior are probably due to how much press SpyEye is now getting. SpyEye has changed and evolved to adapt to the security industry, along with its author’s behavior.
With added text from senior threat researcher Kevin Stevens.
Post from: TrendLabs | Malware Blog – by Trend Micro
SpyEye/ZeuS Toolkit v1.3.05 Beta Part 2
![]()


In the third and final part of my series on OS X security I will cover system security. If you missed out previous articles, check out part one on
The second part to the firewall solution in OS X is ipfw, a packet filtering firewall that is built into the sub-system of OS X. Ipfw is immensely powerful, but can be confusing to a lot of people. It is hidden away from most users unless you go looking for it in terminal.
Many users have services running on their systems that they either rarely use, or, more often than not, dont even know are running.










This is a little inconvenient but means that anyone that cracks your account password doesn’t get instant access to everything in your Keychain, and that you will know whenever an application is trying to gain access to your secured data.
If you talk to any Linux or Unix user you will quickly find out that they rarely login as a user that has administrative privileges. The reason for this? If your account is compromised, the attacker has only gained access to your data, but hasn’t gained access to the entire system.


On the street, you can spot a smartphone user at a hundred paces. They stumble along hesitantly, echoing the drunkard shuffle. Rather than sporting a vacant inebriated look, “smartphoners” stare at their hands with possessed concentration, their fingers flying about a tiny screen at lightning speed.
And to thank you for your efforts, we are giving away five very exclusive, very desirable (let’s be honest, very sexy) Naked Security t-shirts.







