<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;D0MERX06fSp7ImA9WhVUEUU.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359</id><updated>2012-05-16T12:23:24.315-04:00</updated><category term="linux" /><category term="attack" /><category term="challenge" /><category term="dumb criminals" /><category term="sandnet" /><category term="PDF" /><category term="vulnerability" /><category term="malware" /><category term="malware analysis" /><category term="penetration testing" /><category term="musing" /><category term="puzzle" /><category term="conference" /><category term="phish" /><category term="SQL injection" /><category term="forensics" /><category term="APT" /><category term="presentation" /><category term="exploits" /><category term="hacks" /><category term="wireless" /><category term="spam" /><category term="class" /><category term="virus" /><category term="stories" /><category term="scam" /><category term="physical security" /><category term="training" /><category term="crypto" /><category term="snort" /><category term="anti-virus" /><title>The Security Shoggoth</title><subtitle type="html">Stories of an elder thing creation making its way in the world of information security.</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://secshoggoth.blogspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>79</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/TheSecurityShoggoth" /><feedburner:info uri="thesecurityshoggoth" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry gd:etag="W/&quot;D0MDRng9eip7ImA9WhRWEUs.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-5503481227325903330</id><published>2011-12-19T10:05:00.004-05:00</published><updated>2011-12-29T08:31:17.662-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-12-29T08:31:17.662-05:00</app:edited><title>Tools and News</title><content type="html">So first an announcement.  At the beginning of December (or close to that) I left my previous position and went back to &lt;a href="http://www.korelogic.com"&gt;KoreLogic Security,&lt;/a&gt; where I will be working to start up their malware services group, amongst other things.  While I am definitely missing my old co-workers, this is a good move for me.  Look for some interesting posts here.&lt;br /&gt;&lt;br /&gt;A few weeks ago I tweeted: Want to find out how good someone is? Take away all their tools and say, "Now do it.".  I wanted to make expand upon that because I got into a good discussion with &lt;a href="https://twitter.com/#%21/@jwgoerlich"&gt;@jwgoerlich&lt;/a&gt; and &lt;a href="https://twitter.com/#%21/@rogueclown"&gt;@rogueclown&lt;/a&gt; concerning it, and its hard to really explain what you mean in 140 characters or less.&lt;br /&gt;&lt;br /&gt;A few years ago, Harlan Carvey posted about "&lt;a href="http://www.google.com/search?q=%22nintendo+forensics%22&amp;amp;q=%22nintendo+forensics%22+site:windowsir.blogspot.com&amp;amp;pbx=1&amp;amp;oq=%22nintendo+forensics%22"&gt;Nintendo forensics&lt;/a&gt;".  This was a statement that the forensic industry was becoming more "point and click" and analysts were understanding less and less of what the tools were doing.  While some signs have pointed that this is starting to become less prevalent, I believe there are still niches in security where this is either in full-force or starting to become more so.&lt;br /&gt;&lt;br /&gt;Fast forward to the present.  In the last few weeks I've been building my new work computer while analyzing malware as I get the time.  Unfortunately, I do not have all the tools I am used to since I'm waiting for things to be purchased, arrive, etc.  This got me thinking - how much do &lt;span style="font-weight: bold;"&gt;&lt;span style="font-style: italic;"&gt;I&lt;/span&gt; &lt;/span&gt;rely on tools?  Could I perform the analysis I needed using that I know?&lt;br /&gt;&lt;br /&gt;Now I realize that in information security, or IT in general, its almost impossible to do anything without having tools.  Thats not my point - I'm not suggesting that we take away everyone's tools and tell them to analyze malware or perform a pen-test with nothing but a blank OS.  Is it possible?  I'm sure it is.  Would anyone want to?  Hell no!&lt;br /&gt;&lt;br /&gt;My point was that you never really know how good &lt;span style="font-style: italic;"&gt;you&lt;/span&gt; are, until &lt;span style="font-style: italic;"&gt;you&lt;/span&gt; are faced with a situation when you are taken out of your comfort zone and have to rely upon &lt;span style="font-style: italic;"&gt;your&lt;/span&gt; knowledge and the tools available to you at the moment.  I don't always have access to a commercial version of IDA Pro.  Does that mean I can't disassemble malware and analyze it?  No - I just need to be flexible, use tools that I'm not as used to and use my brain just a little bit more.&lt;br /&gt;&lt;br /&gt;I think its a useful exercise in anyone's career to do this.  Imagine for a moment that you didn't have the tool(s) you use most in your job - how would you perform your job?  What alternatives are available to you and how familiar you are with them?  I'm as guilty as anyone else for relying upon specific tools, but this little exercise has helped me look and see where my weak areas are and how I can supplement them.&lt;br /&gt;&lt;br /&gt;Perhaps I should have instead tweeted "Want to find out how good &lt;span style="font-weight: bold; font-style: italic;"&gt;you are&lt;/span&gt;? Take away all &lt;span style="font-weight: bold; font-style: italic;"&gt;your&lt;/span&gt; tools and say, Now do it."  That seems to fit my point better.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-5503481227325903330?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/5503481227325903330/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=5503481227325903330" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/5503481227325903330?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/5503481227325903330?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/GWFntU-f1w0/tools-and-news.html" title="Tools and News" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>0</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2011/12/tools-and-news.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEEBSHc6eSp7ImA9WhRTEkg.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-4405495387048857365</id><published>2011-11-02T13:33:00.004-04:00</published><updated>2011-11-02T13:57:39.911-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-11-02T13:57:39.911-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="conference" /><category scheme="http://www.blogger.com/atom/ns#" term="crypto" /><category scheme="http://www.blogger.com/atom/ns#" term="puzzle" /><title>Answers to the NEOISF Crypto Challenge</title><content type="html">If you were at the &lt;a href="https://www.informationsecuritysummit.org/"&gt;2011 Information Security Summit&lt;/a&gt; last week, you may have come across the &lt;a href="http://www.neoisf.org/"&gt;Northeast Ohio Information Security Forum&lt;/a&gt;'s booth and saw the crypto challenge I created for it. &lt;br /&gt;&lt;br /&gt;The challenge was a series of three encoded messages, each more difficult than the last.  It seemed to be popular as I had printed off 50 copies of the challenge and they were all gone by Friday morning.  Only 2 people, that I know of, finished it (although more may have and just not told me).&lt;br /&gt;&lt;br /&gt;The first encoded message was:&lt;br /&gt;&lt;blockquote style="font-weight: bold;"&gt;Olgrf Rapelcgrq Ner Yrff Rnfl!&lt;br /&gt;&lt;/blockquote&gt;This was a &lt;a href="http://rot13.com/"&gt;ROT13&lt;/a&gt; message that when decoded changed to:&lt;br /&gt;&lt;blockquote&gt;Bytes Encrypted Are Less Easy!&lt;br /&gt;&lt;/blockquote&gt;The second message was a bit harder.&lt;br /&gt;        &lt;style type="text/css"&gt;p { margin-bottom: 0.08in; }&lt;/style&gt;  &lt;p style="margin-bottom: 0in; font-weight: bold;"&gt;&lt;/p&gt;&lt;blockquote&gt;Tymxmu Svpvwmeh sg xhp fpskwiu ms elf oej&lt;br /&gt;&lt;/blockquote&gt;&lt;p&gt;&lt;/p&gt;&lt;br /&gt;To make it a little easier, a hint was given to use the first letter of every word from the first solution as the key.  This was actually another hint that a key was even required to decode the message.  The original message had been encrypted using a &lt;a href="http://sharkysoft.com/misc/vigenere/"&gt;Vignere Cipher&lt;/a&gt;.  Decrypting the message, using the key "BEALE" would produce the following message:&lt;br /&gt;&lt;blockquote&gt;Summit Overview of the booklet is the key&lt;/blockquote&gt;The final puzzle was the hardest of all.  The encoded message was:&lt;br /&gt;         &lt;style type="text/css"&gt;p { margin-bottom: 0.08in; }&lt;/style&gt;  &lt;p style="margin-bottom: 0in;"&gt;&lt;/p&gt;&lt;blockquote&gt;10 11 32 35 177 42 50 54 44 50 42 82 132 71 100 157 54 60 147 66 50 193 3  60 81 100 157 75 36 106&lt;/blockquote&gt;&lt;p&gt;&lt;/p&gt;The hint for this puzzle was "Items from the first two solutions will help you figure this one out!"  Each of the first two solutions gave some type of clue as to the cipher used for the last one.  The first puzzle's hint was the key for the second puzzle: BEALE.&lt;br /&gt;&lt;br /&gt;If anyone searched for BEALE, they would have eventually come across the &lt;a href="https://secure.wikimedia.org/wikipedia/en/wiki/Beale_ciphers"&gt;Beale Ciphers&lt;/a&gt;, encoded messages that supposedly point to buried treasure.  The only message successfully decoded thus far used the Declaration of Independence as a key.  To decode it, you find the word corresponding to the number you are given and take its first letter.  IE. If you have a 10, find the 10th word and use its first letter.  When you put all of these together you get the decoded message.&lt;br /&gt;&lt;br /&gt;This is what you would have to do in order to solve the third puzzle.  But what book do you use to decipher it?  That is where the answer to the second message comes in.  The solutions tells you to use the welcome page in the information security summit booklet.  By taking the first letter of each word of the corresponding number, you would eventually get the following message:&lt;br /&gt;&lt;blockquote&gt;now there are no more secrets for you&lt;/blockquote&gt;&lt;br /&gt;I hope that those who did this found it fun.  I'd love to do another next year, but on a bigger scale.  If anyone has any suggestions, I'd love to hear them!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-4405495387048857365?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/4405495387048857365/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=4405495387048857365" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/4405495387048857365?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/4405495387048857365?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/nsyXWLWHk1g/answers-to-neoisf-crypto-challenge.html" title="Answers to the NEOISF Crypto Challenge" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>0</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2011/11/answers-to-neoisf-crypto-challenge.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUYHRXc_eSp7ImA9WhdQF0U.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-4349369477158010848</id><published>2011-08-19T15:33:00.003-04:00</published><updated>2011-08-19T15:45:34.941-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-08-19T15:45:34.941-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="conference" /><category scheme="http://www.blogger.com/atom/ns#" term="malware analysis" /><category scheme="http://www.blogger.com/atom/ns#" term="training" /><title>Malware Analysis and Malicious Document Analysis Training Courses</title><content type="html">&lt;span style="font-style: italic;"&gt;This is a totally self-serving, marketing post.  Feel free to click that little X in the upper right corner of your browser.&lt;/span&gt;
&lt;br /&gt;
&lt;br /&gt;The &lt;a href="https://www.informationsecuritysummit.org/"&gt;Ohio Information Security Summit&lt;/a&gt; is coming up again from October 27-28  The &lt;a href="https://www.informationsecuritysummit.org/ConferenceAgenda2011.pdf"&gt;conference agenda&lt;/a&gt; is starting to fill in and lots of great talks look to be scheduled!  I will be speaking there with &lt;a href="http://securityblahblah.blogspot.com/"&gt;Greg Feezel&lt;/a&gt; and the NE Ohio Honeynet Project.
&lt;br /&gt;
&lt;br /&gt;There will also be &lt;a href="https://www.informationsecuritysummit.org/2011TrainingDescriptions.doc"&gt;pre-conference training&lt;/a&gt; from October 24-26.  There are more classes this year than last year, many of which look great!
&lt;br /&gt;
&lt;br /&gt;I will be giving my 2-day hands-on Malware Analysis training course again this year.  It is a 2-day course that covers the basics of malware analysis.  The training is geared towards those who have never done, or performed very little, malware analysis.  Plus, if you take the 2-day course, you'll get into my new 1-day Malicious Document course for free!
&lt;br /&gt;
&lt;br /&gt;The Malicious Document training course I am doing for the first time this year will cover how to analyze malicious documents (duh).  Specifically, I will cover malicious JavaScript, PDFs and touch on malicious Word documents.  This is a 1 day course where the students will be very hands-on - analyzing malicious documents from the wild.
&lt;br /&gt;
&lt;br /&gt;If you have any questions on the courses, please feel free to contact me!
&lt;br /&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-4349369477158010848?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/4349369477158010848/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=4349369477158010848" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/4349369477158010848?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/4349369477158010848?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/UQNdpjEOeRU/malware-analysis-and-malicious-document.html" title="Malware Analysis and Malicious Document Analysis Training Courses" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>0</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2011/08/malware-analysis-and-malicious-document.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0UDSH4_fSp7ImA9WhZWE0w.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-3414048940682363131</id><published>2011-05-12T14:17:00.000-04:00</published><updated>2011-05-13T16:41:19.045-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-05-13T16:41:19.045-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="malware" /><title>Proactive Incident Response</title><content type="html">A little while ago Harlan Carvey posted on &lt;a href="http://windowsir.blogspot.com/2011/04/proactive-ir.html"&gt;Proactive Incident Response&lt;/a&gt;.   I've been thinking about this for a while, but have a different perspective on Proactive IR than he does.  (I agree with his take on it, I just look at Proactive IR differently.)&lt;br /&gt;&lt;br /&gt;Computer Incident Response Teams (CIRTs) are often referred to as fire fighters.  This analogy is very true - most of the time CIRTs are fighting fires; the fire being a hacked server, a malware outbreak or a targeted phishing campaign.  We're often jumping from one problem to the next, determining who got in, how they did it, what damage they caused and how to prevent it in the future.  However, is that all CIRTs should be doing?&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.cert.org/archive/pdf/csirt-handbook.pdf"&gt;The CERT Handbook for Computer Incident Response Teams&lt;/a&gt; states that CIRTs should offer three different services: reactive, proactive and security quality management services.  Reactive services are the fire fighting done on a daily basis.  Security quality management services include project and security consulting for other business units; you know, those meetings you get pulled into where they ask you what you think.  What about proactive services?&lt;br /&gt;&lt;br /&gt;If we look back at actual fire fighters, we see that they don't just spend their time putting out fires.  One of their duties is to help fire prevention through education and fire inspections.  In the security world, this is analogous to doing user education, vulnerability scanning and penetration tests.  This is what proactive services are.  But I believe these is another aspect of proactive services that CIRTs tend to miss.&lt;br /&gt;&lt;br /&gt;One of my co-workers has coined a term: hunting trips.  This basically boils down to proactively looking around the interwebs for attackers you've seen in the past.  Since attackers tend to use the same, or similar tools and tactics, indicators of their compromises in other organizations appear if you know where to look.  You can then use the new indicators you've just found to check for signs of compromise in your network.&lt;br /&gt;&lt;br /&gt;Where can you look?  Anywhere that information on security analysis can be found.  This includes blogs, twitter, forums, online sandboxes, AV signature descriptions, etc.  All of these places (and more) have information you can use to tie attackers to new attacks and malware they are using. &lt;br /&gt;&lt;br /&gt;Of course, I wouldn't recommend hand-searching each of these places for information.  Google is the obvious place to start, but be prepared to get back hundreds of results (at best) that are not of interest to you.  I would recommend using the &lt;a href="http://www.google.com/cse/home?cx=011750002002865445766:pc60zx1rliu"&gt;Google Malware Analysis Search&lt;/a&gt;, created by those behind the &lt;a href="http://hooked-on-mnemonics.blogspot.com"&gt;Hooked on Mnemonics Worked for Me&lt;/a&gt; blog, that narrows Google's search to 75 different security sites and feeds.&lt;br /&gt;&lt;br /&gt;So, an example so this might actually make sense.  In the last few days there has been an uptick in spammed emails that contain a link to a zip file named order.zip.  Within this file is a SpyEye trojan.  Analysis of the trojan shows that it drops itself as c:\recycle.bin\recycle.bin.exe (which to my knowledge is not a default location for SpyEye).  This location is fairly unusual and can be a good indicator to use on a hunting trip.&lt;br /&gt;&lt;br /&gt;Using the Google Malware Analysis custom search to look for "recycle.bin.exe", we come across a &lt;a href="http://www.threatexpert.com/report.aspx?md5=127c4f729e6303a99b6704a471c9310d"&gt;ThreatExpert report from March 2011&lt;/a&gt; for the same filename being dropped for a SpyEye trojan.  The TE report also shows that it attempts to contact zweor.com for its C&amp;amp;C server.  We now have a new indicator to search our network for and to go hunting with.&lt;br /&gt;&lt;br /&gt;This is a very simple scenario, but demonstrates the usefulness of performing information gathering to find additional indicators.  I have a feeling most CIRTs are not doing this and would benefit greatly from setting aside time to make sure this is done.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-3414048940682363131?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/3414048940682363131/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=3414048940682363131" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/3414048940682363131?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/3414048940682363131?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/1pnb_ApcoIQ/proactive-incident-response.html" title="Proactive Incident Response" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>0</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2011/05/proactive-incident-response.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkQNQ3czfCp7ImA9Wx9WFU4.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-7473068707767028958</id><published>2011-01-20T10:37:00.002-05:00</published><updated>2011-01-20T10:46:32.984-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-01-20T10:46:32.984-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="scam" /><title>Wanna be a mule?</title><content type="html">Its been a while since I've posted and I apologize.  As things get busy I find I have less time to post on there.  However, one of my new year's goals is to post more so there should be more in the coming weeks.&lt;br /&gt;&lt;br /&gt;I received an email today from my mother who received an email for a job and wanted to know if its legit.  After skimming it my alarms went off and were soon &lt;a href="http://scamfraudalert.wordpress.com/2011/01/19/medline-financial-industries-plc/"&gt;verified&lt;/a&gt;.  To be honest, I've always heard about money mule job requests but have never seen one so I found it interesting.&lt;br /&gt;&lt;br /&gt;I'm currently trying to get mail headers to see where it actually came from.  It is nice to know they offer insurance and a 401K.  :)&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;&lt;/blockquote&gt;&lt;blockquote&gt;From: "Ella D Dickinson" &lt;medlineplc@aol.com&gt;&lt;br /&gt;Subject: RE: [1] Message from Careerbuilder: You have received a new job opportunity&lt;br /&gt;Date: Wed, 19 Jan 2011 23:49:34 -0000&lt;br /&gt;&lt;br /&gt;Hello,&lt;br /&gt;&lt;br /&gt;Please allow me to introduce myself: my name is Ella D. Dickinson and I am the International Human Resource Manager of Medline Financial Industries PLC I am pleased to inform you that we have an open position for you within our company.&lt;br /&gt;&lt;br /&gt;Medline Financial Industries PLC was founded in 1980 and has quickly grown to be one of the largest resellers of medical equipment and apparatus in the United Kingdom as well as in the rest of Europe. We work exclusively with hospitals and other medical companies and groups supplying several hundred types of products ranging from surgical needles and syringes to EKG and MRI machines and everything in between. We have dozens of agreements and contracts with top manufacturers around the world such as GE Healthcare, Medtronic, Baxter International, Cardinal Health, Tyco Healthcare, Siemens Medical Solutions, Philips Medical Systems, Zimmer Holdings, et cetera. Our company has grown very fast during the last few years so now we have expanded our market and business to the United States as well. As such we have a big number of openings in almost every state and we are looking for dedicated and hard working individuals to work for us and help us expand.&lt;br /&gt;&lt;br /&gt;The reason for our success is the fact that we are able to meet our customer's demands wherever and whenever. We are very flexible and we can honor our orders when others cannot. This is due to the fact that we accept almost any type of payments and we have a very fast delivery system which combined with the great customer support we provide took us to where we are today. We take great pride in what we do because it is not always easy to satisfy all customer demands while still processing the orders very fast and receiving payments for the products in a timely manner. This is why we need you and bellow you will find the job description and what is asked of you.&lt;br /&gt;&lt;br /&gt;Description:&lt;br /&gt;&lt;br /&gt;-NO SALES INVOLVED&lt;br /&gt;-While performing this job you will encounter no fees to be paid in advance whatsoever;&lt;br /&gt;-No employee from our company will ever ask you for any sensitive information;&lt;br /&gt;-You will not be involved in any contact with our customers;&lt;br /&gt;-Everything you will do is legal under the European Union/United States and International laws as they are currently applied.&lt;br /&gt;&lt;br /&gt;Your duties are:&lt;br /&gt;&lt;br /&gt;1. Receive payment from our customers. All check will be write in your name. All checks are US checks, no international. You wil receive all checks via USPS (no signature required).&lt;br /&gt;2. Cashing the checks at your existing bank account.&lt;br /&gt;3. Deduct 10% which will be your percentage/pay on each payment processed.&lt;br /&gt;4. Forward balance after deduction of percentage/pay to any of the offices you will be contacted to send payment to. (Payment is to be forwarded by Western Union Money Transfer).&lt;br /&gt;&lt;br /&gt;Your benefits are:&lt;br /&gt;&lt;br /&gt;-10% from each check your will process in the first month. Within one month after receiving the first check you will receive $1,000 as fixed salary.  This is a commission based job, the faster your process orders the more your income will increase. This bonus is given to also cover internet, phone or gas bills. Please note that this salary will be sent after 30 days have passed since you received your first payment to process.&lt;br /&gt;&lt;br /&gt;After two months of working for us an increase to 15% commission from all payments might be applied to your contract if you process and send all the transfers to us in a timely manner. In this case you will be earning around $1,200-1,300 per week as well as the $1,000 salary at the end of the month.&lt;br /&gt;&lt;br /&gt;There are also minor bonuses for cashing the checks and sending the payment to us very fast:&lt;br /&gt;-Cash the check same day: $150 for each check;&lt;br /&gt;-Cash the check within 24 hours: $100 for each check;&lt;br /&gt;-Cash the check within 48 hours: $ 50 for each check.&lt;br /&gt;&lt;br /&gt;The $1,000 salary will be sent to you in form of a cashier check.&lt;br /&gt;&lt;br /&gt;The today's situation on the financial market requires us to open and fill several of these job positions within our company; the job opening is that of a Representative within the US. This opening will help our company to reduce the time it takes to receive funding from orders that we receive each month. And we offer you one of the highest incomes on the market today and the minimal expenditures of time.&lt;br /&gt;&lt;br /&gt;Presently with the number of orders we have we cannot put them on hold for fear of losing our customers, secondly we cannot cash these payments from the US soon enough, as international checks take about 28 working days to cash anywhere in Europe. We lose a lot of time and money each month because we have money transfer delays. Our clients could pay us where we want by sending checks to an US address. What we need you to do is to provide us an address where you can receive our customer checks. We need someone who can receive the money through this method of payment. Regarding the check process all you have to do is to receive the checks our customers will send to your address, take them to your bank, cash them and send the remainder amount to us after deducting all fees incurred and your commission. All fees for transferring the funds will be supported from our share. Bonuses will apply for cashing checks within 24 hours upon receiving a check. You will always take your commission upfront.&lt;br /&gt;&lt;br /&gt;We make direct contact for sales of products. Once orders are received and processed we deliver the product to our customer (usually through USPS). The customer receives and checks the product and proceeds to send the payment. We accept all forms of payment but most of our customers pay using Bank Checks and so to solve this problem and not lose any of our customers we have decided to open this new job position. This job is legal according to the U.S. legislation as it is today. Local money transfers take but a few hours, so it will give us a possibility to get customer's payment almost immediately.&lt;br /&gt;&lt;br /&gt;PAYMENT AND SALARY:&lt;br /&gt;&lt;br /&gt;For example you receive a check as payment for 3000.00 USD, you deduct your commission (10%): 300.00 USD and then send to us the balance: 2700.00 USD. In the first month you will receive around 15-20 orders under 3,000.00 USD to process and after checking your performance records during that first month the orders you will receive, may increase from 3,000.00 upwards to 6,000.00 USD. For example 20 transactions each around 3000.00 USD gives you a total income of 6,000.00 USD per month and after establishing a close co-operation with us you'll be able to operate with larger orders and you'll be able to earn more. You will also deduct fees that are related to this job (gasoline, western union fees, bank commissions, etc) from our balance, not from your commissions. At first the checks you will receive will vary from: $500.00 to $3,000.00. We will also send you a 1099 Form for tax deduction on&lt;br /&gt;your part. Our payments will be issued out in your name and you can have them cashed in your existing bank account, we don't accept newly created bank accounts because it slows the cashing process. Deduct your percentage and forward the balance to the company attorney manager via a western union money transfer, the name will be given to you later after cashing a payment.&lt;br /&gt;&lt;br /&gt;This job takes only 3-7 hours per week. You'll have a lot of free time for taking up another job; you'll get good income and a regular job. This job is very challenging and you should understand it. We are looking only for the employee who satisfies our requirements and will be an earnest assistant.&lt;br /&gt;&lt;br /&gt;We have health insurance and the 401K retirement savings plan as well as all the other standard benefits that a major company usually provides. Unfortunately we can only start talking about this after the first month has passed since you're working for us. We consider the first month as a trial period. In any case you do not have to pay for anything in advance; there are no hidden costs for performing this job. Any fee you might encounter will be deducted from our share of the funds before you send it to us.&lt;br /&gt;&lt;br /&gt;You will receive next instructions step by step.&lt;br /&gt;&lt;br /&gt;Unfortunately we cannot setup any interviews now, as we do not have any representatives in US. We will be able to come to meet within the next few months when the new offices will be opened in your area!&lt;br /&gt;&lt;br /&gt;Please let me know if you are still interested. Within 24 hours after we will receive this information we will forward you a copy of the contract you have to fill in, sign and e-mail back to us.&lt;br /&gt;&lt;br /&gt;Ella D. Dickinson&lt;br /&gt;Medline Financial Industries PLC&lt;br /&gt;Euston Road, London, NW1&lt;br /&gt;United Kingdom&lt;br /&gt;FAX 011-44-132-656-8743&lt;br /&gt;&lt;br /&gt;&lt;/blockquote&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-7473068707767028958?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/7473068707767028958/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=7473068707767028958" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/7473068707767028958?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/7473068707767028958?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/bRdrnwC0JNE/wanna-be-mule.html" title="Wanna be a mule?" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>0</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2011/01/wanna-be-mule.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0EGRXo9fSp7ImA9Wx5SGUo.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-1481535604999435677</id><published>2010-08-16T10:18:00.003-04:00</published><updated>2010-08-16T11:13:44.465-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-08-16T11:13:44.465-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="malware analysis" /><title>You never get a second chance...</title><content type="html">Have you ever heard the saying "You never get a second chance to make a first impression"?  The same applies to malware analysis, and information security in general.&lt;br /&gt;&lt;br /&gt;This morning I was doing some research into some malicious spam emails that were coming in.  They were your normal click-on-a-link-and-be-redirected-to-50-sites emails and I had tracked it down to the last site.  After decoding the JS it gave out, I could see the attacks it was going to perform and the URLs it was going to go to.  So close to the malicious executable...so close.&lt;br /&gt;&lt;br /&gt;So I typed the followed at my prompt:&lt;br /&gt;&lt;span style="font-size:85%;"&gt;&lt;br /&gt;&lt;span style="font-style: italic; font-family: courier new;"&gt;curl -D header.txt "http://badsite.com/welcome.php?id=12&amp;amp;pid=10&amp;amp;1=12"&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;See any problems?&lt;br /&gt;&lt;br /&gt;Curl writes anything it downloads to standard output by default.  In other words, since I didn't redirect the output to a file or use the -O option, the file from the malicious site was written to my screen.  Normally, this wouldn't have been such a bad thing except it was gzip compressed, so my screen was filled with binary characters.&lt;br /&gt;&lt;br /&gt;No problem, right?  All I have to do is download it again, this time redirecting.  Here's what happened:&lt;br /&gt;&lt;br /&gt;&lt;span style="font-size:85%;"&gt;&lt;span style="font-style: italic; font-family: courier new;"&gt;curl -D header.txt "http://badsite.com/welcome.php?id=12&amp;amp;pid=10&amp;amp;1=12" &gt; 1&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style: italic; font-family: courier new;"&gt;  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style: italic; font-family: courier new;"&gt;                                 Dload  Upload   Total   Spent    Left  Speed&lt;/span&gt;&lt;br /&gt;&lt;span style="font-style: italic; font-family: courier new;"&gt;  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;0 bytes downloaded?  What happened?&lt;br /&gt;&lt;br /&gt;Many web-based malicious toolkits used by attackers have an option to only allow the attack file to be downloaded once per IP address.  This prevents multiple re-infections on clients and analysts (like me) from exploring their site.  When I initially requested the file and didn't redirect the output, I used my one shot.  The second time I went to download it, the site saw me and didn't let me access it again.  Of course, there are ways around this, but thats for another post.&lt;br /&gt;&lt;br /&gt;So, what did I take away from this?&lt;br /&gt;&lt;br /&gt;1. Everyone makes mistakes.  Hell, I make alot of them.  If anyone tells you they don't, they're lying.  Learn and move on.&lt;br /&gt;2. I need better web download tools.  Well, the tools (eg. curl) work fine.  I'm flawed.  I've already started to create a script that does all that needs done for me.  No more mess ups.&lt;br /&gt;&lt;br /&gt;I hope others can read this and learn from my mistake.  I'd love to hear how others download malicious websites.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-1481535604999435677?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/1481535604999435677/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=1481535604999435677" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/1481535604999435677?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/1481535604999435677?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/t7BqsXMmje4/you-never-get-second-chance.html" title="You never get a second chance..." /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>1</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2010/08/you-never-get-second-chance.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEEAQXk9fyp7ImA9Wx5SF0w.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-5281552559717249611</id><published>2010-08-13T11:05:00.003-04:00</published><updated>2010-08-13T11:17:20.767-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-08-13T11:17:20.767-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="malware analysis" /><category scheme="http://www.blogger.com/atom/ns#" term="training" /><title>Introduction to Malware Analysis Course</title><content type="html">Once again I will be teaching my &lt;span style="font-style: italic;"&gt;Introduction to Malware Analysis&lt;/span&gt; course this year at the &lt;a href="https://www.informationsecuritysummit.org/"&gt;NE Ohio Information Security Summit&lt;/a&gt; that takes place on October 11-15, 2010 in Cleveland, Ohio.  My course is in the &lt;a href="https://www.informationsecuritysummit.org/training_classes.doc"&gt;pre-conference training&lt;/a&gt; and will take place on Oct 12-13.&lt;br /&gt;&lt;br /&gt;The 2 day introduction to malware analysis class is geared to those  who want to learn malware analysis or are just starting out.  We'll  cover all of the basics for malware analysis including setting up your  analysis lab, static analysis and dynamic analysis.  In the end, you'll  walk out of the class with the knowledge of how to take a malware sample  and determine what it does, who it contacts and what risk it poses.&lt;br /&gt;&lt;br /&gt;The class is structured around labs where you'll use the techniques taught to analyse live malware.  Since we will be analyzing actual malware, students will need to bring their own laptops (requirements will be posted closer to the class).&lt;br /&gt;&lt;br /&gt;The end of the class will also feature an analysis contest where students will compete to win some cool prizes.  Last year I gave away a copies of &lt;a href="http://www.boardgamegeek.com/boardgame/10707/hacker-deluxe-edition"&gt;Hacker&lt;/a&gt; and &lt;a href="http://www.boardgamegeek.com/boardgame/30549/pandemic"&gt;Pandemic&lt;/a&gt;...so we'll see what happens this year!&lt;br /&gt;&lt;br /&gt;Even if you don't take my course, I highly recommend &lt;a href="https://www.informationsecuritysummit.org/register.php"&gt;attending the conference&lt;/a&gt;.  Its an amazing conference for the price ($300 until 9/15).  There are lots of great speakers (many of which speak at Black Hat, Defcon, Shmoocon, etc.).&lt;br /&gt;&lt;br /&gt;Look forward to seeing you there!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-5281552559717249611?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/5281552559717249611/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=5281552559717249611" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/5281552559717249611?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/5281552559717249611?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/nst4fQzUmXQ/introduction-to-malware-analysis-course.html" title="Introduction to Malware Analysis Course" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>0</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2010/08/introduction-to-malware-analysis-course.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CE8DSHg6cSp7ImA9WxFQF0s.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-5100433984110744196</id><published>2010-05-12T13:10:00.006-04:00</published><updated>2010-05-13T11:01:19.619-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-05-13T11:01:19.619-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="malware" /><category scheme="http://www.blogger.com/atom/ns#" term="sandnet" /><title>Simulating the User Experience: Part 3</title><content type="html">In the first two parts of this blog series, I detailed an issue I found where not all of the user environment variables were set for a program run with winexe.  This was causing an issue during analysis of some malware since the samples were looking for those variables.  As a work-around, a batch script was uploaded to the Windows sandbox and scheduled to run.  When the scheduled job ran, all of the environment variables were set and the malware ran as it normally would.&lt;br /&gt;&lt;br /&gt;The whole situation got me thinking - are public sandboxes setting all of the environment variables?  As was seen, some malware rely on these variables and if they aren't set the malware won't run.  If someone were to use a public sandnet to test malware that relies on these variables and the malware didn't run, they could be under the false impression that the program is benign.&lt;br /&gt;&lt;br /&gt;Before I go on I should state that this post is not a knock against public sandboxes.  They provide a great service to the security community.  I did not do this to find any weaknesses in them to exploit or publish maliciously.  My goal here was to determine which sandboxes, if any, miss some variables that may be required for malware to run.&lt;br /&gt;&lt;br /&gt;To test this, I wrote a program that would obtain the environment variables and write each one to its own registry key/value pair.  Since the public sandboxes report any registry modifications made by the program, I would be able to see all of the environment variables available to the program.  This program was then uploaded to a number of different public sandboxes and the results analyzed.  The sandboxes I used were &lt;a href="http://anubis.iseclab.org/"&gt;Anubis&lt;/a&gt;, &lt;a href="http://camas.comodo.com/"&gt;Comodo&lt;/a&gt;, &lt;a href="http://mwanalysis.org/"&gt;CWSandbox&lt;/a&gt;, &lt;a href="http://www.joebox.org/"&gt;Joebox&lt;/a&gt;, &lt;a href="http://www.threatexpert.com/"&gt;ThreatExpert&lt;/a&gt;, &lt;a href="https://aerie.cs.berkeley.edu/submitsample-d.php"&gt;BitBlaze&lt;/a&gt; and the &lt;a href="http://www.norman.com/security_center/security_tools/submit_file/en"&gt;Norman Sandbox&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;In my testing, none of the sandboxes set all 30 of the environment variables I originally saw in my test.  BitBlaze set 29; Anubis, Comodo, CWSandbox and Joebox set 28; and the Norman Sandbox only set 16.  For some reason, ThreatExpert did not report anything back from my program - this could be a problem with my program or some type of security measure on their part.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;* Note: I will not say which variables were and were not set. That information could be used by malware to determine it was running in one of these sandnets and that is not my purpose.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Due to the way the malware is executed in my system, I think that having only 28 or 29 environment variables is a perfectly normal variation.  Therefore, my conclusion to all of this is that with the exception of Norman Sandbox, the sandnets appear to be setting the variables they should and represent a likely variation in the systems malware would run on.&lt;br /&gt;&lt;br /&gt;As for Norman Sandbox, they are setting a small number of environment variables.  This is perhaps a likely scenario for some systems.  However, the variation of such a small amount being set would concern me as I don't know if all malware would work as it normally would.  Only further testing can tell.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-5100433984110744196?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/5100433984110744196/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=5100433984110744196" title="9 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/5100433984110744196?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/5100433984110744196?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/yaT1vyTC3NY/simulating-user-experience-part-3.html" title="Simulating the User Experience: Part 3" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>9</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2010/05/simulating-user-experience-part-3.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkcERHg4cCp7ImA9WxFQFUQ.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-4762971707337222308</id><published>2010-05-08T11:38:00.008-04:00</published><updated>2010-05-11T11:00:05.638-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-05-11T11:00:05.638-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="malware analysis" /><title>Simulating the User Experience: Part 2</title><content type="html">&lt;a href="http://secshoggoth.blogspot.com/2010/05/simulating-user-experience-part-1.html"&gt;In my last post&lt;/a&gt; I discussed the problem I found with &lt;a href="http://eol.ovh.org/winexe/"&gt;winexe&lt;/a&gt; and how it did not set all the Windows environment variables needed to simulate a complete user experience.  This problem was preventing some malware from running in my malware analysis sandnet - a problem I needed to overcome.&lt;br /&gt;&lt;br /&gt;The way I looked at it, I had 3 options:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Modify the source code for winexe to get it to work as I wanted.  However, this was more than I wanted to do at this time.  Maybe later.&lt;/li&gt;&lt;li&gt;Use a program like &lt;a href="http://webjob.sourceforge.net/WebJob/"&gt;webjob&lt;/a&gt; to provide another means to remotely execute the program.  However, this would require me to modify the Windows analysis host which, for reasons I won't go into, is a huge PITA.  Any solution that required me to modify the host was out for now.&lt;/li&gt;&lt;li&gt;Figure out a way to remotely execute the malware on the Windows system using already present tools and still get the user environment I wanted.&lt;/li&gt;&lt;/ul&gt;I decided to start with the third option.  I knew I couldn't use winexe to directly execute the malware as I wouldn't get the correct environment variables set.  But, what if I used winexe to execute another program to launch the malware?&lt;br /&gt;&lt;br /&gt;Using winexe to run 'cmd /c malware.exe' was out as this was the method I was using before.  I then tried creating a batch script to run the malware and executing it with winexe.  No luck there either; the environment variables weren't created.  Finally, I had an idea...what if I scheduled a job to run the malware?  If I scheduled it as the user it should inherit all of the correct variables and run correctly.&lt;br /&gt;&lt;br /&gt;To test it out I created a batch script (named test.bat) in the Windows system that would run &lt;span style="font-style: italic;"&gt;set&lt;/span&gt; and redirect the output into a file.  I then ran the following command (from the Linux box):&lt;br /&gt;&lt;blockquote&gt;winexe -U administrator%mypass //192.168.1.5 'schtasks /create /tn testjob /tr c:\temp\test.bat /sc minute /mo 1 /ru administrator /rp mypass'&lt;br /&gt;&lt;/blockquote&gt;&lt;br /&gt;Success!!!  When the script ran and dumped the environment variables into a file, all 30 were there!  The next step was to create a script to run the malware in the system.&lt;br /&gt;&lt;br /&gt;The automation script was modified to upload the malware to the Windows box along with a batch script that performs the following commands:&lt;br /&gt;&lt;blockquote&gt;schtasks /delete /tn jobname /f&lt;br /&gt;start c:\path\to\malware.exe&lt;br /&gt;&lt;/blockquote&gt;The automation script then schedules a job to run the uploaded script.  When the scheduled job kicks off, the batch file runs.  The batch file deletes the scheduled job and run the malware. &lt;br /&gt;&lt;br /&gt;Why delete the scheduled job?  When scheduling the job, it is scheduled to run every minute.  By deleting the scheduled job there's no worry the malware will run more than once.  Why schedule it to run every minute?  Call it paranoia.  :)&lt;br /&gt;&lt;br /&gt;After making the modifications to my automation script and testing it, I ran it with the Koobface sample that started all my problems and...success!  The results showed the sample ran correctly, dropped the right files and set the right registry keys.   Tests with additional malware have shown that its working correctly as well.&lt;br /&gt;&lt;br /&gt;This test got me thinking...how do publicly available sandnets work?  Are they setting the environment settings correctly?  I'll discuss this in the part 3 of this post.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-4762971707337222308?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/4762971707337222308/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=4762971707337222308" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/4762971707337222308?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/4762971707337222308?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/SI134Tkvdj4/simulating-user-experience-part-2.html" title="Simulating the User Experience: Part 2" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>1</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2010/05/simulating-user-experience-part-2.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUMER34-cSp7ImA9WxFQFEQ.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-3091548515822757331</id><published>2010-05-08T10:04:00.012-04:00</published><updated>2010-05-10T09:16:46.059-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-05-10T09:16:46.059-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="malware" /><title>Simulating the User Experience: Part 1</title><content type="html">Part of malware analysis, especially automated malware analysis, is to simulate the user environment as closely as possible.  After all, our goal is to determine how malware behaves when it is run by a user.  For the last few months I've worked on an automated malware analysis system which I thought did just that.&lt;br /&gt;&lt;br /&gt;Let me explain my automated analysis system.  It is similar to the one I described in &lt;a href="http://secshoggoth.blogspot.com/2009/05/automating-malware-analysis-article.html"&gt;my Hakin9 articles last year&lt;/a&gt;.  Basically I have a host system running Linux that executes an automation script.  The automation script starts up a VM, launches some monitoring tools, uploads and executes the malware, records the results and performs cleanup.  In all, it takes about 5-7 minutes per malware, depending on the settings I am running.  So far it performed extremely well and cut my analysis time down dramatically.&lt;br /&gt;&lt;br /&gt;Imagine my frustration this week when I ran a new Koobface sample in it only to find the malware didn't do anything.  It would launch, perform some start-up operations, then exit.  No registry modifications, no process injection, no network traffic.  However, when I would manually launch it or run it through &lt;a href="http://www.threatexpert.com/"&gt;ThreatExpert&lt;/a&gt;, it would run fine.&lt;br /&gt;&lt;br /&gt;In looking closer, I found out that the malware was trying to place a copy of itself in the %APPDATA% directory.  Since %APPDATA% is an environment variable for the user, it should have been set - or so I thought.&lt;br /&gt;&lt;br /&gt;I took a step back and started to examine the method I was using to execute the malware.  My "host" system which executes the automation scripts runs Linux.  In order to execute the malware in the Windows system, &lt;a href="http://www.samba.org/samba/docs/man/manpages-3/smbclient.1.html"&gt;smbclient&lt;/a&gt; is used to upload the malware and &lt;a href="http://eol.ovh.org/winexe/"&gt;winexe&lt;/a&gt; is used to execute it.   After some thought, I came up with a theory that winexe was not setting all of the environment variables when it executed malware.  I was right.&lt;br /&gt;&lt;br /&gt;It turns out that in a default Windows XP SP3 system, 30 environment variables are set.  With the way I was running winexe (--system --interactive=1), only 22 of the variables were set - %APPDATA%, %CLIENTNAME%, %HOMEDRIVE%, %HOMEPATH%, %LOGONSERVER%, %SESSIONNAME%, %USERDOMAIN% and %USERNAME% are missing.&lt;br /&gt;&lt;br /&gt;To make sure it wasn't because of the way I was running winexe, I ran a number of tests.   Each test consisted of running winexe with different settings.  The command that was run was "cmd.exe /c set &gt; outfile".  To be fair, I also tested &lt;a href="http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx"&gt;PsExec&lt;/a&gt; (from another Windows system).  These are the results I found:&lt;br /&gt;&lt;br /&gt;&lt;table border="1"&gt;&lt;tbody&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th align="center" colspan="3"&gt;winexe&lt;/th&gt;&lt;/tr&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;no settings&lt;/th&gt;&lt;th&gt;interactive&lt;/th&gt;&lt;th&gt;interactive + system&lt;/th&gt;&lt;/tr&gt;&lt;tr align="center"&gt;&lt;td align="LEFT"&gt;%APPDATA%&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;/tr&gt;&lt;tr align="center"&gt;&lt;td align="LEFT"&gt;%CLIENTNAME%&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;/tr&gt;&lt;tr align="center"&gt;&lt;td align="LEFT"&gt;%HOMEDRIVE%&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;/tr&gt;&lt;tr align="center"&gt;&lt;td align="LEFT"&gt;%HOMEPATH%&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;/tr&gt;&lt;tr align="center"&gt;&lt;td align="LEFT"&gt;%LOGONSERVER% &lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;/tr&gt;&lt;tr align="center"&gt;&lt;td align="LEFT"&gt;%SESSIONNAME%&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;/tr&gt;&lt;tr align="center"&gt;&lt;td align="LEFT"&gt;%USERDOMAIN%&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;/tr&gt;&lt;tr align="center"&gt;&lt;td align="LEFT"&gt;%USERNAME%&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;br /&gt;&lt;br /&gt;&lt;table border="1"&gt;&lt;tbody&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th align="center" colspan="3"&gt;psexec&lt;/th&gt;&lt;/tr&gt;&lt;tr&gt;&lt;th&gt;&lt;/th&gt;&lt;th&gt;no settings&lt;/th&gt;&lt;th&gt;interactive&lt;/th&gt;&lt;th&gt;interactive + system&lt;/th&gt;&lt;/tr&gt;&lt;tr align="center"&gt;&lt;td align="LEFT"&gt;%APPDATA%&lt;/td&gt;&lt;td&gt;X&lt;/td&gt;&lt;td&gt;X&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;/tr&gt;&lt;tr align="center"&gt;&lt;td align="LEFT"&gt;%CLIENTNAME%&lt;/td&gt;&lt;td&gt;X&lt;/td&gt;&lt;td&gt;X&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;/tr&gt;&lt;tr align="center"&gt;&lt;td align="LEFT"&gt;%HOMEDRIVE%&lt;/td&gt;&lt;td&gt;X&lt;/td&gt;&lt;td&gt;X&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;/tr&gt;&lt;tr align="center"&gt;&lt;td align="LEFT"&gt;%HOMEPATH%&lt;/td&gt;&lt;td&gt;X&lt;/td&gt;&lt;td&gt;X&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;/tr&gt;&lt;tr align="center"&gt;&lt;td align="LEFT"&gt;%LOGONSERVER% &lt;/td&gt;&lt;td&gt;X&lt;/td&gt;&lt;td&gt;X&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;/tr&gt;&lt;tr align="center"&gt;&lt;td align="LEFT"&gt;%SESSIONNAME%&lt;/td&gt;&lt;td&gt;X&lt;/td&gt;&lt;td&gt;X&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;/tr&gt;&lt;tr align="center"&gt;&lt;td align="LEFT"&gt;%USERDOMAIN%&lt;/td&gt;&lt;td&gt;X&lt;/td&gt;&lt;td&gt;X&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;/tr&gt;&lt;tr align="center"&gt;&lt;td align="LEFT"&gt;%USERNAME%&lt;/td&gt;&lt;td&gt;X&lt;/td&gt;&lt;td&gt;X&lt;/td&gt;&lt;td&gt;&amp;nbsp;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;It turns out that no matter what options you use, winexe does not set the environment variables above.  Note that I also ran winexe with the --runas option and got the same results.  PsExec sets all of the environment variables, except when you specify it to run as SYSTEM.  This makes sense as most of those variables are used to specify user settings and SYSTEM would not have those.&lt;br /&gt;&lt;br /&gt;Obviously, winexe wasn't going to cut it any more because it wasn't setting a complete user environment which, in turn, was preventing malware from running.  So, what to do?  Winexe was my only way to remotely execute a program on a Windows system from a Linux system (without modifying the Windows system and installing other programs).   To find out what I did, you'll have to stay tuned for part 2!  :)&lt;br /&gt;&lt;br /&gt;As a side note, if anyone knows of another program similar to winexe, please let me know.  Also, if anyone knows of a way to get winexe to run correctly, I'd love to hear it.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-3091548515822757331?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/3091548515822757331/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=3091548515822757331" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/3091548515822757331?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/3091548515822757331?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/UbZ35DPwKMw/simulating-user-experience-part-1.html" title="Simulating the User Experience: Part 1" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>2</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2010/05/simulating-user-experience-part-1.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEcFQnY-fyp7ImA9WxFRE0Q.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-111746282479110335</id><published>2010-04-27T13:35:00.006-04:00</published><updated>2010-04-27T14:13:33.857-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-04-27T14:13:33.857-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="PDF" /><category scheme="http://www.blogger.com/atom/ns#" term="malware analysis" /><title>/Launch Malicious PDF</title><content type="html">Wow - I'm posting!! :)&lt;br /&gt;&lt;br /&gt;Today I, and others around the Internet, received an email that stated:&lt;br /&gt;&lt;blockquote&gt;Subject: setting for your mailbox are changed&lt;br /&gt;&lt;br /&gt;SMTP and POP3 servers for &lt;span style="font-style: italic;"&gt;YOUREMAILADDRHERE&lt;/span&gt; mailbox are&lt;br /&gt;changed. Please carefully read the attached instructions&lt;br /&gt;before updating settings.&lt;/blockquote&gt;The email had a PDF attached to it.  Given the &lt;a href="http://www.trustedsource.org/blog/404/Surrounded-by-Malicious-PDFs"&gt;number of malicious PDFs&lt;/a&gt; that have been seen lately, this was likely a bad thing.&lt;br /&gt;&lt;br /&gt;Examining the PDF with &lt;a href="http://blog.didierstevens.com/programs/pdf-tools/"&gt;Didier Steven's pdfid.py&lt;/a&gt; showed that there was an OpenAction in the PDF, but no JavaScript.  Interesting.  Using pdf-parser.py, the object pointed to by the OpenAction was examined:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_4x76DeWu9xs/S9ckqd6_pUI/AAAAAAAAAFA/vyM3bPyyev0/s1600/blog1.png"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 204px;" src="http://2.bp.blogspot.com/_4x76DeWu9xs/S9ckqd6_pUI/AAAAAAAAAFA/vyM3bPyyev0/s320/blog1.png" alt="" id="BLOGGER_PHOTO_ID_5464876984842560834" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;This shows that the &lt;a href="http://blogs.adobe.com/adobereader/2010/04/didier_stevens_launch_function.html"&gt;/Launch vulnerability/feature of PDFs&lt;/a&gt; is being used to drop a VB script and execute it.  What is interesting is the VB script (named script.vbs) parses the original PDF for another VBS to run!  A quick look at the PDF finds the other VBS:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_4x76DeWu9xs/S9cn1tpQ0zI/AAAAAAAAAFI/KzJrWFnNCXI/s1600/full.png"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 282px;" src="http://4.bp.blogspot.com/_4x76DeWu9xs/S9cn1tpQ0zI/AAAAAAAAAFI/KzJrWFnNCXI/s320/full.png" alt="" id="BLOGGER_PHOTO_ID_5464880476576600882" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;(The image above has had code removed for brevity.)&lt;br /&gt;&lt;br /&gt;The new VBS (named batscript.vbs) contains an executable broken up into its hex bytes.  The script will write each byte out to a file named game.exe and then will execute it.  After executing, it sleeps for 3 seconds then covers its tracks by deleting game.exe, batscript.vbs and script.vbs.&lt;br /&gt;&lt;br /&gt;game.exe, meanwhile, will copy itself to &lt;span style="font-style: italic;"&gt;c:\program files\microsoft common\svchost.exe&lt;/span&gt; and set itself up to run in the registry whenever explorer.exe runs.&lt;br /&gt;&lt;br /&gt;While I know the /Launch vulnerability has been exploited recently, this is the first I've seen on a mass-email scale (&lt;a href="http://www.sophos.com/blogs/sophoslabs/?p=9413"&gt;but isn't the first ever&lt;/a&gt;).  I'm sure we'll be seeing more of these as time goes on.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-111746282479110335?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/111746282479110335/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=111746282479110335" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/111746282479110335?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/111746282479110335?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/S2YAlX88m5Q/launch-malicious-pdf.html" title="/Launch Malicious PDF" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_4x76DeWu9xs/S9ckqd6_pUI/AAAAAAAAAFA/vyM3bPyyev0/s72-c/blog1.png" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2010/04/launch-malicious-pdf.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUIMQ308eSp7ImA9WxBXGUo.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-1958402826051315897</id><published>2010-01-31T17:25:00.004-05:00</published><updated>2010-01-31T17:39:42.371-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-01-31T17:39:42.371-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="APT" /><title>Who are the APT targets?</title><content type="html">I've been publicly quiet on the whole APT discussions as of late, with good reason.  There are lots of blogs out there which share (and do not share) my opinion, so there is no need for me to chime into the myriad of voices out there.&lt;br /&gt;&lt;br /&gt;However, an anonymous comment on one of the &lt;a href="http://http://taosecurity.blogspot.com/2010/01/two-dimensional-thinking-and-apt.html"&gt;recent taosecurity posts&lt;/a&gt; brought up a point that I have not seen anyone else talk about.  The comment stated:&lt;br /&gt;&lt;br /&gt;&lt;blockquote style="font-family: georgia;"&gt;&lt;span style="font-size:85%;"&gt;Reading the Mandiant Report, we see:&lt;br /&gt;&lt;br /&gt;1.) Government&lt;br /&gt;2.) Defense Contractors&lt;br /&gt;3.) Fortune XXX acquiring a Chinese compnay&lt;br /&gt;4.)  A Law Firm involved in a Chinese civil litigation case&lt;br /&gt;5.)  A non-profit trying to spread "democracy and free enterprise in China" (maybe they could also do that in the USA).&lt;br /&gt;&lt;br /&gt;Look, it doesn't take Arthur Conan Doyle to piece together the storyline here. This clearly isn't "everyone's problem".&lt;span style="font-weight: bold;"&gt; It's a problem for those that are seen as an enemy of certain nation-states.&lt;/span&gt;&lt;/span&gt;&lt;/blockquote&gt;The part I'd like to focus on is the last statement.  The APT problem is &lt;span style="font-weight: bold; font-style: italic;"&gt;not&lt;/span&gt; only the problem of those seen as the enemy of certain nation states.  It is the problem of everyone.&lt;br /&gt;&lt;br /&gt;If you read Mandiant's excellent report, you will see specific examples (mentioned in the comment above) which are documented APT targets.  Yes, these are what you think of as nation-state attack targets.&lt;br /&gt;&lt;br /&gt;However, I have personally seen the APT attack and compromise systems in networks which have no ties to that nation-state and you would not consider enemies of that nation-state (or any for that matter).  In these cases, the organizations were small-medium sized companies whose systems were compromised in order to be used as command and control systems for the APT's backdoors.&lt;br /&gt;&lt;br /&gt;Of course, there are those that will say that this is the same technique that all attackers use - compromise less secure systems and use them as a go-between to attack other systems.  And I will 100% agree with them on that!  But that re-enforces my point as well!  No one is safe from attack from APT and therefore there should be no reason why organizations should not take every reasonable precaution to against these (or any) attackers and learn as much as they can.&lt;br /&gt;&lt;br /&gt;Yes, there will be those companies that use the term APT as a marketing tool.  Yes, there will be those who say this is a limited threat to some organizations (and to some extent I agree with that).  But in the end, it is a real threat that exists and any organization that does not perform the due diligence to at least learn about the potential threat will be at a disadvantage when they do get attacked; maybe not by the APT but by the next threat.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-1958402826051315897?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/1958402826051315897/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=1958402826051315897" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/1958402826051315897?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/1958402826051315897?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/2WoesrmfuZg/who-are-apt-targets.html" title="Who are the APT targets?" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>3</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2010/01/who-are-apt-targets.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkQFSH86cSp7ImA9WxBXEUw.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-1737973593199594649</id><published>2010-01-21T16:43:00.002-05:00</published><updated>2010-01-21T16:45:19.119-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-01-21T16:45:19.119-05:00</app:edited><title>Funky Ivy</title><content type="html">I was testing out some functionality with the Poison Ivy backdoor today when I grabbed this screenshot.  Very psychedelic!&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_4x76DeWu9xs/S1jK1su-1BI/AAAAAAAAAE4/je2Qt0bfVeo/s1600-h/pi-funky.jpg"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 400px; height: 253px;" src="http://3.bp.blogspot.com/_4x76DeWu9xs/S1jK1su-1BI/AAAAAAAAAE4/je2Qt0bfVeo/s400/pi-funky.jpg" alt="" id="BLOGGER_PHOTO_ID_5429312374685226002" border="0" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-1737973593199594649?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/1737973593199594649/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=1737973593199594649" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/1737973593199594649?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/1737973593199594649?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/Ncx25U15bO0/funky-ivy.html" title="Funky Ivy" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/_4x76DeWu9xs/S1jK1su-1BI/AAAAAAAAAE4/je2Qt0bfVeo/s72-c/pi-funky.jpg" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2010/01/funky-ivy.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkcMR3wyeip7ImA9WxBQE0k.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-242706351765803607</id><published>2010-01-12T18:32:00.004-05:00</published><updated>2010-01-12T18:48:06.292-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-01-12T18:48:06.292-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="malware analysis" /><category scheme="http://www.blogger.com/atom/ns#" term="presentation" /><title>Malware Analysis in the Incident Response Process followup</title><content type="html">I just finished giving my webcast of &lt;a href="http://www.brighttalk.com/webcasts/7977/attend"&gt;Malware Analysis in the Incident Response Process&lt;/a&gt; at &lt;a href="http://www.brighttalk.com/"&gt;brighttalk.com&lt;/a&gt;.  A few questions came in after the presentation ended so I'll answer them here and hopefully those who asked will see it.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;You indicated it is inevitable to get malware.  What is the best prevention…having dedicated PCs for missions critical functions (e.g. online banking)?&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;I honestly believe that the best way to prevent getting malware on systems is to run users with reduced privileges.  I have seen first hand where restricting what activities a user can do on their system (install software, etc) will significantly decrease the amount of malware compromises you have.&lt;br /&gt;&lt;br /&gt;Of course, there are other options as well.  A good defense in depth strategy will make it more difficult for malware to compromise your systems.  Using up-to-date AV on the desktop and your email systems, restricting Internet access and requiring all web-traffic to go through filtering proxy servers will help.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Are there any books you would recommend for beginners to learn malware analysis?&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;There are lots of great books out there that I would recommend to anyone who wants to learn malware analysis.  The following are just a few of the ones I've read.&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.malwareforensics.com/Home_Page.html"&gt;Malware Forensics&lt;/a&gt; by Aquilina, Casey and Malin&lt;br /&gt;&lt;a href="http://www.peterszor.com/"&gt;The Art of Computer Virus Research and Defense&lt;/a&gt; by Peter Szor&lt;br /&gt;&lt;a href="http://zeltser.com/malware-book/"&gt;Malware: Fighting Malicious Code&lt;/a&gt; by Skoudis and Zeltser&lt;br /&gt;&lt;br /&gt;There are others, but these are a good start.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Can you post a recent example of an analysis?&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Unfortunately, I do not have one.  However, I recommend checking out the results from the &lt;a href="http://malwarechallenge.info"&gt;2008 Malware Challenge&lt;/a&gt; for some analysis reports.  I will also try to post something in the next few weeks.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Thanks to those who listened to the webcast.  If you have any other questions, feel free to post them in the comments or send me an email!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-242706351765803607?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/242706351765803607/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=242706351765803607" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/242706351765803607?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/242706351765803607?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/EQokhWIQG6U/malware-analysis-in-incident-response_12.html" title="Malware Analysis in the Incident Response Process followup" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>1</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2010/01/malware-analysis-in-incident-response_12.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUANSXsycSp7ImA9WxBRGUs.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-3709220116221045592</id><published>2010-01-08T11:15:00.003-05:00</published><updated>2010-01-08T11:23:18.599-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-01-08T11:23:18.599-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="malware analysis" /><category scheme="http://www.blogger.com/atom/ns#" term="presentation" /><title>Malware Analysis in the Incident Response Process</title><content type="html">Next week I'll be giving an online presentation at BrightTalk on Malware Analysis in the Incident Response Process.  The description of the talk is:&lt;br /&gt;&lt;blockquote&gt;Malware has become the primary vector of compromise within organisations.  Due to this, it has become necessary for incident response teams to have the ability to perform in-house malware analysis.  This presentation will discuss how malware analysis can benefit an organisation and what options are available.&lt;/blockquote&gt;The talk is scheduled for next Tuesday, January 12 at 6PM EST and is part of their &lt;a href="http://www.brighttalk.com/summit/intrusionprevention"&gt;Intrusion Prevention Summit&lt;/a&gt;.  The summit has alot of interesting talks all day, so I recommend checking it out.&lt;br /&gt;&lt;br /&gt;To attend my talk, you can go to the following URL:&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.brighttalk.com/webcasts/7977/attend"&gt;http://www.brighttalk.com/webcasts/7977/attend&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Hope you can join!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-3709220116221045592?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/3709220116221045592/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=3709220116221045592" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/3709220116221045592?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/3709220116221045592?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/MDaVaIaaKI8/malware-analysis-in-incident-response.html" title="Malware Analysis in the Incident Response Process" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>1</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2010/01/malware-analysis-in-incident-response.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkIHQn48eyp7ImA9WxBTFkk.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-5834769309623001110</id><published>2009-12-12T14:56:00.005-05:00</published><updated>2009-12-12T15:08:53.073-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-12-12T15:08:53.073-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="conference" /><title>SANS Incident Detection Summit Wrapup</title><content type="html">This past week I was able to attend the&lt;a href="http://www.sans.org/incident-detection-summit-2009/?utm_source=web&amp;amp;utm_medium=text-ad&amp;amp;utm_content=FE_Links_Homepage_detectSum_09_fe_list_hmpg&amp;amp;utm_campaign=SANS_WhatWorks_in_Incident_Detection_Summit_2009&amp;amp;ref=47654"&gt; SANS Incident Detection Summit&lt;/a&gt; in Washington DC.  [&lt;span style="font-style: italic;"&gt;In full disclosure, I should point out that I was on two of the panels so I did not have to pay admission to attend.&lt;/span&gt;]  I'll fully admit that the summit blew away all expectations I had of it!&lt;br /&gt;&lt;br /&gt;The SANS 'What Works' Summits are not like their typical SANS conferences.  The summits, or at least this one, are a single track where each session will either have a briefing (a presentation by someone) or a panel of experts discussing a specific topic.  The audience gets to participate by asking questions via yellow note cards that are given to the moderator.  The moderator then chooses which questions to ask.&lt;br /&gt;&lt;br /&gt;Many of the briefings and panels were amazing and gave great insights into different techniques to detect bad guys.  if I had to choose my favorites they probably were Seth Hall discussing Bro, the Honeynet Project briefing and AAron Walters and Brendan Dolan-Gavitt's talk on memory analysis.  Matt Richard's after-hours talk on analyzing PDF and office malware was amazing as well.&lt;br /&gt;&lt;br /&gt;As great as the panels and briefings were, the best part was being able to talk to the people afterwards.  The whole summit had less than 100 people (I'm guessing here) and everyone was willing and happy to talk.  Where else do you get a chance to sit down and talk with people such as AAron Walters, Matt Jonkman, Andre Ludwig, Bamm Visscher, David Bianco, Ken Bradley, Matt Olney and Ken Dunham in one place?&lt;br /&gt;&lt;br /&gt;I will definitely be coming back next year if I can.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-5834769309623001110?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/5834769309623001110/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=5834769309623001110" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/5834769309623001110?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/5834769309623001110?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/g7Vitfj9yi4/sans-incident-detection-summit-wrapup.html" title="SANS Incident Detection Summit Wrapup" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>0</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2009/12/sans-incident-detection-summit-wrapup.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkQFQ3k_fyp7ImA9WxNaEE8.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-461183263676362041</id><published>2009-11-23T20:52:00.003-05:00</published><updated>2009-11-23T21:05:12.747-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-11-23T21:05:12.747-05:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="conference" /><title>SANS Intrusion Detection Summit</title><content type="html">&lt;div&gt;&lt;span class="Apple-style-span"  style="font-family:arial;"&gt;On December 9th and 10th I will be at the SANS Intrusion Detection Summit in Washington DC.   speaking on two different panels, &lt;u&gt;UNIX and Windows: Tools and Techniques&lt;/u&gt; and &lt;u&gt;CIRTs and MSSPs&lt;/u&gt;.  I highly recommend attending if you can.  There are going to be a number of amazing speakers there.  (Yes, I'm not sure how I got on the panels either.)&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class="Apple-style-span"  style="font-family:arial, serif;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;span class="Apple-style-span" style="font-family: arial, serif; font-size: medium; "&gt;Following the success of the 2008 and 2009 editions of the SANS WhatWorks in Forensics and Incident Response Summits, SANS is teaming with Richard Bejtlich to create a practioner-focused event dedicated to incident detection operations. The SANS Incident Detection Summit will share tools, tactics, and techniques practiced by some of the world's greatest incident detectors in two full days of content consisting of keynotes, expert briefings, and dynamic panels.&lt;/span&gt;&lt;/div&gt;&lt;div&gt;&lt;p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica"&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;&lt;p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica"&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;Hope to see you there!&lt;/span&gt;&lt;/p&gt;&lt;p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica"&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;&lt;p style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica"&gt;&lt;a href="http://www.sans.org/incident-detection-summit-2009/"&gt;&lt;span class="Apple-style-span" style="font-size: medium;"&gt;http://www.sans.org/incident-detection-summit-2009/&lt;/span&gt;&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-461183263676362041?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/461183263676362041/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=461183263676362041" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/461183263676362041?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/461183263676362041?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/uzg1c9eCJoA/sans-intrusion-detection-summit.html" title="SANS Intrusion Detection Summit" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>2</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2009/11/sans-intrusion-detection-summit.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEYMRXo7eCp7ImA9WxNVEkw.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-1547013369612028716</id><published>2009-10-22T08:30:00.002-04:00</published><updated>2009-10-22T08:56:24.400-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-22T08:56:24.400-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="malware" /><category scheme="http://www.blogger.com/atom/ns#" term="malware analysis" /><title>Tracking the Defenders</title><content type="html">I've been working hard the last few weeks to get my malware analysis class ready, but something popped up that got me thinking.  In the last few days a number of blogs have reported about avtracker.info, a site which is tracking the IP addresses that AV companies use to research malware.&lt;br /&gt;&lt;br /&gt;According to the supposed &lt;a href="http://www.peterkleissner.com/"&gt;author&lt;/a&gt;*, the reason this site is in existence is:&lt;br /&gt;&lt;blockquote&gt;If you DDoS them, then you will lame down the whole AV business, then there won’t be any new detections for the time you cut them from the internet. The IP list is also useful for software that downloads something from the internet, in order to hide it from automatic analyzers like Anubis. You can simply exit the program when the IP matches with one of the AV list – and then your program stays secure from automatic analysis.&lt;/blockquote&gt;I have to admit that I'm not surprised at these reasons, or even that this is happening.  In fact, I suspect its been happening a long time and this is just the first time a public list has been made.&lt;br /&gt;&lt;br /&gt;Think about it - we watch where the attackers are coming from.  We have honeypots, &lt;a href="http://feeds.dshield.org/block.txt"&gt;block lists&lt;/a&gt;, and share information amongst each other - why should we think the attackers are doing any differently?&lt;br /&gt;&lt;br /&gt;This does illustrate a good point, however.  In my class I teach that you should never allow malware you are analyzing to contact its home servers from your organization.  When you do, the attackers can figure out where you are coming from and, in the best case, block your access.  In the worst case you would be on the receiving end of a DDoS attack.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;* I say supposed because I have no proof one way or another.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-1547013369612028716?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/1547013369612028716/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=1547013369612028716" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/1547013369612028716?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/1547013369612028716?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/rnzaUBDyaRQ/tracking-defenders.html" title="Tracking the Defenders" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>2</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2009/10/tracking-defenders.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DU8DSXY4cSp7ImA9WxNQEkU.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-1038109990670694787</id><published>2009-09-18T11:20:00.003-04:00</published><updated>2009-09-18T11:31:18.839-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-18T11:31:18.839-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="hacks" /><title>Quick Backup Script</title><content type="html">I often create scripts and programs (Perl mostly) to help me do things.  When I'm developing these scripts, I will typically write a chunk of code, test it, add more functionality, test it, rinse, repeat.&lt;br /&gt;&lt;br /&gt;However, there are times where I'll delete a chunk of code to try something different and end up breaking my entire script.  Of course, when this happens I don't have a backup of the old code available to go back to.&lt;br /&gt;&lt;br /&gt;To help me, I made this small script which will backup a file given to it to a directory.  All it does is copy the file to a backup directory and tack on a date string to the end of it so every backup copy is unique.  Yes, this is a simple copy, but it makes it nice to have to do things quickly.&lt;br /&gt;&lt;br /&gt;&lt;blockquote  style="font-family:courier new;"&gt;&lt;span style="font-size:85%;"&gt;#!/bin/bash&lt;br /&gt;&lt;br /&gt;# quick script to backup files&lt;br /&gt;&lt;br /&gt;DEFAULTDIR=${HOME}/backup&lt;br /&gt;DATE=`date +%s`&lt;br /&gt;if [ $# -lt 1 ] ; then&lt;br /&gt;    echo $0 file-to-backup [path to backup dir]&lt;br /&gt;    exit&lt;br /&gt;fi&lt;br /&gt;&lt;br /&gt;# set the backup dir location&lt;br /&gt;BACKUPDIR=${2:-$DEFAULTDIR}&lt;br /&gt;&lt;br /&gt;if [ ! -d ${BACKUPDIR} ] ; then&lt;br /&gt;    echo ${BACKUPDIR} did not exist. Creating.&lt;br /&gt;    mkdir -p ${BACKUPDIR}&lt;br /&gt;fi&lt;br /&gt;&lt;br /&gt;# make sure the file exists&lt;br /&gt;if [ ! -f $1 ] ; then&lt;br /&gt;    echo $1 does not exist.&lt;br /&gt;    exit&lt;br /&gt;fi&lt;br /&gt;&lt;br /&gt;cp $1 $BACKUPDIR/${1}-${DATE}&lt;br /&gt;if [ $? -eq 0 ] ; then&lt;br /&gt;    echo Successfully copied $1 to $BACKUPDIR/${1}-${DATE}&lt;br /&gt;else&lt;br /&gt;    echo Error copying $1 to $BACKUPDIR/${1}-${DATE}&lt;br /&gt;fi&lt;/span&gt;&lt;/blockquote&gt;&lt;br /&gt;I just copied it to /usr/local/bin, called it &lt;span style="font-style: italic;"&gt;myback&lt;/span&gt;, and chmod +x'd it.  Now, whenever I want to backup a script quickly I just run "myback script".&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-1038109990670694787?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/1038109990670694787/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=1038109990670694787" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/1038109990670694787?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/1038109990670694787?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/5lnjpHZE7IQ/quick-backup-script.html" title="Quick Backup Script" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>1</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2009/09/quick-backup-script.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUAFR304eCp7ImA9WxNTGE0.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-2829275012695584460</id><published>2009-08-20T17:11:00.003-04:00</published><updated>2009-08-20T17:28:36.330-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-20T17:28:36.330-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="conference" /><category scheme="http://www.blogger.com/atom/ns#" term="class" /><category scheme="http://www.blogger.com/atom/ns#" term="malware analysis" /><title>Introduction to Malware Dissection</title><content type="html">This October 29-30th the annual &lt;a href="http://www.informationsecuritysummit.org/"&gt;Ohio Information Security Summit&lt;/a&gt; will be held.  I highly recommend attending it if you can.  The conference features two days of great talks, keynotes, labs and networking.  It has been going on for a few years now and never fails to disappoint anyone who attends, especially for the price ($275 until Oct 1, $350 after).  In addition to the normal talks, the summit is offering a number of &lt;a href="http://www.informationsecuritysummit.org/training.php"&gt;pre-conference training courses&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;I will be teaching a 2 day introduction to malware analysis class as one of the pre-conference training courses.  The course is geared to those who want to learn malware analysis or are just starting out.  We'll cover all of the basics for malware analysis including setting up your analysis lab, static analysis and dynamic analysis.  In the end, you'll walk out of the class with the knowledge of how to take a malware sample and determine what it does, who it contacts and what risk it poses.&lt;br /&gt;&lt;br /&gt;In the courses I have taken, I've found that I learn alot more by actually doing things rather than watching a powerpoint presentation for 8 hours. Because of this, the class will be structured around a number of labs which have you do the analysis using various tools on actual malware.  I've collected a number of cool malware samples which will be analyzed in the course in various ways and I'm really excited about it.  At the end of the class they'll also be an analysis contest where prizes will be given out.&lt;br /&gt;&lt;br /&gt;Since we will be handling live malware there are some &lt;a href="http://www.informationsecuritysummit.org/training.php"&gt;laptop requirements listed in the course description.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;If anyone has any questions on the course or the laptop requirements, please contact me.  I look forward to seeing you there!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-2829275012695584460?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/2829275012695584460/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=2829275012695584460" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/2829275012695584460?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/2829275012695584460?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/rygmwOG-fEU/introduction-to-malware-dissection.html" title="Introduction to Malware Dissection" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>0</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2009/08/introduction-to-malware-dissection.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk8EQnc5cSp7ImA9WxNTFEg.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-623131935543588669</id><published>2009-08-16T16:15:00.005-04:00</published><updated>2009-08-16T16:33:23.929-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-16T16:33:23.929-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="musing" /><title>Its Not Always A Security Issue</title><content type="html">I've been spending this weekend fixing my in-laws computer.  Like most of you, I'm the family "tech support" for anything that goes wrong with a computer.  This past week I received a call from my mother-in-law that she was getting pop ups on her computer stating that it was infected and that the program would remove it if they paid for the full version.  Classic sign of fake anti-virus.&lt;br /&gt;&lt;br /&gt;After some quick research, we were able to determine that it was &lt;a href="http://www.bleepingcomputer.com/virus-removal/remove-advanced-virus-remover"&gt;Advanced Virus Remover&lt;/a&gt;.  It appeared to be pretty simple to get off (delete some files, clear out some of the registry, etc) but since I was not there I decided the best way was to have her reboot into safe mode and perform a system restore.  (Unlike some of my relatives, my m-i-l can actually do things like that without me hand-holding.)  Of course, when she tried to go into safe mode, it blue screened.&lt;br /&gt;&lt;br /&gt;The next day I went over to see if I could figure out what was going on.  I was able to remove the malware (and two others) fairly quickly, but we were still getting errors.  In short time I realized that part of the hard drive had gotten corrupted and was causing the BSODs - not the original malware.&lt;br /&gt;&lt;br /&gt;This made me remember another story from a job in a previous life.  I had been called down to another department by a friend.  The entire department were having some odd problems.  Whenever they tried to print their machines would BSOD.  Since I was the resident "malware guy", they decided to call me in to see if I could find anything.  When I got there, some Windows admins were also there looking at some of the systems.  My friend took me to the system with the original problem and I started to examine it.&lt;br /&gt;&lt;br /&gt;After a few minutes I couldn't find anything indicative of malware on the sytem.  I even booted with a Helix CD just in case there was a rootkit on the system.  Nothing.  After a few minutes the Windows admins came over and asked me what I thought.  I replied I didn't see anything but there were reports of a 0-day attack against the Windows printer system that day which were indicative of what we were seeing.  However, I stressed, I didn't know and didn't think this was related.&lt;br /&gt;&lt;br /&gt;Of course, within minutes the Windows admins had me on a call where they were explaining how I thought we had been hacked using a Windows 0-day attack against the printers.  It took at least 45 minutes for me to sort through everything that was being said and to finally point out that I had not found any proof of any attack and that I didn't think this was the problem.  When the Windows admins finally went back to troubleshooting the problem, they found that a corrupt Windows printer driver had gotten pushed to these systems and thats what was causing the issue.&lt;br /&gt;&lt;br /&gt;I learned two things that day:&lt;br /&gt;&lt;br /&gt;1. Never say that you think something has been compromised (or even could be compromised) until you have some type of proof.  People love to over-react in a situation like that and that just provides fuel for the fire.&lt;br /&gt;&lt;br /&gt;2. Not everything is a security incident.  Just like my in-laws computer, the presence of malware may not be the reason for the overall problem.  A corrupt hard drive could just be a corrupt hard drive.  If you start reading compromises into everything you see, you may miss what is actually there.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-623131935543588669?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/623131935543588669/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=623131935543588669" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/623131935543588669?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/623131935543588669?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/080P7JnHf9s/ive-been-spending-this-weekend-fixing.html" title="Its Not Always A Security Issue" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>1</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2009/08/ive-been-spending-this-weekend-fixing.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkANQXk8eSp7ImA9WxJaFkg.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-8599036154269531365</id><published>2009-08-07T09:47:00.003-04:00</published><updated>2009-08-07T10:19:50.771-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-07T10:19:50.771-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="virus" /><category scheme="http://www.blogger.com/atom/ns#" term="malware" /><category scheme="http://www.blogger.com/atom/ns#" term="malware analysis" /><title>Automating Malware Analysis Part 2</title><content type="html">I've heard rumors that the &lt;a href="http://www.hakin9.org/prt/view/about-the-mag/issue/1052.html"&gt;latest issue of Hakin9&lt;/a&gt; is on stands now.  This issue contains the second part of my article on automating malware analysis and adds memory analysis and sandnet capabilities to the analysis script.&lt;br /&gt;&lt;br /&gt;In the script, memory analysis is performed by suspending the virtual machine (as opposed to shutting it down as the first script did).  When a VMWare VM is suspended, the memory for the machine is dumped into a file which can then be analyzed.  This file is analyzed using &lt;a href="https://www.volatilesystems.com/default/volatility/"&gt;the Volatility Framework&lt;/a&gt;.  &lt;br /&gt;&lt;br /&gt;Volatility is an amazing tool which can extract information from Windows XP SP2 &amp; SP3 memory images.  The analysis script in the article uses Volatility to extract the process list, network connections, list of loaded DLLs and list of loaded modules of the VM memory.  However, Volatility can do so much more that I highly recommend extended what is in the article.&lt;br /&gt;&lt;br /&gt;In addition to memory analysis, the article adds sandnet capabilities to the script.  In the original script, the VM was set up in host-only networking mode which prevented the malware from communicating to anything over the network.  This really limited the analyst in what they could see.  For example, if the malware wanted to download additional files from a web server, the analyst would never see it.&lt;br /&gt;&lt;br /&gt;To allow network connectivity, and still keep the network the analyst was on safe from infection, the script uses a tool set called &lt;a href="http://www.inetsim.org/"&gt;InetSim&lt;/a&gt; to create a fake Internet for the malware to interact with.  InetSim loads a number of localized servers (DNS, HTTP, etc) and logs any data sent to it.  Now, when malware attempts to connect to a web server it will be able to and the analyst will see what it is attempted to download.  &lt;a href="http://secshoggoth.blogspot.com/2009/02/inetsim-installation.html"&gt;I blogged about InetSim and how to install InetSim back in February.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I hope everyone enjoys the article.  Please send me any feedback on the article or enhancements to the script.  It does not appear that Hakin9 has posted the code listing for it yet, but as soon as they do I'll link to it from here.  Of course, feel free to contact me to get the code if you want.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-8599036154269531365?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/8599036154269531365/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=8599036154269531365" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/8599036154269531365?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/8599036154269531365?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/4iqMRo11NEQ/automating-malware-analysis-part-2.html" title="Automating Malware Analysis Part 2" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>2</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2009/08/automating-malware-analysis-part-2.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkQFRng5fyp7ImA9WxJaFE0.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-6575577942531831534</id><published>2009-08-04T12:02:00.005-04:00</published><updated>2009-08-04T13:51:57.627-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-04T13:51:57.627-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="conference" /><title>Black Hat Recap</title><content type="html">Wow...its been a few months since I've last posted.  Sorry about that!  Things have been nuts IRL which has kept me away from posting, but if you actually read my blog you'll be happy to know I have some things lined up.&lt;br /&gt;&lt;br /&gt;Last week I had the opportunity to attend Black Hat USA in Las Vegas.  While I won't go over every single talk I attended, the highlights are below.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Advanced Malware Deobfuscation&lt;/span&gt; - This was actually a training course written by Scott Lambert and Jason Geffner.  The course is essentially about the different techniques used to unpack malware, an area I needed some training on.  If you know how to RE and are comfortable in a debugger, I highly recommend this course.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Win at Reversing&lt;/span&gt; - This talk was given by Nick Harbour from Mandiant on a new tool called API Thief. When performing behavioral analysis of a malware sample, the analyst typically wants to see what calls the malware is making and uses a program like Process Monitor to do so. The problem with this only system calls are grabbed and misses some potentially important API calls. Nick's tool uses inline hooking to record API calls instead of system calls. This allows the analyst to get more information and potentially do some tricks to unpack the software. I'm going to be checking out the tool more to see how I can utilize it. Currently it can be downloaded at &lt;a href="http://rnicrosoft.net"&gt;http://rnicrosoft.net&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Reverse Engineering by Crayon&lt;/span&gt; - The next talk was on performing hypervisor based malware analysis and visualization. Essentially, the presenters used a software called Ether which integrates with a Xen VM in order to perform malware analysis. To be honest, I had not looked into using Xen for sandnets, but after this presentation I think it has alot of promise and will be doing some more research into it. All of the slides and notes are posted on &lt;a href="http://offensivecomputing.net"&gt;http://offensivecomputing.net&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;Fast &amp; Furious Reverse Engineering with TitanEngine&lt;/span&gt; - This was the last talk of the con I attended and it really didn't get the attention it deserved. TitanEngine is an open-source SDK and framework the authors are releasing which is used to perform and automate a large number of tasks needed when unpacking malware. The framework is very impressive in what it can do and how mature it is for something that is just being released. The presenters gave a number of live demos of programs written with the framework being used to unpack programs. The last demo they gave was done using TheMida, a packer which is notoriously difficult to unpack. They packed a sample program during the presentation turning on all capabilities of the packer and then unpacked it in a few seconds with a program they made with TitanEngine. This is definitely a program I will be looking into. &lt;a href="http://titan.reversinglabs.com"&gt;http://titan.reversinglabs.com&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I had a great time at Black Hat and met alot of people.  Unfortunately, I wasn't able to stay for Defcon but maybe another year.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-6575577942531831534?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/6575577942531831534/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=6575577942531831534" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/6575577942531831534?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/6575577942531831534?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/Jgsr_DYjrG8/black-hat-recap.html" title="Black Hat Recap" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>0</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2009/08/black-hat-recap.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUUBSH88eip7ImA9WxJRGUw.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-6594185715836831600</id><published>2009-05-21T10:36:00.003-04:00</published><updated>2009-05-21T10:47:39.172-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-05-21T10:47:39.172-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="PDF" /><category scheme="http://www.blogger.com/atom/ns#" term="snort" /><category scheme="http://www.blogger.com/atom/ns#" term="presentation" /><title>Detecting Malicious PDFs</title><content type="html">Last night at the NE Ohio Information Security Forum I gave a presentation on Detecting Malicious PDFs.  I'm still not sure if I'm going to release the presentation, but I am going to release a Snort signature that I've found useful for detecting evil PDFs.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-family:Arial;font-size:85%;"&gt;&lt;/span&gt;&lt;blockquote&gt;&lt;span style="font-family:Arial;font-size:85%;"&gt;alert tcp $EXTERNAL_NET $HTTP_PORTS -&gt; $HOME_NET any (msg:"Potential Malicious PDF (OpenAction JavaScript)"; flow:from_server,established; content:"%PDF-"; content:"&amp;lt;&amp;lt;/OpenAction &amp;lt;&amp;lt;/JS"; within:128; nocase; classtype:trojan-activity;)&lt;/span&gt;&lt;/blockquote&gt;&lt;br /&gt;This signature looks for the PDF header (indicating we're dealing with a PDF) then an &lt;span style="font-style: italic;"&gt;/OpenAction&lt;/span&gt; followed by /JS.  This indicates that JavaScript will be executed as soon as the document is open.&lt;br /&gt;&lt;br /&gt;Yes, I realize this signature can be easily bypassed with &lt;a href="http://blog.didierstevens.com/2008/04/29/pdf-let-me-count-the-ways/"&gt;PDF obfuscation&lt;/a&gt;.  However, I've found that attackers are not yet using this very much.  Let me know if this is useful to you.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-6594185715836831600?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/6594185715836831600/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=6594185715836831600" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/6594185715836831600?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/6594185715836831600?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/fJM_MrU03x8/detecting-malicious-pdfs.html" title="Detecting Malicious PDFs" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>1</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2009/05/detecting-malicious-pdfs.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkUEQHo7fyp7ImA9WxJSF00.&quot;"><id>tag:blogger.com,1999:blog-2672754150485551359.post-8165005265940871140</id><published>2009-05-07T09:13:00.004-04:00</published><updated>2009-05-07T09:50:01.407-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2009-05-07T09:50:01.407-04:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="virus" /><category scheme="http://www.blogger.com/atom/ns#" term="malware" /><category scheme="http://www.blogger.com/atom/ns#" term="malware analysis" /><title>Automating Malware Analysis article</title><content type="html">In the latest &lt;a href="http://hakin9.org/prt/view/about-the-mag/issue/1023.html"&gt;Hakin9 issue (3/2009)&lt;/a&gt;, I have an article on automating malware analysis.  The article discusses how one can set up their own malware analysis automation system using VMWare, some analysis tools and two scripts.  The article uses a Linux system as the base system and a Windows XP Pro as the guest/analysis OS, but I don't see why one couldn't use Cygwin on Windows for a base system with a few tweaks.&lt;br /&gt;&lt;br /&gt;The scripts I created for the article are meant to be used as a base for your own automated analysis system - they are meant to be expanded upon.  I encourage others to add other tools and capabilities to the scripts and share them here on the blog. The scripts used are &lt;a href="http://media.software.com.pl/hakin9/en/Listingi/03_2009/Automating_Malware_Analysis.rtf"&gt;available on Hakin9's site&lt;/a&gt;.  However, if anyone wants the actual files let me know and I'll send them out.&lt;br /&gt;&lt;br /&gt;I should point out that the system and scripts in this article assume you are in VMWare's host-only network mode.  This is to prevent malware from accidentally infecting other systems on your network, the Internet, etc.  However, since the system is set up host-only mode your malware will not be able to communicate with any hosts.  The only network traffic you will see are DNS requests and probes to systems that go unanswered.&lt;br /&gt;&lt;br /&gt;I encourage others to implement this into their automation system using software such as Truman, fakedns, or &lt;a href="http://secshoggoth.blogspot.com/2009/02/inetsim-installation.html"&gt;InetSim&lt;/a&gt; to create a virtual network.  Don't want to take the time?  Then you'll have to wait for the next issue of Hakin9 where I have part 2 to this article and show how to set this up (along with some other cool things).&lt;br /&gt;&lt;br /&gt;I'd love to hear any feedback on the scripts, tools, or the article...including anything you use to expand upon it.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2672754150485551359-8165005265940871140?l=secshoggoth.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel="replies" type="application/atom+xml" href="http://secshoggoth.blogspot.com/feeds/8165005265940871140/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=2672754150485551359&amp;postID=8165005265940871140" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/8165005265940871140?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/2672754150485551359/posts/default/8165005265940871140?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/TheSecurityShoggoth/~3/MsZFFwbRa-A/automating-malware-analysis-article.html" title="Automating Malware Analysis article" /><author><name>Tyler</name><uri>http://www.blogger.com/profile/15411793726236555303</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="27" src="http://3.bp.blogspot.com/_4x76DeWu9xs/SYw_4FLklTI/AAAAAAAAADw/k0wYVgrHSzc/S220/muckmonster-small-blog.png" /></author><thr:total>4</thr:total><feedburner:origLink>http://secshoggoth.blogspot.com/2009/05/automating-malware-analysis-article.html</feedburner:origLink></entry></feed>

