SpyEye Trojan Source Code Published

Once costly code for data-stealing Trojan is now available to the masses; exploits expected to rise, Damballa reports.

The source code for SpyEye, an infamous data-stealing Trojan, has been published on the Web and could easily be adapted and used by any savvy cybercriminal with virtually no cost or chance of getting caught, a researcher said Monday.

"One of the most dangerous Swiss Army knives in malware is now available to billions," said Sean Bodmer, senior threat intelligence analyst at security vendor Damballa.


More Security Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

According to a blog posted by Bodmer on the Damballa website, the SpyEye builder patch source code (release 1.3.45) was leaked by French security researcher Xyliton, part of the Reverse Engineers Dream (RED) Crew.

"He was able to locate a copy of SpyEye builder 1.3.45 and created a walkthrough/tutorial that enables the reader [once in possession of SpyEye builder] to crack the hardware identification [HWID] which has been secured using VMProtect, a licensing tool that locks an installation of software to a particular physical device," the blog said.

The SpyEye malware kit has been widely used in cyberspace for some time now, but it generally was sold at a price of around $10,000--not a price paid by the average script kiddie, Bodmer observed. Now, with the crack, the kit is being sold inexpensively on hacker forums.

"What this means is that anybody can use it," Bodmer said.

Perhaps just as important, the "crack" enables malware developers to avoid the attribution that was previously associated with the high-priced toolkit, Bodmer stated. Where previous exploits using the kit could often be traced back to the original buyer of the toolkit, there have already been some SpyEye exploits spotted that have no attribution, he said.

Read the rest of this article on Dark Reading.

Read our report on how to guard your systems from a SQL attack. Download the report now. (Free registration required.)


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS

Resource Links