Latest Malware News

Spammers Promote Steve Jobs Bogus Charity Fund

Even after a few weeks following Steve Jobs’ death, spammers are still taking advantage of his demise. We have previously reported about this in the following blog entries:

This time, we received sample spammed messages promoting a supposed charity fund for young and gifted programmers and Web coders in honor of the late Apple co-founder.

Written in plain text, the said message aims to persuade recipients to donate funds to the account indicated in the mail. However, we discovered that it turns out to be an account for an online casino payment site.

Trend Micro strongly advises users to be wary of such messages and avoid disclosing important information to unknown websites. Readers may also refer to our blog entry A Refresher on Spam and Exploits to understand why basic mitigation practices with regard to spammed messages are still effective and can help them protect themselves from today’s threats.

If you're new here, you may want to subscribe to our RSS feed. Thanks for visiting!



Powered By WizardRSS.com | Full Text RSS Feed | Amazon Plugin | Settlement Statement

Ongoing analysis of the web infection

During the last couple of days I have together with Yury Namestnikov been investigating the extremely high numbers of infected websites. It all started when I was going through local statistics for Sweden and saw an increase of a certain JavaScript redirector, and also new detections on new variants for Java, PDF and Flash exploits. I published an article about this saying that Sweden was under attack, and you can read the blog post here:

http://www.securelist.com/en/blog/208193174/Sweden_is_under_attack_mass_infection_and_new_exploits

But after some more research I noticed that it was not just Sweden that was affected, it seemed to be a global epidemic. I also noticed that we were talking about two different redirectors; Trojan.JS.Redirector.ro and Trojan.JS.Pakes.cp.

Java Malware Reconsidered, or, Java Brews a Fresh Bot of Malware

At Virus Bulletin 2011, we presented on the exploding level of delivered Java exploits this year with "Firing the roast - Java is heating up again". We examined CVE-2010-0840 exploitation in detail, along with variants of its most common implementation on the web and some tools and tips for analysis. Microsoft’s security team presented findings for 2011 that mirrored ours in relation to Java exploit prevalence on the web - it is #1! At the same time, aside from the recent, well-known BEAST Java implementation, it is striking that it has been very uncommon to see Java backdoors, Trojans and spyware. But that lack of Java malware variety is beginning to change. My colleague, malware analyst Roman Unucheck, identified a new Java bot with some interesting characteristics that we named "Backdoor.Java.Racac".

The Mystery of Duqu: Part One

First of all, we feel it necessary to clarify some of the confusion surrounding the files and their names related to this incident. To get a full understanding of the situation you only need to know that we’re talking about just two malicious programs here (at a minimum) - the main module and a keylogger. All that has been mentioned in last 24 hours about connections between Duqu and Stuxnet is related mostly to the first one - the main module.

The main module consists of three components:

  • a driver that injects a DLL into system processes;
  • a DLL that has an additional module and works with the C&C; and
  • a configuration file.

The module is very similar to Stuxnet - both in structure and in behavior. However, the name Duqu has almost no connection with it. This name is based on the names of the files that are related to a completely different malicious spy-program!

This second malicious program, which is basically a keylogger (but is also able to collect other types of information) was discovered on the system of one of the victims together with the main module described above. Because of this fact, plus the main module’s ability to download other components, it was assumed that the main module and the keylogger were somehow related to each other. While working in a system, the keylogger stores collected data in files with names like ~DQx.tmp. So the name of the main module - Duqu - was given based on these files.

But actually, the code of the Trojan-Spy in part proves the connection between it and the main module, and it was probably downloaded by the main module sometime earlier. But as per its functionality, it is an independent malicious application able to work without the main module. At the same time, the main module is able to work without the Trojan-Spy. However, the connection between the keylogger and Stuxnet is not so obvious, and that’s why it’s possible - at a stretch - to perhaps call it a grandchild of Stuxnet, but certainly not its child :)

Duqu FAQ

This is an active investigation by Kaspersky Lab's Global Research & Analysis Team. We will be updating this FAQ document as necessary.

What exactly is Duqu? How is it related to Stuxnet?

