TryHackMe - New Hire Old Artifacts

-

 



Investigation Breakdown & Step-by-Step Findings


Phase 1: Initial Execution & Password Dumper Identification


Objective: Identify the Web Browser Password Viewer executed on the system.


Splunk Query: index=* EventCode=1 "Password Viewer"


Findings:


Full Binary Path: C:\Users\FINANC~1\AppData\Local\Temp\11111.exe


Company Name: NirSoft (a well-known utility developer whose tools are frequently abused by threat actors).


Phase 2: Secondary Payload & Masquerading


Objective: Locate additional binaries executed from the same temporary directory and uncover their true identity.


Splunk Query: index=* EventCode=1 CurrentDirectory="*AppData\\Local\\Temp*"


Findings:


Executed Binary: IonicLarge.exe


Original Filename: PalitExplorer.exe (revealed via OriginalFileName field analysis using index=* Image="*IonicLarge.exe*").


Phase 3: Defense Evasion & Persistence


Objective: Determine how the malware tampered with local defenses.


Splunk Queries:


Registry activity: index=* Image="*IonicLarge.exe*" EventCode=13


Process termination: index=* "taskkill"


PowerShell Defender overrides: index=* "WMIC" "MSFT_MpPreference" | table _time, CommandLine | sort _time


Findings:


Targeted Registry Path: HKLM\SOFTWARE\Policies\Microsoft\Windows Defender


Terminated & Deleted Binaries: phcIAmLJMAIMSa9j9MpgJo1m.exe,WvmIOrcfsuILdX6SNwIRmGOJ.exe


Powershell Evasion Chain: The attacker executed WMIC commands modifying MSFT_MpPreference threat default actions to bypass Defender detections for four specific Threat IDs (2147735503,2147737010,2147737007,2147737394).


Phase 4: Alternate Persistence & Module Loading


Objective: Trace execution in other user directories and inspect DLL dependencies.


Splunk Queries:


Execution tracking: index=* EventCode=1 Image="*Roaming*"


Loaded modules: index=* EventCode=7 Image="*EasyCalc.exe*"


Findings:


Secondary Execution Path: C:\Users\Finance01\AppData\Roaming\EasyCalc\EasyCalc.exe


Loaded Malicious DLLs: ffmpeg.dll,nw.dll,nw_elf.dll




Comments

Post a Comment

Popular posts from this blog

TryHackMe - Typo Snare Threat Hunter Simulator (medium level)

-
Image
  Threat Hunt Walkthrough The "Typo Snare" scenario on TryHackMe is a fantastic real-world simulation of a sophisticated, multi-stage attack. It starts with a simple mistake and escalates to a full domain compromise, culminating in ransomware. This post will walk you through the entire attack chain, phase by phase, showing you how to find each piece of evidence using Elastic KQL queries. Phase 1: Initial Access & Execution What Happened: The attack began when the user perry.parsons on workstation WKSTN-03 needed a 7-Zip tool. He googled it, clicked a typosquatted link ( 7zipp.org ), and downloaded a trojanized installer. This installer executed a PowerShell script ( 7z.ps1 ) directly from the attacker's server to establish the initial foothold. How to Find It: You are looking for a PowerShell process that was likely spawned by a browser and contains a command to download and execute a script ( iwr for Invoke-WebRequest and iex for Invoke-Expression ). KQL Query...
Read more

TryHackMe - Matryoshka CFT

-
Image
  Full Walkthrough — Matryoshka Containment Unit Matryoshka Containment Unit is a Docker/container escape challenge that teaches: Docker socket abuse Privileged container escalation Shared volume abuse Remote code execution between containers Namespace escape to the host system Below is the complete attack chain from the first flag to the host flag. 1. Initial Enumeration You started inside the level1 container and performed basic Linux/container enumeration. Commands: ls -la cat /proc/1/cgroup find / -perm -4000 2 >/dev/null find / -name docker.sock 2 >/dev/null What you discovered .dockerenv This indicated you were inside a Docker container. /var/run/docker.sock This was the key vulnerability. Docker socket exposure means: the container can communicate directly with the Docker daemon running on the host anyone with access to the socket can effectively control Docker on the host machine This is one of the most dangerous Docker misconfigurations. 2. V...
Read more

TryHackMe - Threat Hunting Simulator - Health Hazard

-
Image
  Scenario overview After months of juggling content calendars and caffeine-fueled brainstorming, co-founder Tom Whiskers finally carved out time to build the company’s first website. It was supposed to be simple: follow a tutorial, install a few packages, and bring the brand to life with lightweight JavaScript magic.   But between sleepless nights and copy-pasted code, Tom started feeling off. Not sick exactly, just off. The terminal scrolled with reassuring green text, the site loaded fine, and everything looked normal.   Then, a strange file appeared on the system. No one could say where it came from. It wasn’t part of the tutorial, didn’t match any known dependencies, and didn’t even run.   It just waited.   Scenario objectives Determine how a threat actor first gained a foothold on the system. Identify suspicious activity that may point to the initial compromise method. Investigate signs of malicious execution following the initial access. Analyse the logs ...
Read more