hacktricks/forensics/basic-forensics-esp/linux-forensics.md

Linux Forensics

Initial Information Gathering

Basic Information

First of all, it's recommended to have some USB with good known binaries and libraries on it you can just get a ubuntu and copy the folders _/bin_, _/sbin_, _/lib,_ and _/lib64_, then mount the USN, and modify the env variables to use those binaries:

export PATH=/mnt/usb/bin:/mnt/usb/sbin
export LD_LIBRARY_PATH=/mnt/usb/lib:/mnt/usb/lib64

Once you have configured the system to use good and known binaries you can start extracting some basic information:

date #Date and time (Clock my be skewed, Might be in different timezone)
uname -a #OS info
ifconfig -a || ip a #Network interfaces (promiscuosu mode?)
ps -ef #Running processes
netstat -anp #Proccess and ports
lsof -V #Open files
netstat -rn; route #Routing table
df; mount #Free space and mounted devices
free #Meam and swap space
w #Who is connected
last -Faiwx #Logins
lsmod #What is loaded
cat /etc/passwd #Unexpected data?
cat /etc/shadow #Unexpected data?
find /directory -type f -mtime -1 -print #Find modified files during the last minute in the directory

Suspicious information

While obtaining the basic information you should check for weird things like:

• root processes usually run with low PIDS, so if you find a root process with a big PID you may suspect
• Check registered logins of users without a shell inside /etc/passwd
• Check for password hashes inside /etc/shadow for users without a shell

Memory Dump

In order to obtain the memory of the running system it's recommended to use LiME.
In order to compile it you need to use the exact same kernel the victim machine is using.

{% hint style="info" %} Remember that you cannot install LiME or any other thing in the victim machine it will make several changes to it {% endhint %}

So, if you have an identical version of Ubuntu you can use apt-get install lime-forensics-dkms
In other cases you need to download LiME from github can compile it with correct kernel headers. In order to obtain the exact kernel headers of the victim machine, you can just copy the directory /lib/modules/<kernel version> to your machine, and then compile LiME using them:

make -C /lib/modules/<kernel version>/build M=$PWD
sudo insmod lime.ko "path=/home/sansforensics/Desktop/mem_dump.bin format=lime"

LiME supports 3 formats:

• Raw every segment concatenated together
• Padded same as raw, but with zeroes in right bits
• Lime (recommended format with metadata

LiME can also be use to send the dump via network instead of storing it on the system using something like: path=tcp:4444

Disk Imaging

Shutting down

First of all you will need to shutdown the system. This isn't always an option as some times system will be a production server that the company cannot afford to shutdown.
There are 2 ways of shutting down the system, a normal shutdown and a "plug the plug" shutdown. The first one will allow the processes to terminate as usual and the filesystem to be synchronized, but I will also allow the possible malware to destroy evidences. The "pull the plug" approach may carry some information loss as we have already took an image of the memory not much info is going to be lost and the malware won't have any opportunity to do anything about it. Therefore, if you suspect that there may be a malware, just execute the sync command on the system and pull the plug.

Taking an image of the disk

It's important to note that before connecting to your computer anything related to the case, you need to be sure that it's going to be mounted as read only to avoid modifying the any information.

#Create a raw copy of the disk
dd if=<subject device> of=<image file> bs=512

#Raw copy with hashes along the way (more secur s it checks hashes while it's copying the data)
dcfldd if=<subject device> of=<image file> bs=512 hash=<algorithm> hashwindow=<chunk size> hashlog=<hash file>
dcfldd if=/dev/sdc of=/media/usb/pc.image hash=sha256 hashwindow=1M hashlog=/media/usb/pc.hashes

Search for known Malware

Modified System Files

Some Linux systems have a feature to verify the integrity of many installed components, providing an effective way to identify unusual or out of place files. For instance, rpm -Va on Linux is designed to verify all packages that were installed using RedHat Package Manager.

#RedHat
rpm -Va
#Debian
dpkg --verify
debsums | grep -v "OK$" #apt-get install debsums

Malware/Rootkit Detectors

Read the following page to learn about tools that can be useful to find malware:

{% page-ref page="../malware-analysis.md" %}

Search installed programs

Package Manager

On Debian-based systems, the /var/ lib/dpkg/status file contains details about installed packages and the /var/log/dpkg.log file records information when a package is installed.
On RedHat and related Linux distributions the rpm -qa --root=/ mntpath/var/lib/rpm command will list the contents of an RPM database on a subject systems.

#Debian
cat /var/lib/dpkg/status | grep -E "Package:|Status:"
cat /var/log/dpkg.log | grep installed
#RedHat
rpm -qa --root=/ mntpath/var/lib/rpm

Other

Not all installed programs will be listed by the above commands because some applications are not available as packages for certain systems and must be installed from source. Therefore, a review of locations such as /usr/local and /opt may reveal other applications that have been compiled and installed from source code.

ls /opt /usr/local

Another good idea is to check the common folders inside $PATH for binaries not related to installed packages:

#Both lines are going to print the executables in /sbin non related to installed packages
#Debian
find /sbin/ -exec dpkg -S {} \; | grep "no path found"
#RedHat
find /sbin/ –exec rpm -qf {} \; | grep "is not"

Inspect AutoStart locations

Scheduled Tasks

cat /var/spool/cron/crontabs/*  \
/var/spool/cron/atjobs \
/var/spool/anacron \
/etc/cron* \
/etc/at* \
/etc/anacrontab \
/etc/incron.d/* \
/var/spool/incron/* \

#MacOS
ls -l /usr/lib/cron/tabs/ /Library/LaunchAgents/ /Library/LaunchDaemons/ ~/Library/LaunchAgents/

Services

It is extremely common for malware to entrench itself as a new, unauthorized service. Linux has a number of scripts that are used to start services as the computer boots. The initialization startup script /etc/inittab calls other scripts such as rc.sysinit and various startup scripts under the /etc/rc.d/ directory, or /etc/rc.boot/ in some older versions. On other versions of Linux, such as Debian, startup scripts are stored in the /etc/init.d/ directory. In addition, some common services are enabled in /etc/inetd.conf or /etc/xinetd/ depending on the version of Linux. Digital investigators should inspect each of these startup scripts for anomalous entries.

• /etc/inittab
• /etc/rc.d/
• /etc/rc.boot/
• /etc/init.d/
• /etc/inetd.conf
• /etc/xinetd/
• /etc/systemd/system
• /etc/systemd/system/multi-user.target.wants/

Kernel Modules

On Linux systems, kernel modules are commonly used as rootkit components to malware packages. Kernel modules are loaded when the system boots up based on the configuration information in the /lib/modules/'uname -r' and /etc/modprobe.d directories, and the /etc/modprobe or /etc/modprobe.conf file. These areas should be inspected for items that are related to malware.

Other AutoStart Locations

There are several configuration files that Linux uses to automatically launch an executable when a user logs into the system that may contain traces of malware.

• /etc/profile.d/* , /etc/profile , /etc/bash.bashrc are executed when any user account logs in.
• ∼/.bashrc , ∼/.bash_profile , ∼/.config/autostart are executed when the specific user logs in.

Examine Logs

Look in all available log files on the compromised system for traces of malicious execution and associated activities such as creation of a new service.

Pure Logs

Logon events recorded in the system and security logs, including logons via the network, can reveal that malware or an intruder gained access to a compromised system via a given account at a specific time. Other events around the time of a malware infection can be captured in system logs, including the creation of a new service or new accounts around the time of an incident.
Interesting system logons:

• /var/log/syslog debian ****or /var/log/messages Redhat
• Shows general messages and info regarding the system. Basically a data log of all activity throughout the global system.
• /var/log/auth.log debian ****or /var/log/secure Redhat
• Keep authentication logs for both successful or failed logins, and authentication processes. Storage depends on system type.
• cat /var/log/auth.log | grep -iE "session opened for|accepted password|new session|not in sudoers"
• /var/log/boot.log: start-up messages and boot info.
• /var/log/maillog or var/log/mail.log: is for mail server logs, handy for postfix, smtpd, or email-related services info running on your server.
• /var/log/kern.log: keeps in Kernel logs and warning info. Kernel activity logs e.g., dmesg, kern.log, klog can show that a particular service crashed repeatedly, potentially indicating that an unstable trojanized version was installed.
• /var/log/dmesg: a repository for device driver messages. Use dmesg to see messages in this file.
• /var/log/faillog: records info on failed logins. Hence, handy for examining potential security breaches like login credential hacks and brute-force attacks.
• /var/log/cron: keeps a record of Crond-related messages cron jobs. Like when the cron daemon started a job.
• /var/log/daemon.log: keeps track of running background services but doesn’t represent them graphically.
• /var/log/btmp: keeps a note of all failed login attempts.
• /var/log/httpd/: a directory containing error_log and access_log files of the Apache httpd daemon. Every error that httpd comes across is kept in the error_log file. Think of memory problems and other system-related errors. access_log logs all requests which come in via HTTP.
• /var/log/mysqld.log or /var/log/mysql.log : MySQL log file that records every debug, failure and success message, including starting, stopping and restarting of MySQL daemon mysqld. The system decides on the directory. RedHat, CentOS, Fedora, and other RedHat-based systems use /var/log/mariadb/mariadb.log. However, Debian/Ubuntu use /var/log/mysql/error.log directory.
• /var/log/xferlog: keeps FTP file transfer sessions. Includes info like file names and user-initiated FTP transfers.
• /var/log/* : You should always check for unexpected logs in this directory

{% hint style="info" %} Linux system logs and audit subsystems may be disabled or deleted in an intrusion or malware incident. In fact, because logs on Linux systems generally contain some of the most useful information about malicious activities, intruders routinely delete them. Therefore, when examining available log files, it is important to look for gaps or out of order entries that might be an indication of deletion or tampering. {% endhint %}

Command History

Many Linux systems are configured to maintain a command history for each user account:

• ~/.bash_history
• ~/.history
• ~/.sh_history
• ~/.*_history

Logins

Using the command last -Faiwx it's possible to get the list of users that have logged in.
It's recommended to check if those logins make sense:

• Any unknown user?
• Any user that shouldn't have a shell has logged in?

This is important as attackers some times may copy /bin/bash inside /bin/false so users like lightdm may be able to login.

Application Traces

• SSH: Connections to systems made using SSH to and from a compromised system result in entries being made in files for each user account _**∼/.ssh/authorized\_keys**_ and _**∼/.ssh/known\_keys**_. These entries can reveal the hostname or IP address of the remote hosts.
• Gnome Desktop: User accounts may have a ∼/.recently-used.xbel file that contains information about files that were recently accessed using applications running in the Gnome desktop.
• VIM: User accounts may have a ∼/.viminfo file that contains details about the use of VIM, including search string history and paths to files that were opened using vim.
• Open Office: Recent files.
• MySQL: User accounts may have a ∼/.mysql_history file that contains queries executed using MySQL.
• Less: User accounts may have a ∼/.lesshst file that contains details about the use of less, including search string history and shell commands executed via less

Review User Accounts and Logon Activities

Examine the /etc/passwd, /etc/shadow and security logs for unusual names or accounts created and/or used in close proximity to known unauthorized events. Also check possible sudo brute-force attacks.
Moreover, check files like /etc/sudoers and /etc/groups for unexpected privileges given to users.
Finally look for accounts with no passwords or easily guessed passwords.

Examine File System

File system data structures can provide substantial amounts of information related to a malware incident, including the timing of events and the actual content of malware.
Malware is increasingly being designed to thwart file system analysis. Some malware alter date-time stamps on malicious files to make it more difficult to find them with time line analysis. Other malicious code is designed to only store certain information in memory to minimize the amount of data stored in the file system.
To deal with such anti-forensic techniques, it is necessary to pay careful attention to time line analysis of file system date-time stamps and to files stored in common locations where malware might be found.

• Using autopsy you can see the timeline of events that may be useful to discover suspicions activity. You can also use the mactime feature from Sleuth Kit directly.
• Check for unexpected scripts inside $PATH maybe some sh or php scripts?
• Files in /dev use to be special files, you may find non-special files here related to malware.
• Look for unusual or hidden files and directories, such as “.. ” dot dot space or “..^G ” dot dot control-G
• setuid copies of /bin/bash on the system find / -user root -perm -04000 –print
• Review date-time stamps of deleted inodes for large numbers of files being deleted around the same time, which might indicate malicious activity such as installation of a rootkit or trojanized service.
• Because inodes are allocated on a next available basis, malicious files placed on the system at around the same time may be assigned consecutive inodes. Therefore, after one component of malware is located, it can be productive to inspect neighbouring inodes.
• Also check directories like /bin or /sbin as the modified and/or changed time of new or modified files me be interesting.
• It's interesting to see the files and folders of a directory sorted by creation date instead alphabetically to see which files/folders are more recent last ones usually.

References

• https://cdn.ttgtmedia.com/rms/security/Malware%20Forensics%20Field%20Guide%20for%20Linux%20Systems_Ch3.pdf
• https://www.plesk.com/blog/featured/linux-logs-explained/

MBR - Master Boot Record

The MBR occupies the sector 0 of the disk the first sector and it's used to indicate the partitions of the disc. This sector is essential to indicate the PC what and from where a partition should be mounted.
It allows up to four partitions at most **just 1** can be active/**bootable**. However, if you need more partitions you can use extended partitions.

Format:

Offset	Length	Item
0 0x00	446(0x1BE)	Boot code
446 0x1BE	16 0x10	First Partition
462 0x1CE	16 0x10	Second Partition
478 0x1DE	16 0x10	Third Partition
494 0x1EE	16 0x10	Fourth Partition
510 0x1FE	2 0x2	Signature 0x55 0xAA

Partition Record Format:

Offset	Length	Item
0 0x00	1 0x01	Active flag 0x80 = bootable
1 0x01	1 0x01	Start head
2 0x02	1 0x01	Start sector bits 0-5; upper bits of cylinder 6- 7
3 0x03	1 0x01	Start cylinder lowest 8 bits
4 0x04	1 0x01	Partition type code 0x83 = Linux
5 0x05	1 0x01	End head
6 0x06	1 0x01	End sector bits 0-5; upper bits of cylinder 6- 7
7 0x07	1 0x01	End cylinder lowest 8 bits
8 0x08	4 0x04	Sectors preceding partition little endian
12 0x0C	4 0x04	Sectors in partition

In order to mount a MBR in Linux you first need to get the start offset you can use `fdisk` and the the `p` command

An then use the following code

#Mount MBR in Linux
mount -o ro,loop,offset=<Bytes>
#63x512 = 32256Bytes
mount -o ro,loop,offset=32256,noatime /path/to/image.dd /media/part/