Duqu is a sophisticated Trojan which seems to have been written by the same people who created the infamous Stuxnet worm. Its main purpose is to act as a backdoor into the system and facilitate the theft of private information. This is the main difference when compared to Stuxnet, which was created to conduct industrial sabotage. It's also important to point out that while Stuxnet is able to replicate from one computer to another using various mechanisms, Duqu is a Trojan that doesn't seem to replicate on its own.

Does this target any PLC/SCADA equipment? Exactly who/what are the targets? Do we know?

Unlike Stuxnet, Duqu doesn't target PLC/SCADA equipment directly, although some of its subroutines could be used to steal information related to industrial installations. It appears that Duqu was created in order to collect intelligence about its targets, which can include pretty much anything that is available in digital format on the victim’s PC.

How does Duqu infect computers? Can it spread via USB devices?

So far, we’ve only seen traces from infected systems, not the main replication component. It seems there is a dropper, “mothership” for Duqu, which infects the computers, however, we do not have a sample yet.

Is there any exploit, especially zero-day in Duqu?

So far, we haven't found any zero-day vulnerabilities attached to this malware, but the investigation continues. The malicious code is rather complex and the analysis is very-time consuming.

How did AV vendors become aware of this threat? Who reported it?

The first public mention that we are aware of is a blogpost from a Hungarian blogger, who seemed to be a victim of the attack. He later posted more information about the certificate used to sign the Duqu driver, however, he ended up deleting the respective posts.

When was this threat first spotted?

We’ve added detection for the main infostealer component on September 14th, as “Trojan.Win32.Inject.bjyg." Later, we found an earlier record of a sample on September 1, 2011.

How many variants of Duqu are there? Are there any major differences in the variants?

It appears that there are at least three variants of the Duqu drivers, together with a few other components. These are all detected with different names by various anti-virus companies, creating the impression that there are multiple different variants. At the time of writing, we are aware of one Infostealer component and three different drivers.

There is talk that this specifically targets Certificate Authorities. Is this true?

While there are indeed reports indicating that the main goal of Duqu is to steal information from CAs, there is no clear evidence at this time to support this claim.

Symantec says this is targeted to specific organizations, possibly with a view to collecting specific information that could be used for future attacks. What kinds of data are they looking for and what kinds of future attacks are possible?

One suspicion is that Duqu was used to steal certificates from CAs that can be used to sign malicious code in order to make it harder to catch. The functionality of the backdoor in Duqu is actually rather complex and it can be used for a lot more. Basically, it can steal everything.

Is the command-and-control server used by Duqu still active? What happens when an infected machine contacts the C&C?

The Duqu C&C server, which was hosted in India is no longer active. Just like in the case of Stuxnet, it was pulled offline pretty quickly once the news broke.

Why is Duqu configured to run for 36 days?

Maybe the author was a fan of round numbers, such as 6x6?

Who is behind this attack?

The same gang who was behind Stuxnet. Curiously, they seem to have picked up an interest in astronomy; the infostealer executable has a portion of a JPEG file picked up by the Hubble telescope (“Interacting Galaxy System NGC 6745”):

The picture portrays the aftermath of direct collision of two galaxies(!), several million of years ago. You can read the story here.

More to come...

* Research by Kaspersky Lab Global Research & Analysis Team.

Are "Offerwalls" siphoning your personal information?

A relatively new development in app advertising has a concerning feature. It leeches much of the same information that many Android Trojans also steal. Through an app promotion campaign, a new feature called “offerwalls” are used by Pay Per Install (PPI) services to promise further adoption and revenue for app developers. But what is the real danger? It is found in the way these services uniquely identify users and the information they collect.

Sweden is under attack - mass infection and new exploits!

Web based threats such as malicious links on social medias, infected websites and malicious ads are terms that we read about quite often. We security experts have for quite some time tried to emphasize the importance of protecting both your website and computer from being infected, since these malicious websites often exploit client vulnerabilities. These vulnerabilities have been one of the major attack vectors for malware writers in recent years, but is it still a problem?

We are constantly seeing new software vulnerabilities , and the bad guys are very quick to developg exploits which are then hosted in their exploit kits. The vulnerabilities themselves are not dangerous unless the attacker is able to exploit them on the victim’s computer. The attackers have therefor developed ways to get victims to visit a website, for example, which then triggers the exploit. Some common ways are through social engineering or infecting a legitimate website with redirection code that points to the exploit kit.

