<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-7943717113868662108</atom:id><lastBuildDate>Mon, 16 Sep 2024 16:56:10 +0000</lastBuildDate><title>The Forensic Threat Hunter</title><description></description><link>https://forensicthreathunter.blogspot.com/</link><managingEditor>noreply@blogger.com (Dr. S)</managingEditor><generator>Blogger</generator><openSearch:totalResults>4</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7943717113868662108.post-8694701286326652307</guid><pubDate>Thu, 22 Feb 2018 14:53:00 +0000</pubDate><atom:updated>2018-02-22T06:53:50.520-08:00</atom:updated><title>New RaaS - 2, In Fact</title><description>There are two new ransomwares hitting the streets and both are RaaS - Ransomware as a Service. Because these are important I am interrupting my series on threat hunting to find if there actually was an event.
Additionally, you will note that I have been using the blog for announcements and pointers to some of the other pages on my site.  Now that I have fixed the site to do its own announcements I will no longer need to do that.  I will delete the distracting messages and in the future stick to blog topics typical of the research we do here at the Cyber Crime Research Lab.
The two ransomwares are Saturn and ShurL0ckr. While they are not the same malware, they do share some characteristics.&lt;br /&gt;
&lt;br /&gt;
&lt;span style=&quot;color: #ea9999; font-size: x-small;&quot;&gt;THE HASH OF SHURL0CKR AS DOWNLOADED FROM THE RAAS ONION SITE IS 21E6512E1C4F9F7B5AFCD190768A9D5EAA9B9E9253B0E74FD7C6273C51DEF6E3 (HTTPS://WWW.VIRUSTOTAL.COM/EN/FILE/6973804399183FB7AC15DAB61D4C331C9AA7072F033BD62892CCA9925253E52E/ANALYSIS/).  A SECOND FILE CREATED ON THE RAAS SITE HAD A HASH OF 72E3E6295C02A4610E710138340095B61E4E365E37291B810BCE970B435897EA&amp;nbsp;&lt;/span&gt;&lt;br /&gt;
&lt;span style=&quot;color: #ea9999; font-size: x-small;&quot;&gt;&lt;br /&gt;&lt;/span&gt;
&lt;span style=&quot;color: #ea9999; font-size: x-small;&quot;&gt;THE HASH OF SATURN, AS REPORTED IN &lt;a href=&quot;https://www.virustotal.com/&quot;&gt;VIRUSTOTAL&lt;/a&gt; BY MALWRHUNTER IS 6973804399183FB7AC15DAB61D4C331C9AA7072F033BD62892CCA9925253E52E (HTTPS://WWW.VIRUSTOTAL.COM/#/FILE/21E6512E1C4F9F7B5AFCD190768A9D5EAA9B9E9253B0E74FD7C6273C51DEF6E3/DETECTION).&lt;/span&gt;&lt;span style=&quot;color: #990000;&quot;&gt;&amp;nbsp;&lt;/span&gt;&lt;br /&gt;
&lt;br /&gt;
&amp;nbsp;Both ransomwares address the Link-local Multicast Name Resolution (LLMNR) address, 224.0.0.252. This multicast IP allows hosts on the same network segment to perform name resolution. I have samples of the ShurL0ckr ransomware so we&#39;ll focus on that for this posting.&lt;br /&gt;
&lt;br /&gt;
ShurL0ckr is a variant of the Gojdu malware. Gojdu is a ransomware-like Trojan whose main forte is as a stealer. Without getting into the internals of the two it appears that Gojdu has been repurposed as do-it-yourself ransomware. These are not the first RaaS malwares. I wrote about Satan RaaS in a blog when I was at SC Magazine. As of the end of 2017, Sophos reported five such kits: Philadelphia, Stampado, Frozr Locker, Satan and RaaSBerry. Now, we can add Saturn and ShurL0ckr.&lt;br /&gt;
&lt;br /&gt;
We tested ShurL0ckr on our&lt;a href=&quot;https://attivonetworks.com/attivo-botsink/&quot;&gt; Attivo BOTSink &lt;/a&gt;deception network on one of our decoy Windows 7, 64-bit VMs.&lt;br /&gt;
&lt;br /&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;
&lt;a href=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjkBLL-eUEV8vaGFF6UT7Vd9nuZHJToHVMip1btMKcpRNL-amRrQRLhlb9zSKpnuJp3RT9U-lteeST8l1FN3MwK8rgWD6YsKt78wNQIjASS62TQMgt7CF0W31NqtvvPXR0qw0eYOzDGIatX/s1600/Blog+%25232+Fig+1+-++-+BOTSink+Detection+of+ShurL0ckr+.PNG&quot; imageanchor=&quot;1&quot; style=&quot;margin-left: 1em; margin-right: 1em;&quot;&gt;&lt;img border=&quot;0&quot; data-original-height=&quot;588&quot; data-original-width=&quot;1600&quot; height=&quot;234&quot; src=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjkBLL-eUEV8vaGFF6UT7Vd9nuZHJToHVMip1btMKcpRNL-amRrQRLhlb9zSKpnuJp3RT9U-lteeST8l1FN3MwK8rgWD6YsKt78wNQIjASS62TQMgt7CF0W31NqtvvPXR0qw0eYOzDGIatX/s640/Blog+%25232+Fig+1+-++-+BOTSink+Detection+of+ShurL0ckr+.PNG&quot; width=&quot;640&quot; /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Figure 1 - BOTSink Detection of ShurL0ckr&amp;nbsp;&lt;/div&gt;
&lt;br /&gt;
&lt;br /&gt;
Notice in Figure 2 that the malware is attempting to communicate with its C&amp;amp;C, 128.136.25.210 on port 443.&lt;br /&gt;
&lt;br /&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;
&lt;a href=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiZAxaQ1Ks7RJnsjc0tPVkjlbCjo1JyJH64p-l5fVSGcvV_gUgv-oddxYih1kNGhD4vAGGO6AgqU-sOegjrxWA8CvSo00YvQjWO8xIxAmxoD9mYsLlhHkEqVyaorFiqw62t40VnfNy63_xH/s1600/Blog+%25232+Fig+2+-+-++-+Attempts+to+communicate+with+C2+.PNG&quot; imageanchor=&quot;1&quot; style=&quot;margin-left: 1em; margin-right: 1em;&quot;&gt;&lt;img border=&quot;0&quot; data-original-height=&quot;307&quot; data-original-width=&quot;1535&quot; height=&quot;128&quot; src=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiZAxaQ1Ks7RJnsjc0tPVkjlbCjo1JyJH64p-l5fVSGcvV_gUgv-oddxYih1kNGhD4vAGGO6AgqU-sOegjrxWA8CvSo00YvQjWO8xIxAmxoD9mYsLlhHkEqVyaorFiqw62t40VnfNy63_xH/s640/Blog+%25232+Fig+2+-+-++-+Attempts+to+communicate+with+C2+.PNG&quot; width=&quot;640&quot; /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
&amp;nbsp;Figure 2 - Attempts to communicate with C2&amp;nbsp;&lt;/div&gt;
&lt;br /&gt;
&lt;br /&gt;
I put this IP into Cisco Investigator and got nothing back. This IP clearly is not in the clearnet DNS.  However, there are other ways to beat the system and they require that we use link analysis. So I went to my favorite Internet Link Analyzer - &lt;a href=&quot;https://www.paterva.com/web7/buy/maltego-clients/maltego.php&quot;&gt;Maltego&lt;/a&gt; - and found a related domain: 3a9bf2dfc88186b28443c1d229f1e605eb54c23c2bb14994dfb20394.6.vfrtg.com. See Figure 3.&lt;br /&gt;
&lt;br /&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;
&lt;a href=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiQVr2vlJY07SuNUe1ziDiMZQHZK6FWQDqxgzs3MdExZBhvRgHjKwQuGZ8zLblHyyv5Pk2ega9wjeSaZ9yxz9A8BUWgYfgecObWt7C3hyWRD-yEDJTThyQ5rv1UObFCLBZSZY0YUrwOTsa8/s1600/Blog+%25232+Fig+3+-++-+Maltego+Domain+Resolution+.PNG&quot; imageanchor=&quot;1&quot; style=&quot;margin-left: 1em; margin-right: 1em;&quot;&gt;&lt;img border=&quot;0&quot; data-original-height=&quot;306&quot; data-original-width=&quot;327&quot; height=&quot;596&quot; src=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiQVr2vlJY07SuNUe1ziDiMZQHZK6FWQDqxgzs3MdExZBhvRgHjKwQuGZ8zLblHyyv5Pk2ega9wjeSaZ9yxz9A8BUWgYfgecObWt7C3hyWRD-yEDJTThyQ5rv1UObFCLBZSZY0YUrwOTsa8/s640/Blog+%25232+Fig+3+-++-+Maltego+Domain+Resolution+.PNG&quot; width=&quot;640&quot; /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Figure 3 - Maltego Domain Resolution&amp;nbsp;&lt;/div&gt;
&lt;br /&gt;
&lt;br /&gt;
This resolves to a domain owned by a registrant hidden by DomainsByProxy and is a possible fast flux. This would explain why it does not appear in the DNS. Further Maltego analysis shows several subdomains so the fast flux theory holds water. Investigate resolves the domain to 102.180.107.49, 130.159.43.175, 163.102.237.212, 199.203.40.178, 107.138.22.245, and 5.188.137.23. A quick scan of the domain yields these additional IPs: 21.129.200.177 50.168.26.33 81.83.196.202 86.117.246.217 117.59.243.39. This is further evidence suggesting a fast flux network. The front-end of the onion site where the builder resides is https://kdv&lt;span style=&quot;background-color: black;&quot;&gt;……&lt;/span&gt;bwh.onion.to.&lt;br /&gt;
&lt;br /&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;
&lt;a href=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj8plCpkvxmGAVg-oZkj0FsHEq9qFMV5QR_RL50UlIKFt5zZY9sgW6g1AXGO7QffzsvZftOo_v9tNjm153b3FImKYIZQkxzifq7MJh-hjfE-XZWCFU1STtI0M41VM3-4RD16GiRTNUOXFTr/s1600/Blog+%25232+Fig+4++--++Ransomware+Builder+Site.PNG&quot; imageanchor=&quot;1&quot; style=&quot;margin-left: 1em; margin-right: 1em;&quot;&gt;&lt;img border=&quot;0&quot; data-original-height=&quot;707&quot; data-original-width=&quot;843&quot; height=&quot;536&quot; src=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj8plCpkvxmGAVg-oZkj0FsHEq9qFMV5QR_RL50UlIKFt5zZY9sgW6g1AXGO7QffzsvZftOo_v9tNjm153b3FImKYIZQkxzifq7MJh-hjfE-XZWCFU1STtI0M41VM3-4RD16GiRTNUOXFTr/s640/Blog+%25232+Fig+4++--++Ransomware+Builder+Site.PNG&quot; width=&quot;640&quot; /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div style=&quot;text-align: center;&quot;&gt;
Figure 4 - Ransomware Builder Site&amp;nbsp;&lt;/div&gt;
&lt;br /&gt;
This ransomware - like Satan RaaS - costs nothing but the actor gets a cut of the cyber criminal&#39;s take. The builder is nothing beyond the page in Figure 4.  Simply insert your bitcoin wallet address and the amount of the ransom (.01 - 1 BTC).&lt;br /&gt;
&lt;br /&gt;
The tools we used this time were&lt;a href=&quot;https://www.virustotal.com/#/home/upload&quot;&gt; VirusTotal,&lt;/a&gt; Attivo &lt;a href=&quot;https://attivonetworks.com/attivo-botsink/&quot;&gt;BOTSink&lt;/a&gt; and &lt;a href=&quot;https://www.paterva.com/web7/buy/maltego-clients/maltego.php&quot;&gt;Maltego&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
--Dr. S</description><link>https://forensicthreathunter.blogspot.com/2018/02/new-raas-2-in-fact.html</link><author>noreply@blogger.com (Dr. S)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjkBLL-eUEV8vaGFF6UT7Vd9nuZHJToHVMip1btMKcpRNL-amRrQRLhlb9zSKpnuJp3RT9U-lteeST8l1FN3MwK8rgWD6YsKt78wNQIjASS62TQMgt7CF0W31NqtvvPXR0qw0eYOzDGIatX/s72-c/Blog+%25232+Fig+1+-++-+BOTSink+Detection+of+ShurL0ckr+.PNG" height="72" width="72"/><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7943717113868662108.post-6359332540181649810</guid><pubDate>Thu, 11 Jan 2018 21:03:00 +0000</pubDate><atom:updated>2018-01-11T13:06:12.039-08:00</atom:updated><title>Now You See It, Now You Don&#39;t (or do you?) - A Threat Hunt Without an Obvious Threat - part 1</title><description>&lt;div class=&quot;MsoNormal&quot;&gt;
OK, folks… this launches the Forensic Threat Hunter Blog.
I&#39;ll begin with a short series on forensic threat hunting to get us
started.&amp;nbsp; As I progress I&#39;ll point out
the tools I am using with a link to the tool&#39;s site so you can have a look. I
am not going into detail about threat hunting - other bloggers and,
particularly, &lt;a href=&quot;https://sqrrl.com/&quot;&gt;Sqrrl&lt;/a&gt;, have done that.&amp;nbsp; We are going to focus on taking your threat
hunt to the next level of sophistication. What that means is extending a
traditional - can I really say that, given how young this technique is? -
threat hunt into the digital forensic analysis that we see with, for example,
computer forensic tools.&amp;nbsp; This certainly
will take us to the cloud and we have tools for that as well.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
Before we get going, I want to recommend a new eBook from
Sqrrl: &lt;a href=&quot;http://info.sqrrl.com/huntpedia&quot;&gt;Huntpedia: Your Threat Hunting
Knowledge Compendium&lt;/a&gt;.&amp;nbsp; This has a lot
of basic - and some not-so-basic - techniques for threat hunting.&amp;nbsp; While it is, sometimes, Sqrrl-centric, it is
a long way from being a sales pitch.&amp;nbsp; You
can do just about everything they talk about using discrete tools - and they
discuss that a bit - but it will take longer and be more tedious. I am going to
use an actual - but hybrid - example (although I need to change a lot of
addresses, domains and URLs to protect the victim(s)) because this is a case
where there were behavioral indications that something had happened but there
were no IoCs internal to the enterprise.&amp;nbsp;
So the question to be answered was &quot;What, if anything,
happened?&quot; &lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
While the core of this is an actual set of events, I have
seen this many times so - again, to protect the victim(s) - I am mixing in
several examples from other threat hunts in which I have participated. We&#39;ll
work our way through this over several blog postings. This posting is mostly
background and general procedure.&amp;nbsp; We
will work our way through the Diamond Model (more on this below) over the
course of the next few postings and, as we do so, getting more and more
detailed as we close in on our results.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
The &lt;u&gt;Huntpedia&lt;/u&gt; tells us that when we are looking
through large volumes of logs we want to answer three questions: What am I
looking for?, Why am I looking for it?, and How do I find it. All that is fine
if you have lots of logs.&amp;nbsp; What if you
don&#39;t? How do you fill in the gaps that the logs normally would fill? There are
lots of techniques and over the course of this series we will use many of them
but the problem here is finding a starting point. This is where a solid
knowledge of the involved operating system(s) is necessary.&amp;nbsp; You need to know how the device&#39;s logs are
created, where they reside and what they can tell you. If you are missing logs
you will need alternatives.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;b&gt;&lt;i&gt;Where to Start?&lt;/i&gt;&lt;/b&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
In our example, we had limited logs available.&amp;nbsp; But we did have some event logs on the
perimeter and that is where we started.&amp;nbsp;
We were tipped off initially by some anomalous behavior and that led us
to the firewall logs on the perimeter. Some of the devices involved were, of
course, Internet-facing so that is where we began.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
I have a very strong bias towards data collection: do it
early, often and as completely as you can.&amp;nbsp;
Of course we harvested what logs we could but there was more to see and
the logs weren&#39;t talking to us.&amp;nbsp; So we
took each of the servers on the perimeter - particularly those that showed
interactions that we couldn&#39;t explain externally to the enterprise - and we
took forensic images of each.&amp;nbsp; Here&#39;s a
hint: if you are in a VMWare virtual environment, just snapshot and take the
.vmdk file as you image. That is what we did.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
Next, there are some servers inside that we care a lot about
and you need to image those as well.&amp;nbsp;
Those include such things as domain controllers, sensitive databases,
any server that sets user privileges, such as web authentication servers,
Active Directory and so on. These baseline images should be duplicated and the
original first generation versions secured as evidence. NEVER work on
these.&amp;nbsp; Always use your copies. &lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
This first step is evidence preservation. If you really have
suffered a breach you don&#39;t know that your attacker has left the building. He
may still be lurking in your enterprise or he may have a back door through
which he can return at will.&amp;nbsp; One of the
biggest mistakes new threat hunters make is failing to preserve the crime
scene.&amp;nbsp; That critical first step will
help ensure that you have a clear picture - or as clear as practical under
whatever your circumstances are - of what the damage looks like even if you
have no idea yet as to how it occurred.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
Notice that we have not yet begun our hunt.&amp;nbsp; This is what military folks call
&quot;preparing the battlespace&quot;. Eventually, we will return to our images
- and probably later versions of them - and take a deeper forensic dive. In the
mean time, we have gotten our preliminary evidence and preserved it.&amp;nbsp; Note that we will take more images as our
investigation progresses and we find more involved computers.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
The &lt;u&gt;Huntpedia&lt;/u&gt; talks about the Diamond Model for
threat hunting. The Diamond Model starts with understanding the adversary, its
capabilities, what the adversary&#39;s infrastructure looked like (e.g., email,
compromised pivot computers, etc.) and what the victim looks like.&amp;nbsp; At this point we are looking at the victim
and we are beginning to see indications - if not actual IoCs yet - of what the
infrastructure that attacked us looks like.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
Infrastructure is our next step. For this we need some seeds
to begin our hunt.&amp;nbsp; In our data
collection step we saw some IPs, URLs and, perhaps, domains that seemed to be
out of place.&amp;nbsp; That caught our
attention.&amp;nbsp; So, to see just how
interesting these are we do some WHOIS to find out a little bit about them.
Here we use &lt;a href=&quot;https://learn-umbrella.cisco.com/datasheets/investigate-from-opendns&quot;&gt;Cisco
Umbrella Investigate&lt;/a&gt; to learn as much about the infrastructure as we can at
this point. This helps us understand who our possible attackers might be and,
perhaps as much about them as is available. We&#39;ll get into more detail in a
subsequent posting. &lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
For example, we are running a BOTSink deception network from
&lt;a href=&quot;https://attivonetworks.com/&quot;&gt;Attivo&lt;/a&gt; and we noticed a series of
failed SSH login attempts against our bait web server. See Figure 1 (you can click on the figures to expand them):&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div align=&quot;center&quot; class=&quot;MsoCaption&quot; style=&quot;text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;
&lt;a href=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhTfaXobwKc9rwJT7k8WD1x3erofwtghvk3sAm4ETdSSGU2pays9ycqtqfHEy1WMNeVnYEpYrrsYV6dJNyPcTzYVXGX6_fBDbUDS5YImVRPbsEpi-81Rm03WhAfMUFMPBLAmU3JRcmP_a3h/s1600/Blog+1+-+Fig+1.jpg&quot; imageanchor=&quot;1&quot; style=&quot;margin-left: 1em; margin-right: 1em;&quot;&gt;&lt;img border=&quot;0&quot; data-original-height=&quot;165&quot; data-original-width=&quot;906&quot; height=&quot;115&quot; src=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhTfaXobwKc9rwJT7k8WD1x3erofwtghvk3sAm4ETdSSGU2pays9ycqtqfHEy1WMNeVnYEpYrrsYV6dJNyPcTzYVXGX6_fBDbUDS5YImVRPbsEpi-81Rm03WhAfMUFMPBLAmU3JRcmP_a3h/s640/Blog+1+-+Fig+1.jpg&quot; width=&quot;640&quot; /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;div align=&quot;center&quot; class=&quot;MsoCaption&quot; style=&quot;text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div align=&quot;center&quot; class=&quot;MsoCaption&quot; style=&quot;text-align: center;&quot;&gt;
&lt;i&gt;Figure &lt;!--[if supportFields]&gt;&lt;span
style=&#39;mso-element:field-begin&#39;&gt;&lt;/span&gt;&lt;span
style=&#39;mso-spacerun:yes&#39;&gt; &lt;/span&gt;SEQ Figure \* ARABIC &lt;span style=&#39;mso-element:
field-separator&#39;&gt;&lt;/span&gt;&lt;![endif]--&gt;1&lt;!--[if supportFields]&gt;&lt;span
style=&#39;mso-no-proof:yes&#39;&gt;&lt;span style=&#39;mso-element:field-end&#39;&gt;&lt;/span&gt;&lt;/span&gt;&lt;![endif]--&gt;
- SSHD Authentication Attack - Failure&lt;/i&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div align=&quot;center&quot; class=&quot;MsoCaption&quot; style=&quot;text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
This is similar to seeing a suspicious event or IP in your
firewall log. We plug the IP into Investigate and we get Figure 2:&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;
&lt;a href=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj-qTB9eqMiBrgquhqBlLndJsN-HOq35KLq0u19cBTZO17cu-TEcjHYXe6p264-KT0OBsiZ67m2lRpoK5NlDXgHp4FESGoDCSpsydW5aoJCuw-EFefdKu476juSMjJLYI7CI1DWSARDxvIC/s1600/Blog+1+-+Fig+2.jpg&quot; imageanchor=&quot;1&quot; style=&quot;margin-left: 1em; margin-right: 1em;&quot;&gt;&lt;img border=&quot;0&quot; data-original-height=&quot;794&quot; data-original-width=&quot;1251&quot; height=&quot;406&quot; src=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj-qTB9eqMiBrgquhqBlLndJsN-HOq35KLq0u19cBTZO17cu-TEcjHYXe6p264-KT0OBsiZ67m2lRpoK5NlDXgHp4FESGoDCSpsydW5aoJCuw-EFefdKu476juSMjJLYI7CI1DWSARDxvIC/s640/Blog+1+-+Fig+2.jpg&quot; width=&quot;640&quot; /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div align=&quot;center&quot; class=&quot;MsoCaption&quot; style=&quot;text-align: center;&quot;&gt;
&lt;i&gt;Figure &lt;!--[if supportFields]&gt;&lt;span
style=&#39;mso-element:field-begin&#39;&gt;&lt;/span&gt;&lt;span
style=&#39;mso-spacerun:yes&#39;&gt; &lt;/span&gt;SEQ Figure \* ARABIC &lt;span style=&#39;mso-element:
field-separator&#39;&gt;&lt;/span&gt;&lt;![endif]--&gt;2&lt;!--[if supportFields]&gt;&lt;span
style=&#39;mso-no-proof:yes&#39;&gt;&lt;span style=&#39;mso-element:field-end&#39;&gt;&lt;/span&gt;&lt;/span&gt;&lt;![endif]--&gt;
- Investigate analysis of 88.99.38.183&lt;/i&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div align=&quot;center&quot; class=&quot;MsoCaption&quot; style=&quot;text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
We can see that the IP is hosted in Germany and it hosts
four different malwares.&amp;nbsp; There is more
but we&#39;ll save that for a later posting.&amp;nbsp;
&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
Now let&#39;s look at this IP&#39;s playmates.&amp;nbsp; For that we turn to &lt;a href=&quot;https://www.paterva.com/web7/buy/maltego-clients.php&quot;&gt;Maltego&lt;/a&gt;, a sort
of Internet link analyzer (we&#39;ll get deeper into that one later as well).&amp;nbsp; See Figure 3:&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;
&lt;a href=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEidlRtaJPQOmSlH-EhaA1YQUFWsI3jUQ7ofxHbtAZGMOUTNmlQNvC1pSjACyupcttmJqolSZn_5tDA_JcZ0n9hEaJ2rEFK7Csr3oLOysM1PS_gi9MlXMajME9-NEEQAmd_D_44w18IphevK/s1600/Blog+1+-+Fig+3.jpg&quot; imageanchor=&quot;1&quot; style=&quot;margin-left: 1em; margin-right: 1em;&quot;&gt;&lt;img border=&quot;0&quot; data-original-height=&quot;684&quot; data-original-width=&quot;787&quot; height=&quot;556&quot; src=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEidlRtaJPQOmSlH-EhaA1YQUFWsI3jUQ7ofxHbtAZGMOUTNmlQNvC1pSjACyupcttmJqolSZn_5tDA_JcZ0n9hEaJ2rEFK7Csr3oLOysM1PS_gi9MlXMajME9-NEEQAmd_D_44w18IphevK/s640/Blog+1+-+Fig+3.jpg&quot; width=&quot;640&quot; /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div align=&quot;center&quot; class=&quot;MsoCaption&quot; style=&quot;text-align: center;&quot;&gt;
&lt;i&gt;Figure &lt;!--[if supportFields]&gt;&lt;span
style=&#39;mso-element:field-begin&#39;&gt;&lt;/span&gt;&lt;span
style=&#39;mso-spacerun:yes&#39;&gt; &lt;/span&gt;SEQ Figure \* ARABIC &lt;span style=&#39;mso-element:
field-separator&#39;&gt;&lt;/span&gt;&lt;![endif]--&gt;3&lt;!--[if supportFields]&gt;&lt;span
style=&#39;mso-no-proof:yes&#39;&gt;&lt;span style=&#39;mso-element:field-end&#39;&gt;&lt;/span&gt;&lt;/span&gt;&lt;![endif]--&gt;
- Maltego Analysis of 88.99.38.183&lt;/i&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div align=&quot;center&quot; class=&quot;MsoCaption&quot; style=&quot;text-align: center;&quot;&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
So we are beginning to get a start on our threat hunt. Next
time we will dig deeper into what we can find and how we deal with the question
of what, if anything, happened.&amp;nbsp; All we
know so far is that there was a connection of some sort to the 88 IP and that
the IP appears malicious.&amp;nbsp; It attempted
to crack our SSH password.&amp;nbsp; What we don&#39;t
know at this point is whether this was a opportunistic attack or whether
someone inside our enterprise invited it. For that we will start by looking at
email to see if there was a phishing attack.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div class=&quot;MsoNormal&quot;&gt;
--Dr. S&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
</description><link>https://forensicthreathunter.blogspot.com/2018/01/now-you-see-it-now-you-dont-or-do-you.html</link><author>noreply@blogger.com (Dr. S)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhTfaXobwKc9rwJT7k8WD1x3erofwtghvk3sAm4ETdSSGU2pays9ycqtqfHEy1WMNeVnYEpYrrsYV6dJNyPcTzYVXGX6_fBDbUDS5YImVRPbsEpi-81Rm03WhAfMUFMPBLAmU3JRcmP_a3h/s72-c/Blog+1+-+Fig+1.jpg" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7943717113868662108.post-3777884009700110763</guid><pubDate>Tue, 02 Jan 2018 15:29:00 +0000</pubDate><atom:updated>2018-01-02T07:29:54.442-08:00</atom:updated><title>After Many Years with the Best InfoSec Publication in the World, We&#39;re Out on Our Own</title><description>I want to thank the folks at &lt;b&gt;&quot;SC Magazine&quot; &lt;/b&gt;for letting me point you to this site.&amp;nbsp; I cannot imagine a better publication to spend 25 years with and I have made a lot of friends there over those years.&lt;br /&gt;
&lt;br /&gt;
I have a lot of exciting things to share with you and, as you might expect, it takes awhile to put a technical blog together, but here are a few of the topics we&#39;ll address in the next couple of months:&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Forensic threat hunting with Sqrrl (that&#39;s our next blog posting)&lt;/li&gt;
&lt;li&gt;A forensic threat hunt in a real environment where all is not as it seems&lt;/li&gt;
&lt;li&gt;Evidence vs. opinion - it doesn&#39;t matter what we know - it&#39;s what we can prove&lt;/li&gt;
&lt;li&gt;Penetrating the underground and, coincidentally, a fast flux bullet-proof hosting network&lt;/li&gt;
&lt;li&gt;Tracking compromised payment cards through the underground dump shops&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
A lot of direct research goes into these blogs so when they publish you will be able to depend upon their accuracy.&amp;nbsp; We also will tell you what tools - commercial and open source/free - that we used in the research for the particular blog posting.&amp;nbsp; That will let you duplicate our efforts.&lt;br /&gt;
&lt;br /&gt;
So, I&#39;m looking forward to some exciting times.&amp;nbsp; Along with all of that here in the blog, don&#39;t forget to watch our underground news and IoCs tab as well as any new research papers I might publish (there is a new one up today).&lt;br /&gt;
&lt;br /&gt;
So, once again, welcome to the &lt;i&gt;&lt;b&gt;Forensic Threat Hunter&lt;/b&gt;&lt;/i&gt;! Fasten your seat belts... here we go!!!&lt;br /&gt;
&lt;br /&gt;
--Dr. S</description><link>https://forensicthreathunter.blogspot.com/2018/01/after-many-years-with-best-infosec.html</link><author>noreply@blogger.com (Dr. S)</author><thr:total>3</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-7943717113868662108.post-4464879804065169572</guid><pubDate>Fri, 03 Nov 2017 15:19:00 +0000</pubDate><atom:updated>2017-11-04T06:47:49.331-07:00</atom:updated><title>Welcome to the Forensic Threat Hunter Blog!</title><description>Welcome to the Forensic Threat Hunter. Forensic threat hunting is the next generation of cyber threat hunting.&amp;nbsp; Over the next few months I will be evolving this blog in much the same way as my Threat Hunter blog on SC Magazine so stay tuned.&lt;br /&gt;
&lt;br /&gt;
--Dr. S&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;</description><link>https://forensicthreathunter.blogspot.com/2017/11/welcome.html</link><author>noreply@blogger.com (Dr. S)</author><thr:total>0</thr:total></item></channel></rss>