NahamCon CTF 2023 How i solved Raided Digital Forensics without volatility

0xS1rx58
3 min readJun 17, 2023

--

In this post, I’ll be describing how I solved Raided without volatility

Second Blood

After reading the description we knew its memory image and used to stage attacks and hacker was accessing other systems.

Starting investigation…

its captured from kali

i will use bulk_extractor to extract more data

bulk_extractor -o ./xxx raided-challenge-dump-vmem

-o output

raided-challenge-dump-vmem file name

i got packets.pcap let’s analysis it

i will use tshark to analysis it you can use wireshark

tshark -r packets.pcap

-r set the filename to read from

we found ssh connection 167.172.12.154

i used ping 167.172.12.154 to check if live or not, i got response

we retrieved some command from history of .zsh_history

ssh -i ~/.ssh/id_ed25519 l33t@167.172.12.154

its command to connect with server using private key ~/.ssh/id_ed25519

and user l33t

server ip 167.172.12.154

we can retrieve private key we can use binwalk binwalk — dd=”.*” -C 193056208 -N id_ed25519 raided-challenge-dump-vmem or strings

  • strings raided-challenge-dump-vmem | grep “PRIVATE KEY” -A 10
  • we know a header of private keys its begin with
  • — — -BEGIN RSA PRIVATE KEY — — -
  • — — -BEGIN OPENSSH PRIVATE KEY — — -

but i searched using PRIVATE KEY — — — because if we remember file name of ssh is id_ed25519 header will be — — -BEGIN OPENSSH PRIVATE KEY — — -

- note : this command to generate key not to solve ssh-keygen -t ed25519 -f ed25519_key to gene

now try to connect

flag{654e9dc4c424e25423c19c5e64fffb27}

Sign up to discover human stories that deepen your understanding of the world.

Free

Distraction-free reading. No ads.

Organize your knowledge with lists and highlights.

Tell your story. Find your audience.

Membership

Read member-only stories

Support writers you read most

Earn money for your writing

Listen to audio narrations

Read offline with the Medium app

--

--

No responses yet

Write a response