Last month almost all major vendors released critical security updates for their software, such as Adobe, Oracle, Apple, Microsoft and Mozilla. I then started to research the current threat landscape, and focused on Sweden since I am the security researcher for the Nordic region; and after just a few minutes I saw that both Swedish websites and Swedish users were under attack.

In September we saw a 3700% increase in JavaScript-based redirection scripts, specifically Trojan.JS.Redirector.ro. This malicious redirector went from 908th place to 15th place in the list of the most detected malware in Sweden in one month. This code only redirects users to another URL, and I thought it was strange that we did not really see an increase of detected malware in September?

Oracle Critical Patch Update October 2011

Overshadowed by the Duqu madness yesterday, Oracle released a slew of critical updates (please see "Related Links" in the right column of this page). Most interesting, but perhaps with little impact, is the Java SE BEAST update. Oracle claims to have pushed 57 different fixes across their product lines, including patches for Java and their virtualization Sun Ray product. But the hottest thing to talk about, of course, is the patch closing up CVE-2011-3389, or holes in the JSSE.

Keeping Tabs on the Next STUXNET

The security industry is currently buzzing with talks about a threat dubbed as the precursor to the next STUXNET.

According to a Symantec analysis, portions of the code are very similar to STUXNET, and was likely written by the same cybercriminals as the well-known threat. Unlike STUXNET, however, Duqu does not have code that suggests it was developed to access SCADA systems. Instead, its final payload appears to be inclined toward information theft.

Duqu is made up of several components. The SYS file, which is detected as RTKT_DUQU.A, is responsible for activating the malware, and triggering the execution of its other routines. Based on analysis, however, the main goal of the said files is to establish a connection with its C&C server. It is said that Duqu delivered an information-stealing malware, detected as TROJ_SHADOW.AF, into the affected systems through this connection. We have also verified that its codes are very similar to that of STUXNET.

Upon execution, TROJ_SHADOW.AF enumerates the processes currently running on the system. It also checks if it matches any of the following security-related processes:

  • avp.exe (Kaspersky)
  • Mcshield.exe (McAfee)
  • avguard.exe (Avira)
  • bdagent.exe (Bitdefender)
  • UmxCfg.exe (CA)
  • fsdfwd.exe (F-Secure)
  • rtvscan.exe and ccSvcHst.exe (Symantec)
  • ekrn.exe (ESET)
  • RavMonD.exe (Rising)

If found, TROJ_SHADOW.AF launches the same process in a suspended state, then patches the malware code before resuming the execution. In effect, there will be two AV processes; the first being the original, and the second being the patched one.

TROJ_SHADOW.AF requires command lines in order to execute properly. Available commands include: collecting information on the affected system, terminating malware processes, and deleting itself. It can steal a wide array of information on any affected system, such as:

1. Drive information such as:

  • FreeSpace
  • Drive device name

2. Screenshots
3. Running Processes and Owner of Running Processes
4. Network Information such as

  • IP address
  • IP routing table
  • TCP and UDP table
  • DNS Cache table
  • Local Shares

5. Local shared folders and connected users
6. Removable drives serial number
7. Window Names
8. Information on open files on local computer using NetFileEnum

We will be updating this blog entry for further developments. While our investigation is currently ongoing, preliminary information indicates that Trend Micro’s products protect against TROJ_SHADOW.AF. Smart Feedback from the Smart Protection Network™ indicates that no Trend customers have been affected by this threat. Trend Support has not received any infection notifications.

Trend Micro products have been updated to provide protections against this latest threat through updated signature as well as by blocking access to malicious control servers with Web Reputation Services.

Users may refer to our Knowledge Base page to read up on how to protect systems from this threat.

If you're new here, you may want to subscribe to our RSS feed. Thanks for visiting!



Powered By WizardRSS.com | Full Text RSS Feed | Amazon Plugin | Settlement Statement

Federal Trojan's got a "Big Brother"

About two weeks ago, the German Chaos Computer Club (CCC) has published an analysis report of a backdoor trojan that they claim had been used by German police during investigations in order to capture VoIP and IM communication on a suspect's PC. Our friends over at F-Secure published a blog post last week where they wrote about another file that, according to them, seemed to be the dropper component of the trojan. They were kind enough to share the MD5 hash of the file, so we could pull it from our collection. Stefan and I took a closer look.

