3% of Government Websites Still Remain Unpatched Against the OpenSSL “Heartbleed Bug”

Yesterday, I collected over 1,200 .GOV TLD domains and ran checks against them.  Of that, 58 were affected by the OpenSSL bug, aka, Heartbleed.  This morning, upon checking again, only 39 remain unpatched of that initial 58 affected.

During my testing I was able to inadvertently obtain login credentials for a particular .GOV website illustrated in the screenshot below.

Heartbleed affected .GOV website showing user credentials

Heartbleed affected .GOV website showing user credentials

I collected the .GOV domains from http://www.data.gov/.  I cooked a simple bash script loop against this list and passed it to a Proof of Concept “check” tool to determine if the site was unpatched.  The tool I used is https://gist.github.com/takeshixx/10107280 (python).

Read More

OpenSSL “Heartbleed Bug” Check

heartbleedI published a web-based Heartbleed Bug check tool, https://techish.net/pub/Heartbleed/, based on the project from http://filippo.io/Heartbleed/.  His server was overloaded and I wanted to provide some friends and colleagues a way to test their systems.  Along with the web-based version, you can also test from the command line in Linux.  To find out more about the OpenSSL Heartbleed Bug, you can visit http://www.heartbleed.com/.

wget -qO- https://techish.net/pub/Heartbleed/?h=google.com

Hope this helps anyone out there needing a way to test if they are vulnerable.

Google, MSN, Yahoo Search Redirector Malware HiJack

Google Redirect Malware, Virus, Spyware…

UPDATE (9/29/2011 9:15AM EST)
I have corrected the link to the 7770finder.exe file. This still detects the original strain of this piece of malware. To fully innoculate and protect yourself, I recommend downloading Malwarebytes’ Anti-Malware software:http://www.malwarebytes.org/. It’s FREE for personal use!

UPDATE (1/19/2009 6:30PM EST)

I’ve been getting a lot of email questioning why my tool did not remove found infected files.  This tool does NOT remove any infected files.  It is up to you to remove them.  This tool also does not support directory recursion;  e.g., it ONLY scans %SystemDir% files, no subfolders.  Sorry.

UPDATE (1/15/2009 12:51PM EST)

I have been able to successfully re-infect myself and I can confirm this is being distributed via PDF JavaScript as I was monitoring processes and my system32 directory as I visited a known vulnerable site.  I also saw ~.exe process start up during my monitoring after I saw Acrobat.exe and acrotray.exe start up.  Once infected, the processes (Acrobat, Acrotray) terminated.

To help prevent infection take the following actions:

Adober Reader: Disable Adobe JavaScript functionality (Edit -> Preferences, go to JavaScript entry and untick “Enable Acrobat JavaScript”)

Foxit Reader: Edit -> Preferences -> JavaScript (Uncheck the box)

Use NoScript Firefox Plugin

Tips thanks to Edvard and app103 over at DonationCoder

UPDATE (1/14/2009 11:17PM EST)

Update your PDF application and disable JavaScript.

UPDATE (1/14/2009)
Malwarebytes is able to detect the malware.   Interestingly enough, it only detects it if it’s in c:windowssystem32drivers folder.  I’m not sure what’s up with that. Update the applications to ensure you’re using the latest definitions.  If you know of any other Spyware/Malware/AV software that is detecting this, leave a comment.

AVG supposedly detects this threat (posted by: Peter Liu)

Please let me know of any other software that detects this.


Here’s what I know about this lovely little malware that hijacks Google, MSN Live, and I’m sure a few other popular search engines by injecting javascript in the header:

1) Redirects searches to

2) Displays what appear to be normal results, but in fact are linked to many other malware centric sites

3) Kaspersky (as of this writing) is the only application to detect the presence of this malware on your PC (and yes I’ve tried Malware Bytes, Spybot S&D, AntiVir, SuperSpyware)

4) The culprit file resides in c:\windows\system32\wdmaud.sys and should be removed, or renamed.  Don’t remove the file from c:\windows\system32\drivers\wdmaud.sys.

5) After deleting/renaming the file, restart your browser(s) and you’ll be OK.  Note:  This affects IE and FF, I have not tested Opera, Netscape or Safari.

Here’s an example screenshot of what Google results look like when you are infected.  Notice the Google links (green links) on the results page.


What I’d like to know is what that file has to do with the browser.  The WDMAUD.sys file (the real one) deals with Windows High Definition Audio.  Could this file have been placed there via Flash vulnerability?  I know I was on YouTube the night prior to me being invaded.

I ran ProcessMon from SysInternals and saw that Firefox and IE both called for wdmaud.sys but in the c:\windows\system32 directory, not in the drivers subfolder.  Here’s a screenshot of that.  If I move the file (the infected file) out of system32 the redirection stops.  If I put it back in the infection is back.  My question that is burning me is HOW did it get there?  What put it there?


Process Monitor highlighting the search request for wdmaud.sys

Removal Instructions

So far, the infection is in c:\windows\system32\wdmaud.sys (or c:\winnt\system32\wdmaud.sys).  Simply delete the file and restart any open web browsers.

Detection Tool

If you do not find the wdmaud.sys file, or are unsure what to even look for, you may download a tool that we created that will investigate all the files in the Windows system directory.  It doesn’t just specifically look for the wdmaud.sys file, but it looks for the signature in every file within that directory.

Compatible with:  Windows XP (all SPs), Server 2000/2003/2008, and Vista.

Your use of this software indicates that you agree to the attached terms of service.

Download Tool Here (EXE) (md5:74705f9d02ae429f6ca84662ac755621)

Tool Update (1/16/2009)

* Prints path of file that is infected

* Allows program to accept a path as an argument;  otherwise it uses %SystemDir% as default if no path specified

* Still no recursion -yet-

If you download the tool and find it useful, or don’t find it useful, I’d appreciate any feedback.  You can leave a comment or send any questions/comments to rjkreider@gmail.com.