Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

Source Code For SpyEye Trojan Published; More Exploits On The Horizon, Researcher Says

Once costly code for data-stealing Trojan is now available to the masses, 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.

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 says.

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 observes. Now, with the crack, the kit is being sold inexpensively on hacker forums.

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

Perhaps just as important, the "crack" enables malware developers to avoid the attribution that was previously associated with the high-priced toolkit, Bodmer states. 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 says.

"This will make it more difficult to track SpyEye botnets back to the source," Bodmer says.

SpyEye, which incorporated elements of the popular Zeus Trojan earlier this year, was already ranked as one of the top three threats on the Web this year, Bodmer says, infecting some 2 million devices. "Now I expect that number to climb," he says, possibly even displacing TDL and rogue antivirus threats, which occupy the other two spots in the top three.

"SpyEye has been on everyone’s priority list of threat discussions for quite some time, and is now going to become an even more pervasive threat," Bodmer says. "The same thing happened when the Zeus kit source code was released in March 2011.

"Damballa Labs has been tracking dozens of new Zeus bot operators since the leak earlier this year -- and now that SpyEye has been outed, it is only a matter of time before this becomes a much larger malware threat than any we have seen to date," the blog states. "So for the next few months, please hold onto your seats people… this ride is about to get very interesting."

Have a comment on this story? Please click "Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message. Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
How to Better Secure Your Microsoft 365 Environment
Kelly Sheridan, Staff Editor, Dark Reading,  1/25/2021
Attackers Leave Stolen Credentials Searchable on Google
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-3142
PUBLISHED: 2021-01-28
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2020-35128. Reason: This candidate is a reservation duplicate of CVE-2020-35128. Notes: All CVE users should reference CVE-2020-35128 instead of this candidate. All references and descriptions in this candidate have been removed to preve...
CVE-2020-35124
PUBLISHED: 2021-01-28
A cross-site scripting (XSS) vulnerability in the assets component of Mautic before 3.2.4 allows remote attackers to inject executable JavaScript through the Referer header of asset downloads.
CVE-2020-25782
PUBLISHED: 2021-01-28
An issue was discovered on Accfly Wireless Security IR Camera 720P System with software versions v3.10.73 through v4.15.77. There is an unauthenticated stack-based buffer overflow in the function CNetClientManage::ServerIP_Proto_Set during incoming message handling.
CVE-2020-25783
PUBLISHED: 2021-01-28
An issue was discovered on Accfly Wireless Security IR Camera System 720P with software versions v3.10.73 through v4.15.77. There is an unauthenticated heap-based buffer overflow in the function CNetClientTalk::OprMsg during incoming message handling.
CVE-2020-25784
PUBLISHED: 2021-01-28
An issue was discovered on Accfly Wireless Security IR Camera System 720P with software versions v3.10.73 through v4.15.77. There is an unauthenticated stack-based buffer overflow in the function CNetClientGuard::SubOprMsg during incoming message handling.