The dropper carries five other binaries in its resource table, so there are six components in total - each with a different purpose - all of which have been analyzed by us. Amongst the new things we found in there are two rather interesting ones: firstly, this version is not only capable of running on 32 bit systems; it also includes support for 64 bit versions of Windows. Secondly, the list of target processes to monitor is longer than the one mentioned in the CCC report. The number of applications infected by the various components is 15 in total.

SpyEye vs. Tracker

It has become clear that the creator of the banking Trojan SpyEye have added plugin support to their code. In this new design, these plugins can be used by third parties to add extra functions to the core bot. The plugins are DLLs stored in the bot’s configuration file. Among the core plugins created for SpyEye is customconnector. As its name implies, this supports the bot’s communications with the botnet C&C or its collector. The collector is a malicious server which receives data harvested from the victim’s computer; it can be distinct from the C&C server. Since the creator of SpyEye has outsourced the botnet’s links to the C&C server, different SpyEye operators can create unique protocols governing communications between bot and server. Naturally, these protocols could make it more difficult to track the activity of SpyEye botnets. Despite this, cybercriminals have not, so far, rushed to take advantage of this opportunity: SpyEye’s old protocol in the basic customconnector.dll is still in use. Even so, we have recently spotted some changes related to this plugin.

Highlights from VB 2011 Barcelona

This year, we had the privilege of attending the 21st Virus Bulletin International Conference in Barcelona, Spain.

Researchers from Trend Micro presented three topics in the corporate stream and one topic in the technical stream. Ethan YX Chen covered file-fraction reputation for the technical stream on day 1. For the corporate steam on day 2, Max Goncharov presented on traffic direction systems as malware distribution tools while David Sancho and Rainer Link talked about the lessons they learned while sinkholing botnets. Trend Micro global director of education David Perry talked about the missing metrics of malware.

Among the different topics that were presented in this conference, we got hooked on those in the technical stream. Here’s a rundown of what we found particularly interesting.

A Mobile Malware Jail

The presentation entitled, “An OpenBTS GSM Replication Jail for Mobile Malware,” by Axelle Apvrille discussed the challenges security researchers faced when analyzing mobile threats.

As she said, the golden rule of antivirus is not to spread any malware that we are analyzing. However, when testing malware, sometimes it is necessary to connect to the Internet or to other connections during analysis in order to verify or analyze their routines. Analysis is easier to do on malware affecting computers since it is easy to isolate them from the Internet and still be able to see what they do. Mobile malware, however, are not as easy to confine since there are no wires to unplug in order to analyze them.

Since we don’t want to risk infecting our co-workers’ smartphones while trying to analyze a mobile malware, we need a way to be able to analyze mobile malware effectively without putting other users at risk.

Ms. Apvrille’s solution for this is to create a dummy GSM service operator. This is a cheaper solution compared with building a Faraday cage but it is as effective in confining the malware. It uses OpenBTS, an open source, Unix-based application, and a Universal Software Radio Peripheral (USRP) device. How cheap is cheap? Around US$1,000. Still expensive but we believe this is a good investment for antivirus companies due to the growing number of mobile malware.

Fraud and Stealth Malware

The presentation about fraud malware analysis showed us that FAKEAV/fake tools have been around for some time now and will probably be there for even longer because of their capability to adapt to changes in the computing landscape.

According to the report, we may even expect such threats to adapt to mobile platforms in the coming years.

The stealth malware presentation analysis featured recently emerging rootkits and bootkits, including the infamous TDL Family, Zeroaccess, POPUREB, and Mebromi (aka MyBios).

File Reputation Research

In his presentation, Tim Ebringer of Microsoft brought out the issue regarding difficulties with finding other malware samples related to one particular file. This was similar to Ethan YX Chen’s paper wherein he proposed a solution to combine reputation- and content-based solutions. He offered a different perspective on the efforts to fight against today’s highly polymorphic, micro-distribution malware.

There are a lot of malware families right now so how can we say that a certain sample belongs to a certain malware family?

