A few Ghidra tips for IDA users, part 1 – the decompiler/unreachable code, (Mon, Apr 8th)

As I continue to explore NSA&#;x26;#;39;s new reversing tool, Ghidra, one of the features that I heard about and was excited to see in action was the decompiler. So, in this entry in the series, I&#;x26;#;39;ll start to delve into that some. In particular, I&#;x26;#;39;ll look at one particular option that turned out to be more useful than I originally thought, though I&#;x26;#;39;m still not entirely certain how I&#;x26;#;39;ll use it going forward. I&#;x26;#;39;ve long been a user of the Hex-Rays decompiler at $dayjob and I really like it, but I can&#;x26;#;39;t afford it for use in my personal/Storm Center research and we don&#;x26;#;39;t use it in FOR610, so I was really looking forward to giving the Ghidra one a try. I have to say, so far, I&#;x26;#;39;m pretty impressed. As I explain to my FOR610 students, decompiling is a hard problem. A lot of context is lost during optimization, so except for very simple programs you shouldn&#;x26;#;39;t expect the decompiler to give you C code that looks like the original source. Having said that, for someone like me who has been programming on-and-off for a very long time, I can usually grasp the purpose of a function much more quickly in a (pseudo-)high level language than I can in assembler. One place decompiling is extremely useful for, is showing the parameters to function calls (especially Windows API calls) in a way that isn&#;x26;#;39;t as tedious (and potentially error prone) as scrolling up and counting the PUSH instructions (cdecl or stdcall) or trying to trace the contents of certain registers (fastcall). More on that in my next installment.

Continue reading A few Ghidra tips for IDA users, part 1 – the decompiler/unreachable code, (Mon, Apr 8th)→

Posted in Uncategorized

Fake Office 365 Payment Information Update, (Sun, Apr 7th)

If you currently have Office 365, watch out for fake request with a Subject of “Action required: Update your payment information now” and with sender: “Microsoft Online Services Team no-replay@support.onmicrosoft.com”. Over the past few weeks I have received several of these emails which looks quite legitimate. Here is an example:

Continue reading Fake Office 365 Payment Information Update, (Sun, Apr 7th)→

Posted in Uncategorized

Beagle: Graph transforms for DFIR data & logs, (Fri, Apr 5th)

From About Beagle:
“Beagle is an incident response and digital forensics tool which transforms data sources and logs into graphs. Supported data sources include FireEye HX Triages, Windows EVTX files, SysMon logs and Raw Windows memory images. The resulting Graphs can be sent to graph databases such as Neo4J or DGraph, or they can be kept locally as Python NetworkX objects.
Beagle can be used directly as a Python library, or through a provided Web interface.â€
Our use here will be through the Web interface running from Docker.

Continue reading Beagle: Graph transforms for DFIR data & logs, (Fri, Apr 5th)→

Posted in Uncategorized

New Waves of Scans Detected by an Old Rule, (Thu, Apr 4th)

Who remembers the famous ShellShock (&#;x26;#;x25;&#;x26;#;x25;cve:2014-6271&#;x26;#;x25;&#;x26;#;x25;)&#;x26;#;x3f; This bug affected the bash shell in 2014 and was critical due to the facts that it was easy to exploit and that bash is a widespread shell used in many tools/applications. So, at this time, I created an OSSEC alerts to report ShellShock exploitation&#;x26;#;xc2;&#;x26;#;xa0;attempts against my servers. Still today,&#;x26;#;xc2;&#;x26;#;xa0;I&#;x26;#;39;m getting a hit on this rule from time to time.

Continue reading New Waves of Scans Detected by an Old Rule, (Thu, Apr 4th)→

Posted in Uncategorized