072. Here's How Adversaries Abuse PowerShell to Steal Authentication Material

Hello everyone! Let's keep looking at PowerShell abuse examples observed in-the-wild. I hope you have ScriptBlock events (Event ID 4104) from Powershell-Operational Event Logs, as we're going to look inside malicious scripts this time.

Recently Outpost24 blogged about EncryptHub, and I spotted a very interesting PowerShell script responsible for stealing sensitive data. Let's look at the script from detection perspective.

For example, the adversary attempts to collect Telegram data:

$processname = "telegram"

$pathtele = "$env:userprofile\AppData\Roaming\Telegram Desktop\tdata"

It means we can hunt for Telegram data paths in the ScriptBlock:

event_type: "ScriptExecutionWin"

AND

script_text: "Telegram Desktop" AND "tdata"

Another example is collecting crypto wallets data:

"Armory" = Join-Path $env:appdata "\Armory\*.wallet"

"Atomic" = Join-Path $env:appdata "\Atomic\Local Storage\leveldb"

"Bitcoin" = Join-Path $env:appdata "\Bitcoin\wallets"

"Binance" = Join-Path $env:appdata "\Binance\Wallet\*.*"

"Bytecoin" = Join-Path $env:appdata "\bytecoin\*.wallet"

"Coinomi" = Join-Path $env:localappdata "\Coinomi\Coinomi\wallets"

"Dash" = Join-Path $env:appdata "\DashCore\wallets"

"Electrum" = Join-Path $env:appdata "\Electrum\wallets"

"Ethereum" = Join-Path $env:appdata "\Ethereum\keystore"

"Exodus" = Join-Path $env:appdata "\Exodus\exodus.wallet"

"Guarda" = Join-Path $env:appdata "\Guarda\Local Storage\leveldb"

Here we can use various wallet names to build our detection, for example:

event_type: "ScriptExecutionWin"

AND

script_text: "Armory" OR "Atomic" OR "Bitcoin" OR "Binance" OR "bytecoin" OR "Coinomy" OR "DashCore" OR "Electrum" OR "Ethereum" OR "Exodus" OR "Guarda"

The script contains lots of interesting data, so you can check it and think about other detection opportunities.

See you tomorrow!

Comments

Post a Comment

Popular posts from this blog

033. Free Google Threat Intelligence Course

Image
Hello everyone! Everybody loves free courses, right? Have you missed a free course on Google Threat Intelligence ? If the answer is "Yes", it's your chance to check it!  I like this course as it not only overviews the capabilities of Google Threat Intelligence as a product, but also covers various threat intelligence use cases, for example, how to empower incident response and forensic investigations or how to use it for adversary hunting and tracking. I've already got my completion badge: What about you? See you tomorrow!
Read more

001. The Zeltser Challenge

Image
Hello everyone! Happy New Year! New year - new challenges! So, a few weeks ago David Cowen reminded me about the Zeltser challenge. What's the point? You must blog every day for a year to push yourself to research and write. Sound cool, right? Dave suggested to start the challenge with him on 1/1/25, and that's why you are reading this post! So, what am I going to share here? I'm a big fan of intelligence-led approach to cyber defense, so every day we'll look at this or that technique (or sub-technique) leveraged by real adversaries, so we can learn more about our enemies.  We'll look both at public reporting and private findings by BI.ZONE Threat Intelligence team. Stay tuned, and see you tomorrow!
Read more

012. They Want to Know Everything About Your System!

Image
Hello everyone! Today we'll look at reconnaissance techniques leveraged by Secret Blizzard (also known as Turla) as seen in the report by Microsoft Threat Intelligence.  In this campaign Secret Blizzard used the Amadey bot to download its own backdoors to specifically selected target devices associated with the Ukrainian military. So, one of the batch scripts leveraged by adversary invoked lots of reconnaissance commands. Let's look at each of them: ver - to collect information about OS version; systeminfo - to collect compromised system information; ipconfig /all - to collect the full TCP/IP configuration for all adapters; ipconfig /displaydns - to collect the contents of the DNS client resolver cache; route print - to collect the entries in the local IP routing table; arp -a - to collect information on current arp cache tables for all interfaces; netstat -a -n - to collect information on active network connections; net share - to collect information on ...
Read more