For the popular ones (Autorun, OnlineGames, FAKEAV), there is no problem but for the not-so-popular ones (RAMNIT, SYSWRT), the likelihood of placing the sample in a new family is high, therefore, damaging the malware taxonomy.

With Bindex, all malware samples are divided into blocks of code and stored in a database. If a new sample that is being analyzed by an engineer contains an interesting code snippet, he/she can search the database using the snippet and find related malware. If the result turns out to be very broad (e.g., composed of different families) then the code snippet that he/she searched may be a compiler code.

Being able to identify a compiler code can help avoid false alarms since the engineer will then know that the code should not be used as a malware signature. Overall, we think this application is of great help in creating heuristic detections.

VB2011 was a great experience for meeting other people in the antimalware industry. In sum, the learning we gained during the conference will definitely help us become even stronger in our battles against future threats and ultimately be better in providing solutions for and in protecting users.

If you're new here, you may want to subscribe to our RSS feed. Thanks for visiting!



Powered By WizardRSS.com | Full Text RSS Feed | Amazon Plugin | Settlement Statement

Another Modified ZeuS Variant Seen in the Wild

In the past, we’ve reported about malware based on the leaked ZeuS code, such as Ice IX, and ZeuS 2.3.2.0, and this usage of the leaked code has continued on since then, and has resulted to attacks such as the one I’m about to share.

My colleagues and I have been monitoring another new version of ZeuS since the late September, one that we believe is also based on the leaked ZeuS source code. Although this new ZeuS variant seems to have no reference on its code of its version number, we believe it was developed by the same criminals behind LICAT.

This new version, detected as TSPY_ZBOT.SMQH spread around late September through spam that claims to be from ATO (Australian Taxation Office). The spammed messages contain a malicious link, which when clicked directs users to a malicious website that serves the BlackHole exploit kit. The exploit kit, in turn, downloads a variant of this new ZeuS version.

Unlike earlier ZeuS versions that use HTTP to download its configuration file, this version opens a random UDP port and connects to a hardcoded list of IP addresses to download its configuration file.

TSPY_ZBOT.SMQH establishes connection with the server by sending encrypted data which contains the bot ID and a stream of characters. Each IP address in the hardcoded has a corresponding stream of characters which the server seems to check to validate the communication.

Click for larger view

If any of the IP addresses is alive, it will reply with the encrypted configuration file via TCP.

Decrypting the Configuration File

Once the configuration file is downloaded, TSPY_ZBOT.SMQH will employ the following decryption algorithm for its configuration file:

As we can see, unlike ZeuS 2.3.2.0 which uses Advanced Encryption Standard (AES), the decryption algorithm did not change much compared to the modified ZeuS 2, which uses RC4.

As I mentioned earlier, like LICAT and ZeuS 2.3.2.0, this new variant also seems to be crafted by a private professional gang, probably the same creators of LICAT, or affiliated with them at least. In fact, the configuration file for TSPY_ZBOT.SMQH has the same format as that of the configuration file of LICAT.

Although the spammed messages only target Australian users, the contents of the decrypted configuration file suggest that it may be used in a global campaign, including the United States, European, and even Asian countries.

We will continuously monitor this threat and other variants that will emerge in the future.

Thanks to Mark Dixon of Westpac Bank of Australia for providing samples of the related malware and spam.

If you're new here, you may want to subscribe to our RSS feed. Thanks for visiting!



Powered By WizardRSS.com | Full Text RSS Feed | Amazon Plugin | Settlement Statement

Return of the Hack, Playstation Accounts breached again

Sony has reported that it has had a number of sign-in attempts on accounts belonging to users on its various networks. In a statement on the Sony site it was revealed that “Sony Network Entertainment International LLC and Sony Online Entertainment (SOE) have detected a large amount of unauthorized sign-in attempts on PlayStation®Network (PSN), Sony Entertainment Network (SEN) and Sony Online Entertainment (SOE) services.”

A Refresher on Spam and Exploits

Lately, we have been seeing a renewed increase in volume of spam attacks that utilizes an exploit kit – specifically, the BlackHole exploit kit – to trigger a malicious payload. Specifically, we have seen this in the latest slew of Automated Clearing House (ACH) spam, and the more recent spam run related to Steve Jobs’ death.

