Hammered Cyberdefenders
Category : Digital Forensics Log Analysis Honeypot Apache2
Last updated
Category : Digital Forensics Log Analysis Honeypot Apache2
Last updated
This challenge takes you into the world of virtual systems and confusing log data. In this challenge, figure out what happened to this webserver honeypot using the logs from a possibly compromised server.
Challenge files:
kern.log
auth.log
daemon.log
dmesg
apache2
let's investigate auth.log file to see the authentication of accounts
by greping failed authentication attempets we can see that there are many attempts to login by sshd .
okay the service is ssh
Ans : ssh
we can look in the kern.log file, as it contains information logged by the kernel
Ans : 4.2.4-1ubuntu3
We can back to auth.log file to see which account was successfully login
Ans : root
let's grep failed auth ip
and success ip
By comparing them we found it's 6 login to system
219.150.161.20, 222.66.204.246, 121.11.66.70, 222.169.224.197, 122.226.202.12, 61.168.227.12
Ans : 6
The two IP addresses 188.131.23.37 and 219.150.161.20 are the highest value
but 188.131.23.37 appears only six times in auth.log, and appears 219.150.161.20 many times.
Ans : 219.150.161.20
The requests store in www-access.log
Ans : 365
Ans : 6
We can Look for installed package in dpkg.log file
Ans : nmap
back to auth.log file and grep login success from the attacker ip address
last log in Apr 19 05:56:05
Ans : 04/19/2010 05:56:05 AM
database information stores in daemon.log
The most dangerous one is creates root users without passwords
Ans : mysql.user contains 2 root accounts without password!
grep the time in the Q
Ans : wind3str0y
Grep User-Agent Value from www-access.log file
Ans : pxyscand/2.1 Thanks UUUUUUUUUUUUUUUUUU 🥰