In this post, we will reorient readers on the infection chain of such attacks to help us understand why the basic mitigation practices are still effective and helpful in protecting one’s self from today’s threats.

In a typical spam campaign that involves malware, cybercriminals lure users through social engineering into performing several actions before the intended payload gets executed. For example, a user needs to download, extract, and execute a supposedly “benign” file for a spam attack to succeed.

Spam campaigns using exploit kits, however, are a bit more dangerous since they only need to lure the user into clicking a malicious link and the rest of the infection will be able to take place.

Below is an example of this type of spam purporting to be coming from National Automated Clearing House Association (NACHA). NACHA manages the ACH network, which facilitates bulk payment transactions involving businesses, governments, as well as consumers. Users who are more likely to receive email from NACHA are those who conduct transactions related to payroll, government benefits, tax refunds, and others.

Click for larger view

In the spam screenshot above, we can see that the link points to a dubious-looking domain that is not related to National Automated Clearing House Association (NACHA). A blank page is displayed when users click the link. This blank page is actually a gateway page that contains the following obfuscated JavaScript:

When decrypted, we can see that it is a script that attempts to embed an iframe pointing to another malicious site, which uses the BlackHole Exploit Kit:

Once the iframe is loaded, content is also loaded from the BlackHole Exploit Kit site which, again, contains a highly obfuscated script. Upon decoding the code, we can now see the actual code which searches for vulnerable software and uses the appropriate exploits.

The BlackHole Exploit Kit exploits vulnerabilities both in third-party applications like Adobe Acrobat, Adobe Flash, and Java, as well as in Windows components like Microsoft Data Access Components (MDAC) and Help and Support Center (HCP).

Click for larger view

Successful exploitation executes a shellcode, which triggers downloading and executing malware. We have observed that these attacks have been used to spread ZeuS variants, although these may also be used to spread other malware families.

Multilayer Mitigation

As a reminder to users, here are some ways to prevent this kind of threat from getting into their systems:

  • Be aware of social engineering attacks. A majority of online attacks today utilize social engineering before they can exhibit technical infection. By being wary of what you do online, infections can already be mitigated at the onset. Simple common sense like not entertaining unsolicited emails could go a long way in terms of your personal online security.
  • Always check for malicious links. Always check where the URLs hyperlinks point to. It is also a good practice to copy and paste a URL to your browser address bar instead of clicking links directly.
  • Consider disabling JavaScript in your browser. As mentioned earlier, the gateway page and the BlackHole Exploit Kit page both used JavaScript. This is also the case for a lot of threats today that use the browser to execute a malicious payload. As such, it is a good idea to consider disabling JavaScript in your browser and only allow it to your trusted sites if necessary.
  • Always remember to patch. The BlackHole Exploit Kit utilizes exploits that affect old, unpatched versions of software. The persistence of such tools means that old exploits are still able to infect many users. No matter how inconvenient it may be, patching your software regularly is still an important mitigation process.

The state of the threat landscape and the overwhelming reliance of the general public on the Internet demands that users should have awareness of the kinds of threats found on the Web, as well as ways to protect themselves through it. In having knowledge of how attacks such as this one work, users can gain advantage of the attackers, and be able to stop a threat even before it gets into their system. A little self-education can ultimately make the whole Internet a better and safer place to be.

More information on how cybercriminals have utilized spam in their malicious schemes can be found on our recently released security focus report, Spam in Today’s Business World.

If you're new here, you may want to subscribe to our RSS feed. Thanks for visiting!



Powered By WizardRSS.com | Full Text RSS Feed | Amazon Plugin | Settlement Statement

Latin American banks under fire from the Mexican VOlk-Botnet

Latin America has ceased to be a region that simply receives attacks from across the world.

Since late 2009 it has begun to copy fraudulent business models through which American cybercriminals have begun producing their own criminal resources.

Examples include Brazil, with the web application called TELA (to manage the information stolen from zombie computers); or S.A.P.Z. from Peru, used to propagate malicious code designed to steal bank details. But of course, these are not the only ones. Mexico has also joined this list, with different crimeware developments. Tequila and Mariachi crimeware programs started the trend in this region, back in 2009. But the newest is VOlk-Botnet. The following image shows the main page:

More Articles...

Page 1 of 43

Start
Prev
1