Edit tour

Linux Analysis Report
byte.x86.elf

Overview

General Information

Sample name:	byte.x86.elf
Analysis ID:	1579451
MD5:	7f450c92cd48f89e76cc42545287a95c
SHA1:	417afaa1961773ef81080998fbeeb04e112e8f30
SHA256:	883e0e27500a5dd5d22ebe043110896ec2223dfb1ce2dd152fe2da1a7f85aca0
Tags:	elfuser-abuse_ch
Infos:

Detection

Mirai, Okiru

Score:	96
Range:	0 - 100
Whitelisted:	false

Signatures

Malicious sample detected (through community Yara rule)

Multi AV Scanner detection for submitted file

Sample tries to kill a massive number of system processes

Yara detected Mirai

Yara detected Okiru

Machine Learning detection for sample

Sample is packed with UPX

Sample reads /proc/mounts (often used for finding a writable filesystem)

Sample tries to kill multiple processes (SIGKILL)

Creates hidden files and/or directories

Deletes log files

Detected TCP or UDP traffic on non-standard ports

ELF contains segments with high entropy indicating compressed/encrypted content

Enumerates processes within the "proc" file system

Executes commands using a shell command-line interpreter

Executes the "grep" command used to find patterns in files or piped streams

Executes the "kill" or "pkill" command typically used to terminate processes

Reads CPU information from /sys indicative of miner or evasive malware

Reads the 'hosts' file potentially containing internal network hosts

Sample contains only a LOAD segment without any section mappings

Sample tries to kill a process (SIGKILL)

Tries to connect to HTTP servers, but all servers are down (expired dropper behavior)

Uses the "uname" system call to query kernel version information (possible evasion)

Yara signature match

Classification

General Information

Joe Sandbox version:	41.0.0 Charoite
Analysis ID:	1579451
Start date and time:	2024-12-22 12:56:04 +01:00
Joe Sandbox product:	CloudBasic
Overall analysis duration:	0h 4m 8s
Hypervisor based Inspection enabled:	false
Report type:	full
Cookbook file name:	defaultlinuxfilecookbook.jbs
Analysis system description:	Ubuntu Linux 20.04 x64 (Kernel 5.4.0-72, Firefox 91.0, Evince Document Viewer 3.36.10, LibreOffice 6.4.7.2, OpenJDK 11.0.11)
Analysis Mode:	default
Sample name:	byte.x86.elf
Detection:	MAL
Classification:	mal96.spre.troj.evad.linELF@0/24@95/0

Warnings

Connection to analysis system has been lost, crash info: Unknown
VT rate limit hit for: vbtgsze.r-e.kr

Process Tree

system is lnxubuntu20

byte.x86.elf (PID: 6237, Parent: 6163, MD5: 7f450c92cd48f89e76cc42545287a95c) Arguments: /tmp/byte.x86.elf

byte.x86.elf New Fork (PID: 6238, Parent: 6237)

byte.x86.elf New Fork (PID: 6239, Parent: 6237)

byte.x86.elf New Fork (PID: 6240, Parent: 6237)

byte.x86.elf New Fork (PID: 6241, Parent: 6240)

byte.x86.elf New Fork (PID: 6242, Parent: 6240)

systemd New Fork (PID: 6279, Parent: 1)

dbus-daemon (PID: 6279, Parent: 1, MD5: 3089d47e3f3ab84cd81c48fd406d7a8c) Arguments: /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

systemd New Fork (PID: 6280, Parent: 1)

rsyslogd (PID: 6280, Parent: 1, MD5: 0b8087fc907c42eb3c81a691db258e33) Arguments: /usr/sbin/rsyslogd -n -iNONE

systemd New Fork (PID: 6281, Parent: 1860)

pulseaudio (PID: 6281, Parent: 1860, MD5: 0c3b4c789d8ffb12b25507f27e14c186) Arguments: /usr/bin/pulseaudio --daemonize=no --log-target=journal

gvfsd-fuse New Fork (PID: 6282, Parent: 2038)

fusermount (PID: 6282, Parent: 2038, MD5: 576a1b135c82bdcbc97a91acea900566) Arguments: fusermount -u -q -z -- /run/user/1000/gvfs

systemd New Fork (PID: 6291, Parent: 1)

dbus-daemon (PID: 6291, Parent: 1, MD5: 3089d47e3f3ab84cd81c48fd406d7a8c) Arguments: /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

systemd New Fork (PID: 6292, Parent: 1)

rsyslogd (PID: 6292, Parent: 1, MD5: 0b8087fc907c42eb3c81a691db258e33) Arguments: /usr/sbin/rsyslogd -n -iNONE

systemd New Fork (PID: 6294, Parent: 1860)

pulseaudio (PID: 6294, Parent: 1860, MD5: 0c3b4c789d8ffb12b25507f27e14c186) Arguments: /usr/bin/pulseaudio --daemonize=no --log-target=journal

systemd New Fork (PID: 6304, Parent: 1)

systemd-logind (PID: 6304, Parent: 1, MD5: 8dd58a1b4c12f7a1d5fe3ce18b2aaeef) Arguments: /lib/systemd/systemd-logind

systemd New Fork (PID: 6361, Parent: 1)

rtkit-daemon (PID: 6361, Parent: 1, MD5: df0cacf1db4ec95ac70f5b6e06b8ffd7) Arguments: /usr/libexec/rtkit-daemon

gdm3 New Fork (PID: 6362, Parent: 1320)

Default (PID: 6362, Parent: 1320, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: /etc/gdm3/PrimeOff/Default

gdm3 New Fork (PID: 6365, Parent: 1320)

Default (PID: 6365, Parent: 1320, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: /etc/gdm3/PrimeOff/Default

gdm3 New Fork (PID: 6366, Parent: 1320)

Default (PID: 6366, Parent: 1320, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: /etc/gdm3/PrimeOff/Default

systemd New Fork (PID: 6370, Parent: 1)

polkitd (PID: 6370, Parent: 1, MD5: 8efc9b4b5b524210ad2ea1954a9d0e69) Arguments: /usr/lib/policykit-1/polkitd --no-debug

systemd New Fork (PID: 6375, Parent: 1)

dbus-daemon (PID: 6375, Parent: 1, MD5: 3089d47e3f3ab84cd81c48fd406d7a8c) Arguments: /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

systemd New Fork (PID: 6377, Parent: 1)

gpu-manager (PID: 6377, Parent: 1, MD5: 8fae9dd5dd67e1f33d873089c2fd8761) Arguments: /usr/bin/gpu-manager --log /var/log/gpu-manager.log

gpu-manager New Fork (PID: 6381, Parent: 6377)

sh (PID: 6381, Parent: 6377, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: sh -c "grep -G \"^blacklist.*nvidia[[:space:]]*$\" /etc/modprobe.d/*.conf"

sh New Fork (PID: 6382, Parent: 6381)

grep (PID: 6382, Parent: 6381, MD5: 1e6ebb9dd094f774478f72727bdba0f5) Arguments: grep -G ^blacklist.*nvidia[[:space:]]*$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf

gpu-manager New Fork (PID: 6383, Parent: 6377)

sh (PID: 6383, Parent: 6377, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: sh -c "grep -G \"^blacklist.*nvidia[[:space:]]*$\" /lib/modprobe.d/*.conf"

sh New Fork (PID: 6387, Parent: 6383)

grep (PID: 6387, Parent: 6383, MD5: 1e6ebb9dd094f774478f72727bdba0f5) Arguments: grep -G ^blacklist.*nvidia[[:space:]]*$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf

gpu-manager New Fork (PID: 6388, Parent: 6377)

sh (PID: 6388, Parent: 6377, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: sh -c "grep -G \"^blacklist.*radeon[[:space:]]*$\" /etc/modprobe.d/*.conf"

sh New Fork (PID: 6389, Parent: 6388)

grep (PID: 6389, Parent: 6388, MD5: 1e6ebb9dd094f774478f72727bdba0f5) Arguments: grep -G ^blacklist.*radeon[[:space:]]*$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf

gpu-manager New Fork (PID: 6391, Parent: 6377)

sh (PID: 6391, Parent: 6377, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: sh -c "grep -G \"^blacklist.*radeon[[:space:]]*$\" /lib/modprobe.d/*.conf"

sh New Fork (PID: 6392, Parent: 6391)

grep (PID: 6392, Parent: 6391, MD5: 1e6ebb9dd094f774478f72727bdba0f5) Arguments: grep -G ^blacklist.*radeon[[:space:]]*$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf

gpu-manager New Fork (PID: 6395, Parent: 6377)

sh (PID: 6395, Parent: 6377, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: sh -c "grep -G \"^blacklist.*amdgpu[[:space:]]*$\" /etc/modprobe.d/*.conf"

sh New Fork (PID: 6396, Parent: 6395)

grep (PID: 6396, Parent: 6395, MD5: 1e6ebb9dd094f774478f72727bdba0f5) Arguments: grep -G ^blacklist.*amdgpu[[:space:]]*$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf

gpu-manager New Fork (PID: 6404, Parent: 6377)

sh (PID: 6404, Parent: 6377, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: sh -c "grep -G \"^blacklist.*amdgpu[[:space:]]*$\" /lib/modprobe.d/*.conf"

systemd New Fork (PID: 6378, Parent: 1860)

pulseaudio (PID: 6378, Parent: 1860, MD5: 0c3b4c789d8ffb12b25507f27e14c186) Arguments: /usr/bin/pulseaudio --daemonize=no --log-target=journal

systemd New Fork (PID: 6379, Parent: 1)

rsyslogd (PID: 6379, Parent: 1, MD5: 0b8087fc907c42eb3c81a691db258e33) Arguments: /usr/sbin/rsyslogd -n -iNONE

systemd New Fork (PID: 6394, Parent: 1)

rtkit-daemon (PID: 6394, Parent: 1, MD5: df0cacf1db4ec95ac70f5b6e06b8ffd7) Arguments: /usr/libexec/rtkit-daemon

systemd New Fork (PID: 6402, Parent: 1)

polkitd (PID: 6402, Parent: 1, MD5: 8efc9b4b5b524210ad2ea1954a9d0e69) Arguments: /usr/lib/policykit-1/polkitd --no-debug

systemd New Fork (PID: 6405, Parent: 1)

dbus-daemon (PID: 6405, Parent: 1, MD5: 3089d47e3f3ab84cd81c48fd406d7a8c) Arguments: /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

systemd New Fork (PID: 6406, Parent: 1)

generate-config (PID: 6406, Parent: 1, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: /usr/share/gdm/generate-config

generate-config New Fork (PID: 6407, Parent: 6406)

pkill (PID: 6407, Parent: 6406, MD5: fa96a75a08109d8842e4865b2907d51f) Arguments: pkill --signal HUP --uid gdm dconf-service

systemd New Fork (PID: 6408, Parent: 1860)

pulseaudio (PID: 6408, Parent: 1860, MD5: 0c3b4c789d8ffb12b25507f27e14c186) Arguments: /usr/bin/pulseaudio --daemonize=no --log-target=journal

systemd New Fork (PID: 6409, Parent: 1)

rsyslogd (PID: 6409, Parent: 1, MD5: 0b8087fc907c42eb3c81a691db258e33) Arguments: /usr/sbin/rsyslogd -n -iNONE

systemd New Fork (PID: 6419, Parent: 1)

rtkit-daemon (PID: 6419, Parent: 1, MD5: df0cacf1db4ec95ac70f5b6e06b8ffd7) Arguments: /usr/libexec/rtkit-daemon

systemd New Fork (PID: 6423, Parent: 1)

dbus-daemon (PID: 6423, Parent: 1, MD5: 3089d47e3f3ab84cd81c48fd406d7a8c) Arguments: /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

systemd New Fork (PID: 6426, Parent: 1860)

pulseaudio (PID: 6426, Parent: 1860, MD5: 0c3b4c789d8ffb12b25507f27e14c186) Arguments: /usr/bin/pulseaudio --daemonize=no --log-target=journal

systemd New Fork (PID: 6427, Parent: 1)

rsyslogd (PID: 6427, Parent: 1, MD5: 0b8087fc907c42eb3c81a691db258e33) Arguments: /usr/sbin/rsyslogd -n -iNONE

systemd New Fork (PID: 6429, Parent: 1)

gpu-manager (PID: 6429, Parent: 1, MD5: 8fae9dd5dd67e1f33d873089c2fd8761) Arguments: /usr/bin/gpu-manager --log /var/log/gpu-manager.log

gpu-manager New Fork (PID: 6433, Parent: 6429)

sh (PID: 6433, Parent: 6429, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: sh -c "grep -G \"^blacklist.*nvidia[[:space:]]*$\" /etc/modprobe.d/*.conf"

sh New Fork (PID: 6434, Parent: 6433)

grep (PID: 6434, Parent: 6433, MD5: 1e6ebb9dd094f774478f72727bdba0f5) Arguments: grep -G ^blacklist.*nvidia[[:space:]]*$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf

gpu-manager New Fork (PID: 6436, Parent: 6429)

sh (PID: 6436, Parent: 6429, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: sh -c "grep -G \"^blacklist.*nvidia[[:space:]]*$\" /lib/modprobe.d/*.conf"

sh New Fork (PID: 6437, Parent: 6436)

grep (PID: 6437, Parent: 6436, MD5: 1e6ebb9dd094f774478f72727bdba0f5) Arguments: grep -G ^blacklist.*nvidia[[:space:]]*$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf

gpu-manager New Fork (PID: 6438, Parent: 6429)

sh (PID: 6438, Parent: 6429, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: sh -c "grep -G \"^blacklist.*radeon[[:space:]]*$\" /etc/modprobe.d/*.conf"

sh New Fork (PID: 6439, Parent: 6438)

grep (PID: 6439, Parent: 6438, MD5: 1e6ebb9dd094f774478f72727bdba0f5) Arguments: grep -G ^blacklist.*radeon[[:space:]]*$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf

gpu-manager New Fork (PID: 6440, Parent: 6429)

sh (PID: 6440, Parent: 6429, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: sh -c "grep -G \"^blacklist.*radeon[[:space:]]*$\" /lib/modprobe.d/*.conf"

sh New Fork (PID: 6441, Parent: 6440)

grep (PID: 6441, Parent: 6440, MD5: 1e6ebb9dd094f774478f72727bdba0f5) Arguments: grep -G ^blacklist.*radeon[[:space:]]*$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf

gpu-manager New Fork (PID: 6442, Parent: 6429)

sh (PID: 6442, Parent: 6429, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: sh -c "grep -G \"^blacklist.*amdgpu[[:space:]]*$\" /etc/modprobe.d/*.conf"

sh New Fork (PID: 6443, Parent: 6442)

grep (PID: 6443, Parent: 6442, MD5: 1e6ebb9dd094f774478f72727bdba0f5) Arguments: grep -G ^blacklist.*amdgpu[[:space:]]*$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf

gpu-manager New Fork (PID: 6446, Parent: 6429)

sh (PID: 6446, Parent: 6429, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: sh -c "grep -G \"^blacklist.*amdgpu[[:space:]]*$\" /lib/modprobe.d/*.conf"

sh New Fork (PID: 6447, Parent: 6446)

grep (PID: 6447, Parent: 6446, MD5: 1e6ebb9dd094f774478f72727bdba0f5) Arguments: grep -G ^blacklist.*amdgpu[[:space:]]*$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf

systemd New Fork (PID: 6445, Parent: 1)

rtkit-daemon (PID: 6445, Parent: 1, MD5: df0cacf1db4ec95ac70f5b6e06b8ffd7) Arguments: /usr/libexec/rtkit-daemon

systemd New Fork (PID: 6448, Parent: 1)

dbus-daemon (PID: 6448, Parent: 1, MD5: 3089d47e3f3ab84cd81c48fd406d7a8c) Arguments: /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

systemd New Fork (PID: 6449, Parent: 1)

generate-config (PID: 6449, Parent: 1, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: /usr/share/gdm/generate-config

generate-config New Fork (PID: 6450, Parent: 6449)

pkill (PID: 6450, Parent: 6449, MD5: fa96a75a08109d8842e4865b2907d51f) Arguments: pkill --signal HUP --uid gdm dconf-service

systemd New Fork (PID: 6451, Parent: 1860)

pulseaudio (PID: 6451, Parent: 1860, MD5: 0c3b4c789d8ffb12b25507f27e14c186) Arguments: /usr/bin/pulseaudio --daemonize=no --log-target=journal

systemd New Fork (PID: 6452, Parent: 1)

rsyslogd (PID: 6452, Parent: 1, MD5: 0b8087fc907c42eb3c81a691db258e33) Arguments: /usr/sbin/rsyslogd -n -iNONE

systemd New Fork (PID: 6454, Parent: 1)

dbus-daemon (PID: 6454, Parent: 1, MD5: 3089d47e3f3ab84cd81c48fd406d7a8c) Arguments: /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

systemd New Fork (PID: 6462, Parent: 1)

rtkit-daemon (PID: 6462, Parent: 1, MD5: df0cacf1db4ec95ac70f5b6e06b8ffd7) Arguments: /usr/libexec/rtkit-daemon

systemd New Fork (PID: 6466, Parent: 1)

polkitd (PID: 6466, Parent: 1, MD5: 8efc9b4b5b524210ad2ea1954a9d0e69) Arguments: /usr/lib/policykit-1/polkitd --no-debug

systemd New Fork (PID: 6470, Parent: 1)

dbus-daemon (PID: 6470, Parent: 1, MD5: 3089d47e3f3ab84cd81c48fd406d7a8c) Arguments: /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

systemd New Fork (PID: 6471, Parent: 1860)

pulseaudio (PID: 6471, Parent: 1860, MD5: 0c3b4c789d8ffb12b25507f27e14c186) Arguments: /usr/bin/pulseaudio --daemonize=no --log-target=journal

systemd New Fork (PID: 6472, Parent: 1)

rsyslogd (PID: 6472, Parent: 1, MD5: 0b8087fc907c42eb3c81a691db258e33) Arguments: /usr/sbin/rsyslogd -n -iNONE

systemd New Fork (PID: 6474, Parent: 1)

gpu-manager (PID: 6474, Parent: 1, MD5: 8fae9dd5dd67e1f33d873089c2fd8761) Arguments: /usr/bin/gpu-manager --log /var/log/gpu-manager.log

gpu-manager New Fork (PID: 6478, Parent: 6474)

sh (PID: 6478, Parent: 6474, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: sh -c "grep -G \"^blacklist.*nvidia[[:space:]]*$\" /etc/modprobe.d/*.conf"

sh New Fork (PID: 6479, Parent: 6478)

grep (PID: 6479, Parent: 6478, MD5: 1e6ebb9dd094f774478f72727bdba0f5) Arguments: grep -G ^blacklist.*nvidia[[:space:]]*$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf

gpu-manager New Fork (PID: 6481, Parent: 6474)

sh (PID: 6481, Parent: 6474, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: sh -c "grep -G \"^blacklist.*nvidia[[:space:]]*$\" /lib/modprobe.d/*.conf"

sh New Fork (PID: 6484, Parent: 6481)

grep (PID: 6484, Parent: 6481, MD5: 1e6ebb9dd094f774478f72727bdba0f5) Arguments: grep -G ^blacklist.*nvidia[[:space:]]*$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf

gpu-manager New Fork (PID: 6485, Parent: 6474)

sh (PID: 6485, Parent: 6474, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: sh -c "grep -G \"^blacklist.*radeon[[:space:]]*$\" /etc/modprobe.d/*.conf"

sh New Fork (PID: 6486, Parent: 6485)

grep (PID: 6486, Parent: 6485, MD5: 1e6ebb9dd094f774478f72727bdba0f5) Arguments: grep -G ^blacklist.*radeon[[:space:]]*$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf

gpu-manager New Fork (PID: 6487, Parent: 6474)

sh (PID: 6487, Parent: 6474, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: sh -c "grep -G \"^blacklist.*radeon[[:space:]]*$\" /lib/modprobe.d/*.conf"

sh New Fork (PID: 6488, Parent: 6487)

grep (PID: 6488, Parent: 6487, MD5: 1e6ebb9dd094f774478f72727bdba0f5) Arguments: grep -G ^blacklist.*radeon[[:space:]]*$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf

gpu-manager New Fork (PID: 6491, Parent: 6474)

sh (PID: 6491, Parent: 6474, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: sh -c "grep -G \"^blacklist.*amdgpu[[:space:]]*$\" /etc/modprobe.d/*.conf"

sh New Fork (PID: 6492, Parent: 6491)

grep (PID: 6492, Parent: 6491, MD5: 1e6ebb9dd094f774478f72727bdba0f5) Arguments: grep -G ^blacklist.*amdgpu[[:space:]]*$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf

gpu-manager New Fork (PID: 6497, Parent: 6474)

sh (PID: 6497, Parent: 6474, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: sh -c "grep -G \"^blacklist.*amdgpu[[:space:]]*$\" /lib/modprobe.d/*.conf"

sh New Fork (PID: 6498, Parent: 6497)

grep (PID: 6498, Parent: 6497, MD5: 1e6ebb9dd094f774478f72727bdba0f5) Arguments: grep -G ^blacklist.*amdgpu[[:space:]]*$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf

systemd New Fork (PID: 6490, Parent: 1)

rtkit-daemon (PID: 6490, Parent: 1, MD5: df0cacf1db4ec95ac70f5b6e06b8ffd7) Arguments: /usr/libexec/rtkit-daemon

systemd New Fork (PID: 6496, Parent: 1)

polkitd (PID: 6496, Parent: 1, MD5: 8efc9b4b5b524210ad2ea1954a9d0e69) Arguments: /usr/lib/policykit-1/polkitd --no-debug

systemd New Fork (PID: 6502, Parent: 1)

dbus-daemon (PID: 6502, Parent: 1, MD5: 3089d47e3f3ab84cd81c48fd406d7a8c) Arguments: /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

systemd New Fork (PID: 6503, Parent: 1)

generate-config (PID: 6503, Parent: 1, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: /usr/share/gdm/generate-config

generate-config New Fork (PID: 6505, Parent: 6503)

pkill (PID: 6505, Parent: 6503, MD5: fa96a75a08109d8842e4865b2907d51f) Arguments: pkill --signal HUP --uid gdm dconf-service

systemd New Fork (PID: 6504, Parent: 1860)

pulseaudio (PID: 6504, Parent: 1860, MD5: 0c3b4c789d8ffb12b25507f27e14c186) Arguments: /usr/bin/pulseaudio --daemonize=no --log-target=journal

systemd New Fork (PID: 6506, Parent: 1)

rsyslogd (PID: 6506, Parent: 1, MD5: 0b8087fc907c42eb3c81a691db258e33) Arguments: /usr/sbin/rsyslogd -n -iNONE

systemd New Fork (PID: 6515, Parent: 1)

dbus-daemon (PID: 6515, Parent: 1, MD5: 3089d47e3f3ab84cd81c48fd406d7a8c) Arguments: /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

systemd New Fork (PID: 6516, Parent: 1)

rsyslogd (PID: 6516, Parent: 1, MD5: 0b8087fc907c42eb3c81a691db258e33) Arguments: /usr/sbin/rsyslogd -n -iNONE

systemd New Fork (PID: 6518, Parent: 1860)

pulseaudio (PID: 6518, Parent: 1860, MD5: 0c3b4c789d8ffb12b25507f27e14c186) Arguments: /usr/bin/pulseaudio --daemonize=no --log-target=journal

systemd New Fork (PID: 6519, Parent: 1)

gpu-manager (PID: 6519, Parent: 1, MD5: 8fae9dd5dd67e1f33d873089c2fd8761) Arguments: /usr/bin/gpu-manager --log /var/log/gpu-manager.log

gpu-manager New Fork (PID: 6523, Parent: 6519)

sh (PID: 6523, Parent: 6519, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: sh -c "grep -G \"^blacklist.*nvidia[[:space:]]*$\" /etc/modprobe.d/*.conf"

systemd New Fork (PID: 6524, Parent: 1)

dbus-daemon (PID: 6524, Parent: 1, MD5: 3089d47e3f3ab84cd81c48fd406d7a8c) Arguments: /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

systemd New Fork (PID: 6525, Parent: 1)

generate-config (PID: 6525, Parent: 1, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: /usr/share/gdm/generate-config

systemd New Fork (PID: 6526, Parent: 1)

rsyslogd (PID: 6526, Parent: 1, MD5: 0b8087fc907c42eb3c81a691db258e33) Arguments: /usr/sbin/rsyslogd -n -iNONE

systemd New Fork (PID: 6528, Parent: 1)

dbus-daemon (PID: 6528, Parent: 1, MD5: 3089d47e3f3ab84cd81c48fd406d7a8c) Arguments: /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

systemd New Fork (PID: 6529, Parent: 1860)

pulseaudio (PID: 6529, Parent: 1860, MD5: 0c3b4c789d8ffb12b25507f27e14c186) Arguments: /usr/bin/pulseaudio --daemonize=no --log-target=journal

systemd New Fork (PID: 6533, Parent: 1)

gpu-manager (PID: 6533, Parent: 1, MD5: 8fae9dd5dd67e1f33d873089c2fd8761) Arguments: /usr/bin/gpu-manager --log /var/log/gpu-manager.log

systemd New Fork (PID: 6535, Parent: 1)

generate-config (PID: 6535, Parent: 1, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: /usr/share/gdm/generate-config

generate-config New Fork (PID: 6537, Parent: 6535)

pkill (PID: 6537, Parent: 6535, MD5: fa96a75a08109d8842e4865b2907d51f) Arguments: pkill --signal HUP --uid gdm dconf-service

systemd New Fork (PID: 6536, Parent: 1)

rsyslogd (PID: 6536, Parent: 1, MD5: 0b8087fc907c42eb3c81a691db258e33) Arguments: /usr/sbin/rsyslogd -n -iNONE

systemd New Fork (PID: 6538, Parent: 1860)

pulseaudio (PID: 6538, Parent: 1860, MD5: 0c3b4c789d8ffb12b25507f27e14c186) Arguments: /usr/bin/pulseaudio --daemonize=no --log-target=journal

systemd New Fork (PID: 6539, Parent: 1)

rsyslogd (PID: 6539, Parent: 1, MD5: 0b8087fc907c42eb3c81a691db258e33) Arguments: /usr/sbin/rsyslogd -n -iNONE

systemd New Fork (PID: 6540, Parent: 1860)

pulseaudio (PID: 6540, Parent: 1860, MD5: 0c3b4c789d8ffb12b25507f27e14c186) Arguments: /usr/bin/pulseaudio --daemonize=no --log-target=journal

systemd New Fork (PID: 6541, Parent: 1)

rsyslogd (PID: 6541, Parent: 1, MD5: 0b8087fc907c42eb3c81a691db258e33) Arguments: /usr/sbin/rsyslogd -n -iNONE

systemd New Fork (PID: 6542, Parent: 1860)

pulseaudio (PID: 6542, Parent: 1860, MD5: 0c3b4c789d8ffb12b25507f27e14c186) Arguments: /usr/bin/pulseaudio --daemonize=no --log-target=journal

systemd New Fork (PID: 6543, Parent: 1)

rsyslogd (PID: 6543, Parent: 1, MD5: 0b8087fc907c42eb3c81a691db258e33) Arguments: /usr/sbin/rsyslogd -n -iNONE

systemd New Fork (PID: 6544, Parent: 1860)

systemd New Fork (PID: 6545, Parent: 1)

rsyslogd (PID: 6545, Parent: 1, MD5: 0b8087fc907c42eb3c81a691db258e33) Arguments: /usr/sbin/rsyslogd -n -iNONE

systemd New Fork (PID: 6546, Parent: 1860)

pulseaudio (PID: 6546, Parent: 1860, MD5: 0c3b4c789d8ffb12b25507f27e14c186) Arguments: /usr/bin/pulseaudio --daemonize=no --log-target=journal

systemd New Fork (PID: 6547, Parent: 1)

gpu-manager (PID: 6547, Parent: 1, MD5: 8fae9dd5dd67e1f33d873089c2fd8761) Arguments: /usr/bin/gpu-manager --log /var/log/gpu-manager.log

systemd New Fork (PID: 6548, Parent: 1)

generate-config (PID: 6548, Parent: 1, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: /usr/share/gdm/generate-config

systemd New Fork (PID: 6549, Parent: 1)

rsyslogd (PID: 6549, Parent: 1, MD5: 0b8087fc907c42eb3c81a691db258e33) Arguments: /usr/sbin/rsyslogd -n -iNONE

systemd New Fork (PID: 6552, Parent: 1)

gpu-manager (PID: 6552, Parent: 1, MD5: 8fae9dd5dd67e1f33d873089c2fd8761) Arguments: /usr/bin/gpu-manager --log /var/log/gpu-manager.log

systemd New Fork (PID: 6553, Parent: 1)

generate-config (PID: 6553, Parent: 1, MD5: 1e6b1c887c59a315edb7eb9a315fc84c) Arguments: /usr/share/gdm/generate-config

systemd New Fork (PID: 6554, Parent: 1)

gpu-manager (PID: 6554, Parent: 1, MD5: 8fae9dd5dd67e1f33d873089c2fd8761) Arguments: /usr/bin/gpu-manager --log /var/log/gpu-manager.log

systemd New Fork (PID: 6555, Parent: 1)

plymouth (PID: 6555, Parent: 1, MD5: 87003efd8dad470042f5e75360a8f49f) Arguments: /bin/plymouth quit

systemd New Fork (PID: 6580, Parent: 1)

systemd-logind (PID: 6580, Parent: 1, MD5: 8dd58a1b4c12f7a1d5fe3ce18b2aaeef) Arguments: /lib/systemd/systemd-logind

systemd New Fork (PID: 6659, Parent: 1)

systemd New Fork (PID: 6660, Parent: 1)

dbus-daemon (PID: 6660, Parent: 1, MD5: 3089d47e3f3ab84cd81c48fd406d7a8c) Arguments: /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

systemd New Fork (PID: 6661, Parent: 1)

dbus-daemon (PID: 6661, Parent: 1, MD5: 3089d47e3f3ab84cd81c48fd406d7a8c) Arguments: /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

systemd New Fork (PID: 6662, Parent: 1)

dbus-daemon (PID: 6662, Parent: 1, MD5: 3089d47e3f3ab84cd81c48fd406d7a8c) Arguments: /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

systemd New Fork (PID: 6663, Parent: 1)

dbus-daemon (PID: 6663, Parent: 1, MD5: 3089d47e3f3ab84cd81c48fd406d7a8c) Arguments: /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

cleanup

Malware Threat Intel

Provided by

Name	Description	Attribution	Blogpost URLs	Link
Mirai	Mirai is one of the first significant botnets targeting exposed networking devices running Linux. Found in August 2016 by MalwareMustDie, its name means "future" in Japanese. Nowadays it targets a wide range of networked embedded devices such as IP cameras, home routers (many vendors involved), and other IoT devices. Since the source code was published on "Hack Forums" many variants of the Mirai family appeared, infecting mostly home networks all around the world.	No Attribution	http://osint.bambenekconsulting.com/feeds/ http://www.simonroses.com/2016/10/mirai-ddos-botnet-source-code-binary-analysis/ https://blog.malwaremustdie.org/2020/02/mmd-0065-2021-linuxmirai-fbot-re.html https://blog.netlab.360.com/another-lilin-dvr-0-day-being-used-to-spread-mirai-en/ https://blog.netlab.360.com/mirai_ptea-botnet-is-exploiting-undisclosed-kguard-dvr-vulnerability-en/	https://malpedia.caad.fkie.fraunhofer.de/details/elf.mirai

Yara Signatures

Memory Dumps

Source	Rule	Description	Author	Strings
6237.1.0000000008048000.000000000805a000.r-x.sdmp	JoeSecurity_Okiru	Yara detected Okiru	Joe Security
6239.1.0000000008048000.000000000805a000.r-x.sdmp	JoeSecurity_Okiru	Yara detected Okiru	Joe Security
6242.1.0000000008048000.000000000805a000.r-x.sdmp	JoeSecurity_Okiru	Yara detected Okiru	Joe Security
6242.1.0000000008048000.000000000805a000.r-x.sdmp	JoeSecurity_Mirai_9	Yara detected Mirai	Joe Security
6239.1.0000000008048000.000000000805a000.r-x.sdmp	JoeSecurity_Mirai_9	Yara detected Mirai	Joe Security
6242.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_fa3ad9d0	unknown	unknown	0x11aa:$a: CB 08 C1 CB 10 66 C1 CB 08 31 C9 8A 4F 14 D3 E8 01 D8 66 C1
6242.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_b14f4c5d	unknown	unknown	0x7180:$a: 53 31 DB 8B 4C 24 0C 8B 54 24 08 83 F9 01 76 15 66 8B 02 83 E9 02 25 FF FF 00 00 83 C2 02 01 C3 83 F9 01 77 EB 49 75 05 0F BE 02 01 C3
6242.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_93fc3657	unknown	unknown	0x1235:$a: 00 00 00 89 44 24 60 89 D1 31 C0 8B 7C 24 28 FC F3 AB 89 D1 8B 7C
6242.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_804f8e7c	unknown	unknown	0x10db:$a: 31 ED 81 E1 FF 00 00 00 89 4C 24 58 89 EA C6 46 04 00 C1 FA 1F
6242.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_99d78950	unknown	unknown	0x1d01:$a: 10 89 C3 80 BC 04 83 00 00 00 20 0F 94 C0 8D B4 24 83 00 00 00 25 FF 00 0x1de1:$a: 10 89 C3 80 BC 04 83 00 00 00 20 0F 94 C0 8D B4 24 83 00 00 00 25 FF 00 0x1eb6:$a: 10 89 C3 80 BC 04 83 00 00 00 20 0F 94 C0 8D B4 24 83 00 00 00 25 FF 00 0x2161:$a: 10 89 C3 80 BC 04 83 00 00 00 20 0F 94 C0 8D B4 24 83 00 00 00 25 FF 00 0x25e3:$a: 10 89 C3 80 BC 04 83 00 00 00 20 0F 94 C0 8D B4 24 83 00 00 00 25 FF 00
6242.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_a68e498c	unknown	unknown	0xff3:$a: 10 39 D0 7E 25 8B 4C 24 38 01 D1 8A 11 8D 42 9F 3C 19 77 05 8D
6242.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_88de437f	unknown	unknown	0x96d2:$a: 24 08 8B 4C 24 04 85 D2 74 0D 31 C0 89 F6 C6 04 08 00 40 39 D0
6242.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_ae9d0fa6	unknown	unknown	0x2ff2:$a: 83 EC 04 8A 44 24 18 8B 5C 24 14 88 44 24 03 8A 44 24 10 25 FF 00
6242.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_389ee3e9	unknown	unknown	0xcc9b:$a: 89 45 00 EB 2C 8B 4B 04 8B 13 8B 7B 18 8B 01 01 02 8B 02 83
6242.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_cc93863b	unknown	unknown	0xb5a0:$a: C3 57 8B 44 24 0C 8B 4C 24 10 8B 7C 24 08 F3 AA 8B 44 24 08
6242.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_8aa7b5d3	unknown	unknown	0x96a2:$a: 8B 4C 24 14 8B 74 24 0C 8B 5C 24 10 85 C9 74 0D 31 D2 8A 04 1A 88
6242.1.0000000008048000.000000000805a000.r-x.sdmp	Mirai_Botnet_Malware	Detects Mirai Botnet Malware	Florian Roth	0xea60:$x1: POST /cdn-cgi/ 0xfd88:$s1: LCOGQGPTGP
6237.1.0000000008048000.000000000805a000.r-x.sdmp	JoeSecurity_Mirai_9	Yara detected Mirai	Joe Security
6239.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_fa3ad9d0	unknown	unknown	0x11aa:$a: CB 08 C1 CB 10 66 C1 CB 08 31 C9 8A 4F 14 D3 E8 01 D8 66 C1
6239.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_b14f4c5d	unknown	unknown	0x7180:$a: 53 31 DB 8B 4C 24 0C 8B 54 24 08 83 F9 01 76 15 66 8B 02 83 E9 02 25 FF FF 00 00 83 C2 02 01 C3 83 F9 01 77 EB 49 75 05 0F BE 02 01 C3
6239.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_93fc3657	unknown	unknown	0x1235:$a: 00 00 00 89 44 24 60 89 D1 31 C0 8B 7C 24 28 FC F3 AB 89 D1 8B 7C
6239.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_804f8e7c	unknown	unknown	0x10db:$a: 31 ED 81 E1 FF 00 00 00 89 4C 24 58 89 EA C6 46 04 00 C1 FA 1F
6239.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_99d78950	unknown	unknown	0x1d01:$a: 10 89 C3 80 BC 04 83 00 00 00 20 0F 94 C0 8D B4 24 83 00 00 00 25 FF 00 0x1de1:$a: 10 89 C3 80 BC 04 83 00 00 00 20 0F 94 C0 8D B4 24 83 00 00 00 25 FF 00 0x1eb6:$a: 10 89 C3 80 BC 04 83 00 00 00 20 0F 94 C0 8D B4 24 83 00 00 00 25 FF 00 0x2161:$a: 10 89 C3 80 BC 04 83 00 00 00 20 0F 94 C0 8D B4 24 83 00 00 00 25 FF 00 0x25e3:$a: 10 89 C3 80 BC 04 83 00 00 00 20 0F 94 C0 8D B4 24 83 00 00 00 25 FF 00
6239.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_a68e498c	unknown	unknown	0xff3:$a: 10 39 D0 7E 25 8B 4C 24 38 01 D1 8A 11 8D 42 9F 3C 19 77 05 8D
6239.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_88de437f	unknown	unknown	0x96d2:$a: 24 08 8B 4C 24 04 85 D2 74 0D 31 C0 89 F6 C6 04 08 00 40 39 D0
6239.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_ae9d0fa6	unknown	unknown	0x2ff2:$a: 83 EC 04 8A 44 24 18 8B 5C 24 14 88 44 24 03 8A 44 24 10 25 FF 00
6239.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_389ee3e9	unknown	unknown	0xcc9b:$a: 89 45 00 EB 2C 8B 4B 04 8B 13 8B 7B 18 8B 01 01 02 8B 02 83
6239.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_cc93863b	unknown	unknown	0xb5a0:$a: C3 57 8B 44 24 0C 8B 4C 24 10 8B 7C 24 08 F3 AA 8B 44 24 08
6239.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_8aa7b5d3	unknown	unknown	0x96a2:$a: 8B 4C 24 14 8B 74 24 0C 8B 5C 24 10 85 C9 74 0D 31 D2 8A 04 1A 88
6237.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_fa3ad9d0	unknown	unknown	0x11aa:$a: CB 08 C1 CB 10 66 C1 CB 08 31 C9 8A 4F 14 D3 E8 01 D8 66 C1
6237.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_b14f4c5d	unknown	unknown	0x7180:$a: 53 31 DB 8B 4C 24 0C 8B 54 24 08 83 F9 01 76 15 66 8B 02 83 E9 02 25 FF FF 00 00 83 C2 02 01 C3 83 F9 01 77 EB 49 75 05 0F BE 02 01 C3
6237.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_93fc3657	unknown	unknown	0x1235:$a: 00 00 00 89 44 24 60 89 D1 31 C0 8B 7C 24 28 FC F3 AB 89 D1 8B 7C
6237.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_804f8e7c	unknown	unknown	0x10db:$a: 31 ED 81 E1 FF 00 00 00 89 4C 24 58 89 EA C6 46 04 00 C1 FA 1F
6237.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_99d78950	unknown	unknown	0x1d01:$a: 10 89 C3 80 BC 04 83 00 00 00 20 0F 94 C0 8D B4 24 83 00 00 00 25 FF 00 0x1de1:$a: 10 89 C3 80 BC 04 83 00 00 00 20 0F 94 C0 8D B4 24 83 00 00 00 25 FF 00 0x1eb6:$a: 10 89 C3 80 BC 04 83 00 00 00 20 0F 94 C0 8D B4 24 83 00 00 00 25 FF 00 0x2161:$a: 10 89 C3 80 BC 04 83 00 00 00 20 0F 94 C0 8D B4 24 83 00 00 00 25 FF 00 0x25e3:$a: 10 89 C3 80 BC 04 83 00 00 00 20 0F 94 C0 8D B4 24 83 00 00 00 25 FF 00
6237.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_a68e498c	unknown	unknown	0xff3:$a: 10 39 D0 7E 25 8B 4C 24 38 01 D1 8A 11 8D 42 9F 3C 19 77 05 8D
6237.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_88de437f	unknown	unknown	0x96d2:$a: 24 08 8B 4C 24 04 85 D2 74 0D 31 C0 89 F6 C6 04 08 00 40 39 D0
6237.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_ae9d0fa6	unknown	unknown	0x2ff2:$a: 83 EC 04 8A 44 24 18 8B 5C 24 14 88 44 24 03 8A 44 24 10 25 FF 00
6237.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_389ee3e9	unknown	unknown	0xcc9b:$a: 89 45 00 EB 2C 8B 4B 04 8B 13 8B 7B 18 8B 01 01 02 8B 02 83
6237.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_cc93863b	unknown	unknown	0xb5a0:$a: C3 57 8B 44 24 0C 8B 4C 24 10 8B 7C 24 08 F3 AA 8B 44 24 08
6237.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_8aa7b5d3	unknown	unknown	0x96a2:$a: 8B 4C 24 14 8B 74 24 0C 8B 5C 24 10 85 C9 74 0D 31 D2 8A 04 1A 88
6239.1.0000000008048000.000000000805a000.r-x.sdmp	Mirai_Botnet_Malware	Detects Mirai Botnet Malware	Florian Roth	0xea60:$x1: POST /cdn-cgi/ 0xfd88:$s1: LCOGQGPTGP
6237.1.0000000008048000.000000000805a000.r-x.sdmp	Mirai_Botnet_Malware	Detects Mirai Botnet Malware	Florian Roth	0xea60:$x1: POST /cdn-cgi/ 0xfd88:$s1: LCOGQGPTGP
Process Memory Space: byte.x86.elf PID: 6237	JoeSecurity_Okiru	Yara detected Okiru	Joe Security
Process Memory Space: byte.x86.elf PID: 6237	JoeSecurity_Mirai_9	Yara detected Mirai	Joe Security
Process Memory Space: byte.x86.elf PID: 6239	JoeSecurity_Okiru	Yara detected Okiru	Joe Security
Process Memory Space: byte.x86.elf PID: 6239	JoeSecurity_Mirai_9	Yara detected Mirai	Joe Security
Process Memory Space: byte.x86.elf PID: 6242	JoeSecurity_Okiru	Yara detected Okiru	Joe Security
Process Memory Space: byte.x86.elf PID: 6242	JoeSecurity_Mirai_9	Yara detected Mirai	Joe Security
Click to see the 43 entries

Suricata Signatures

⊘No Suricata rule has matched

Joe Sandbox Signatures

Click to jump to signature section

Show All Signature Results

AV Detection

Multi AV Scanner detection for submitted file

Source: byte.x86.elf	Virustotal: Detection: 39%			Perma Link
Source: byte.x86.elf	ReversingLabs: Detection: 39%

Machine Learning detection for sample

Source: byte.x86.elf

Joe Sandbox ML: detected

Source: /usr/bin/pkill (PID: 6407)	Reads CPU info from /sys: /sys/devices/system/cpu/online	Jump to behavior
Source: /usr/bin/pkill (PID: 6450)	Reads CPU info from /sys: /sys/devices/system/cpu/online	Jump to behavior
Source: /usr/bin/pkill (PID: 6505)	Reads CPU info from /sys: /sys/devices/system/cpu/online	Jump to behavior

Source: global traffic

TCP traffic: 192.168.2.23:43546 -> 154.216.19.138:777

Source: /usr/sbin/rsyslogd (PID: 6280)	Reads hosts file: /etc/hosts	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6292)	Reads hosts file: /etc/hosts	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6379)	Reads hosts file: /etc/hosts	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6409)	Reads hosts file: /etc/hosts	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6427)	Reads hosts file: /etc/hosts	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6452)	Reads hosts file: /etc/hosts	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6472)	Reads hosts file: /etc/hosts	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6506)	Reads hosts file: /etc/hosts	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6516)	Reads hosts file: /etc/hosts	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6526)	Reads hosts file: /etc/hosts	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6536)	Reads hosts file: /etc/hosts	Jump to behavior

Source: global traffic	TCP traffic: 192.168.2.23:43928 -> 91.189.91.42:443
Source: global traffic	TCP traffic: 192.168.2.23:42836 -> 91.189.91.43:443
Source: global traffic	TCP traffic: 192.168.2.23:42516 -> 109.202.202.202:80

Source: unknown	TCP traffic detected without corresponding DNS query: 91.189.91.42
Source: unknown	TCP traffic detected without corresponding DNS query: 91.189.91.43
Source: unknown	TCP traffic detected without corresponding DNS query: 109.202.202.202
Source: unknown	TCP traffic detected without corresponding DNS query: 91.189.91.42
Source: unknown	TCP traffic detected without corresponding DNS query: 91.189.91.43
Source: unknown	TCP traffic detected without corresponding DNS query: 109.202.202.202
Source: unknown	TCP traffic detected without corresponding DNS query: 91.189.91.42
Source: unknown	TCP traffic detected without corresponding DNS query: 91.189.91.43
Source: unknown	UDP traffic detected without corresponding DNS query: 1.1.1.1
Source: unknown	UDP traffic detected without corresponding DNS query: 1.1.1.1
Source: unknown	UDP traffic detected without corresponding DNS query: 1.1.1.1
Source: unknown	UDP traffic detected without corresponding DNS query: 1.1.1.1
Source: unknown	UDP traffic detected without corresponding DNS query: 1.1.1.1

Source: global traffic	DNS traffic detected: DNS query: vbtgsze.r-e.kr
Source: global traffic	DNS traffic detected: DNS query: daisy.ubuntu.com

Source: byte.x86.elf	String found in binary or memory: http://upx.sf.net
Source: syslog.201.dr, syslog.143.dr, syslog.93.dr, syslog.221.dr, syslog.157.dr, syslog.103.dr, syslog.205.dr, syslog.23.dr, syslog.33.dr, syslog.53.dr	String found in binary or memory: https://www.rsyslog.com

Source: unknown	Network traffic detected: HTTP traffic on port 43928 -> 443
Source: unknown	Network traffic detected: HTTP traffic on port 42836 -> 443

System Summary

Malicious sample detected (through community Yara rule)

Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_fa3ad9d0 Author: unknown
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_b14f4c5d Author: unknown
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_93fc3657 Author: unknown
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_804f8e7c Author: unknown
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_99d78950 Author: unknown
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_a68e498c Author: unknown
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_88de437f Author: unknown
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_ae9d0fa6 Author: unknown
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_389ee3e9 Author: unknown
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_cc93863b Author: unknown
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_8aa7b5d3 Author: unknown
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Detects Mirai Botnet Malware Author: Florian Roth
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_fa3ad9d0 Author: unknown
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_b14f4c5d Author: unknown
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_93fc3657 Author: unknown
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_804f8e7c Author: unknown
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_99d78950 Author: unknown
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_a68e498c Author: unknown
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_88de437f Author: unknown
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_ae9d0fa6 Author: unknown
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_389ee3e9 Author: unknown
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_cc93863b Author: unknown
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_8aa7b5d3 Author: unknown
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_fa3ad9d0 Author: unknown
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_b14f4c5d Author: unknown
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_93fc3657 Author: unknown
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_804f8e7c Author: unknown
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_99d78950 Author: unknown
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_a68e498c Author: unknown
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_88de437f Author: unknown
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_ae9d0fa6 Author: unknown
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_389ee3e9 Author: unknown
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_cc93863b Author: unknown
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_8aa7b5d3 Author: unknown
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Detects Mirai Botnet Malware Author: Florian Roth
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Detects Mirai Botnet Malware Author: Florian Roth

Sample tries to kill a massive number of system processes

Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 1 (init), result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 2, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 3, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 4, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 6, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 9, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 10, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 11, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 12, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 13, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 14, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 15, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 16, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 17, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 18, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 20, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 21, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 22, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 23, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 24, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 25, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 26, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 27, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 28, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 29, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 30, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 35, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 77, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 78, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 79, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 80, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 81, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 82, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 83, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 84, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 85, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 88, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 89, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 91, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 92, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 93, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 94, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 95, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 96, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 97, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 98, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 99, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 100, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 101, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 102, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 103, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 104, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 105, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 106, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 107, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 108, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 109, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 110, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 111, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 112, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 113, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 114, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 115, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 116, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 117, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 118, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 119, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 120, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 121, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 122, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 123, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 124, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 125, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 126, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 127, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 128, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 130, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 132, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 141, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 144, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 157, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 201, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 202, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 203, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 204, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 205, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 206, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 207, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 208, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 209, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 210, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 211, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 212, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 213, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 214, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 215, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 216, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 217, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 218, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 219, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 220, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 221, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 222, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 223, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 224, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 225, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 226, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 227, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 228, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 229, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 230, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 231, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 232, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 233, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 234, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 235, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 236, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 237, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 243, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 248, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 249, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 250, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 251, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 252, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 253, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 254, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 255, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 256, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 257, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 258, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 259, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 260, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 261, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 262, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 263, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 264, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 265, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 266, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 267, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 269, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 270, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 272, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 274, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 278, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 281, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 286, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 322, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 324, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 326, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 327, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 328, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 333, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 346, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 379, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 419, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 420, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 658, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 667, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 670, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 674, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 675, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 676, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 677, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 720, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 721, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 772, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 777, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 785, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 793, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 936, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 896, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent to PID below 1000: pid: 910, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 1 (init), result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 2, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 3, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 4, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 6, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 9, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 10, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 11, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 12, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 13, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 14, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 15, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 16, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 17, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 18, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 20, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 21, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 22, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 23, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 24, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 25, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 26, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 27, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 28, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 29, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 30, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 35, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 77, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 78, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 79, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 80, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 81, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 82, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 83, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 84, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 85, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 88, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 89, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 91, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 92, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 93, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 94, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 95, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 96, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 97, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 98, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 99, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 100, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 101, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 102, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 103, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 104, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 105, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 106, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 107, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 108, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 109, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 110, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 111, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 112, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 113, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 114, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 115, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 116, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 117, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 118, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 119, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 120, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 121, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 122, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 123, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 124, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 125, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 126, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 127, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 128, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 130, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 132, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 141, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 144, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 157, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 201, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 202, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 203, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 204, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 205, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 206, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 207, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 208, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 209, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 210, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 211, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 212, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 213, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 214, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 215, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 216, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 217, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 218, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 219, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 220, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 221, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 222, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 223, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 224, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 225, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 226, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 227, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 228, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 229, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 230, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 231, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 232, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 233, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 234, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 235, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 236, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 237, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 243, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 248, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 249, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 250, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 251, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 252, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 253, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 254, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 255, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 256, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 257, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 258, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 259, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 260, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 261, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 262, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 263, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 264, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 265, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 266, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 267, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 269, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 270, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 272, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 274, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 278, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 281, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 286, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 322, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 324, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 326, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 327, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 328, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 333, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 346, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 379, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 419, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 420, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 658, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 667, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 670, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 674, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 675, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 676, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 677, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 720, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 721, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 772, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 777, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 785, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 793, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 936, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 896, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent to PID below 1000: pid: 910, result: successful	Jump to behavior

Sample tries to kill multiple processes (SIGKILL)

Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 1 (init), result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 2, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 3, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 4, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 9, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 10, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 11, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 12, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 13, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 14, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 15, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 16, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 17, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 18, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 20, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 21, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 22, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 23, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 24, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 25, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 26, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 27, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 28, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 29, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 30, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 35, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 77, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 78, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 79, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 80, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 81, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 82, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 83, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 84, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 85, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 88, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 89, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 91, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 92, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 93, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 94, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 95, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 96, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 97, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 98, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 99, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 100, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 101, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 102, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 103, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 104, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 105, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 106, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 107, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 108, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 109, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 110, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 111, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 112, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 113, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 114, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 115, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 116, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 117, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 118, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 119, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 120, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 121, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 122, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 123, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 124, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 125, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 126, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 127, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 128, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 130, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 132, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 141, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 144, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 157, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 201, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 202, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 203, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 204, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 205, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 206, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 207, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 208, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 209, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 210, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 211, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 212, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 213, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 214, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 215, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 216, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 217, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 218, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 219, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 220, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 221, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 222, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 223, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 224, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 225, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 226, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 227, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 228, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 229, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 230, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 231, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 232, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 233, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 234, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 235, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 236, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 237, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 243, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 248, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 249, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 250, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 251, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 252, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 253, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 254, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 255, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 256, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 257, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 258, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 259, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 260, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 261, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 262, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 263, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 264, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 265, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 266, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 267, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 269, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 270, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 272, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 274, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 278, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 281, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 286, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 322, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 324, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 326, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 327, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 328, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 333, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 346, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 379, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 419, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 420, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 658, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 667, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 670, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 674, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 675, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 676, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 677, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 720, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 721, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 772, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 777, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 785, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 793, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 936, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 1207, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 1320, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 1344, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 1601, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 1886, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 1983, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 2048, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 2746, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 2749, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 2761, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 2882, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 3021, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 3088, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 4444, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 4445, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 4446, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 4447, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 4496, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 4498, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 4501, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6222, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6277, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6279, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6280, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6281, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 896, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 910, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6071, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6375, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6376, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6377, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6378, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6379, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6380, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6405, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6406, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6408, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6409, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6410, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6448, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6449, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6451, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6452, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6453, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6454, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6462, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6471, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6472, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6473, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6474, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6506, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6507, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6515, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6516, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6517, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6518, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6519, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6526, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6527, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6528, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6529, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 1 (init), result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 2, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 3, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 4, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 9, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 10, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 11, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 12, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 13, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 14, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 15, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 16, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 17, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 18, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 20, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 21, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 22, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 23, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 24, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 25, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 26, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 27, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 28, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 29, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 30, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 35, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 77, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 78, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 79, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 80, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 81, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 82, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 83, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 84, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 85, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 88, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 89, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 91, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 92, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 93, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 94, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 95, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 96, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 97, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 98, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 99, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 100, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 101, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 102, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 103, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 104, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 105, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 106, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 107, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 108, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 109, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 110, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 111, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 112, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 113, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 114, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 115, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 116, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 117, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 118, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 119, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 120, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 121, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 122, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 123, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 124, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 125, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 126, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 127, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 128, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 130, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 132, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 141, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 144, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 157, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 201, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 202, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 203, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 204, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 205, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 206, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 207, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 208, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 209, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 210, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 211, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 212, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 213, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 214, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 215, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 216, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 217, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 218, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 219, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 220, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 221, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 222, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 223, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 224, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 225, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 226, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 227, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 228, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 229, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 230, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 231, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 232, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 233, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 234, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 235, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 236, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 237, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 243, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 248, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 249, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 250, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 251, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 252, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 253, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 254, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 255, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 256, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 257, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 258, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 259, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 260, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 261, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 262, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 263, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 264, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 265, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 266, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 267, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 269, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 270, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 272, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 274, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 278, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 281, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 286, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 322, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 324, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 326, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 327, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 328, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 333, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 346, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 379, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 419, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 420, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 658, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 667, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 670, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 674, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 675, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 676, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 677, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 720, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 721, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 772, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 777, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 785, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 793, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 936, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 1207, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 1320, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 1344, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 1601, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 1886, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 1983, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 2048, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 2746, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 2749, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 2761, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 2882, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 3021, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 3088, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 4444, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 4445, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 4446, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 4447, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 4496, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 4498, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 4501, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6222, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6277, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6279, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6280, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6281, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 896, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 910, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6071, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6291, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6292, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6293, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6294, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6377, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6378, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6379, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6380, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6423, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6426, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6427, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6428, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6429, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6470, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6471, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6472, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6473, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6474, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6502, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6503, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6504, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6506, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6507, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6524, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6525, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6533, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6534, result: successful	Jump to behavior

Source: LOAD without section mappings

Program segment: 0x8048000

Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 1 (init), result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 2, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 3, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 4, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 9, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 10, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 11, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 12, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 13, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 14, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 15, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 16, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 17, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 18, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 20, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 21, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 22, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 23, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 24, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 25, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 26, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 27, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 28, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 29, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 30, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 35, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 77, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 78, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 79, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 80, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 81, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 82, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 83, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 84, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 85, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 88, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 89, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 91, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 92, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 93, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 94, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 95, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 96, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 97, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 98, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 99, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 100, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 101, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 102, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 103, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 104, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 105, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 106, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 107, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 108, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 109, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 110, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 111, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 112, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 113, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 114, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 115, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 116, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 117, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 118, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 119, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 120, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 121, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 122, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 123, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 124, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 125, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 126, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 127, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 128, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 130, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 132, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 141, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 144, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 157, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 201, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 202, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 203, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 204, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 205, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 206, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 207, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 208, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 209, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 210, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 211, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 212, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 213, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 214, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 215, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 216, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 217, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 218, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 219, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 220, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 221, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 222, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 223, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 224, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 225, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 226, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 227, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 228, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 229, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 230, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 231, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 232, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 233, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 234, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 235, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 236, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 237, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 243, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 248, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 249, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 250, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 251, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 252, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 253, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 254, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 255, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 256, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 257, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 258, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 259, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 260, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 261, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 262, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 263, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 264, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 265, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 266, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 267, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 269, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 270, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 272, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 274, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 278, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 281, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 286, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 322, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 324, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 326, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 327, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 328, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 333, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 346, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 379, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 419, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 420, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 658, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 667, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 670, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 674, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 675, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 676, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 677, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 720, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 721, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 772, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 777, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 785, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 793, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 936, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 1207, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 1320, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 1344, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 1601, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 1886, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 1983, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 2048, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 2746, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 2749, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 2761, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 2882, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 3021, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 3088, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 4444, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 4445, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 4446, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 4447, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 4496, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 4498, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 4501, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6222, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6277, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6279, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6280, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6281, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 896, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 910, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6071, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6375, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6376, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6377, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6378, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6379, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6380, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6405, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6406, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6408, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6409, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6410, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6448, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6449, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6451, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6452, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6453, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6454, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6462, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6471, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6472, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6473, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6474, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6506, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6507, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6515, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6516, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6517, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6518, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6519, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6526, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6527, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6528, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6238)	SIGKILL sent: pid: 6529, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 1 (init), result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 2, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 3, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 4, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 9, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 10, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 11, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 12, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 13, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 14, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 15, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 16, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 17, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 18, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 20, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 21, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 22, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 23, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 24, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 25, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 26, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 27, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 28, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 29, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 30, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 35, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 77, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 78, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 79, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 80, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 81, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 82, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 83, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 84, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 85, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 88, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 89, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 91, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 92, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 93, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 94, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 95, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 96, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 97, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 98, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 99, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 100, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 101, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 102, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 103, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 104, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 105, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 106, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 107, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 108, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 109, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 110, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 111, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 112, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 113, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 114, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 115, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 116, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 117, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 118, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 119, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 120, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 121, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 122, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 123, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 124, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 125, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 126, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 127, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 128, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 130, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 132, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 141, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 144, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 157, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 201, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 202, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 203, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 204, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 205, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 206, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 207, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 208, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 209, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 210, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 211, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 212, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 213, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 214, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 215, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 216, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 217, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 218, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 219, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 220, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 221, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 222, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 223, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 224, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 225, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 226, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 227, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 228, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 229, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 230, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 231, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 232, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 233, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 234, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 235, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 236, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 237, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 243, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 248, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 249, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 250, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 251, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 252, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 253, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 254, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 255, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 256, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 257, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 258, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 259, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 260, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 261, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 262, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 263, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 264, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 265, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 266, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 267, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 269, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 270, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 272, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 274, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 278, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 281, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 286, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 322, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 324, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 326, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 327, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 328, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 333, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 346, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 379, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 419, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 420, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 658, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 667, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 670, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 674, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 675, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 676, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 677, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 720, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 721, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 772, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 777, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 785, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 793, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 936, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 1207, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 1320, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 1344, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 1601, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 1886, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 1983, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 2048, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 2746, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 2749, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 2761, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 2882, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 3021, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 3088, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 4444, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 4445, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 4446, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 4447, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 4496, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 4498, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 4501, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6222, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6277, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6279, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6280, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6281, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 896, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 910, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6071, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6291, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6292, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6293, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6294, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6377, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6378, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6379, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6380, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6423, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6426, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6427, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6428, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6429, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6470, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6471, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6472, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6473, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6474, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6502, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6503, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6504, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6506, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6507, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6524, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6525, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6533, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	SIGKILL sent: pid: 6534, result: successful	Jump to behavior

Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_fa3ad9d0 reference_sample = 8dc745a6de6f319cd6021c3e147597315cc1be02099d78fc8aae94de0e1e4bc6, os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = fe93a3552b72b107f95cc5a7e59da64fe84d31df833bf36c81d8f31d8d79d7ca, id = fa3ad9d0-7c55-4621-90fc-6b154c44a67b, last_modified = 2021-09-16
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_b14f4c5d os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = a70d052918dd2fbc66db241da6438015130f0fb6929229bfe573546fe98da817, id = b14f4c5d-054f-46e6-9fa8-3588f1ef68b7, last_modified = 2021-09-16
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_93fc3657 reference_sample = 8dc745a6de6f319cd6021c3e147597315cc1be02099d78fc8aae94de0e1e4bc6, os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = d01a9e85a01fad913ca048b60bda1e5a2762f534e5308132c1d3098ac3f561ee, id = 93fc3657-fd21-4e93-a728-c084fc0a6a4a, last_modified = 2021-09-16
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_804f8e7c reference_sample = 8dc745a6de6f319cd6021c3e147597315cc1be02099d78fc8aae94de0e1e4bc6, os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = 1080d8502848d532a0b38861437485d98a41d945acaf3cb676a7a2a2f6793ac6, id = 804f8e7c-4786-42bc-92e4-c68c24ca530e, last_modified = 2021-09-16
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_99d78950 reference_sample = 8dc745a6de6f319cd6021c3e147597315cc1be02099d78fc8aae94de0e1e4bc6, os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = 3008edc4e7a099b64139a77d15ec0e2c3c1b55fc23ab156304571c4d14bc654c, id = 99d78950-ea23-4166-a85a-7a029209f5b1, last_modified = 2021-09-16
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_a68e498c reference_sample = 8dc745a6de6f319cd6021c3e147597315cc1be02099d78fc8aae94de0e1e4bc6, os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = 951c9dfcba531e5112c872395f6c144c4bc8b71c666d2c7d9d8574a23c163883, id = a68e498c-0768-4321-ab65-42dd6ef85323, last_modified = 2021-09-16
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_88de437f reference_sample = 8dc745a6de6f319cd6021c3e147597315cc1be02099d78fc8aae94de0e1e4bc6, os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = c19eb595c2b444a809bef8500c20342c9f46694d3018e268833f9b884133a1ea, id = 88de437f-9c98-4e1d-96c0-7b433c99886a, last_modified = 2021-09-16
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_ae9d0fa6 os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = ca2bf2771844bec95563800d19a35dd230413f8eff0bd44c8ab0b4c596f81bfc, id = ae9d0fa6-be06-4656-9b13-8edfc0ee9e71, last_modified = 2021-09-16
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_389ee3e9 reference_sample = 5217f2a46cb93946e04ab00e385ad0fe0a2844b6ea04ef75ee9187aac3f3d52f, os = linux, severity = x86, creation_date = 2022-01-05, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = 59f2359dc1f41d385d639d157b4cd9fc73d76d8abb7cc09d47632bb4c9a39e6e, id = 389ee3e9-70c1-4c93-a999-292cf6ff1652, last_modified = 2022-01-26
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_cc93863b reference_sample = 5217f2a46cb93946e04ab00e385ad0fe0a2844b6ea04ef75ee9187aac3f3d52f, os = linux, severity = x86, creation_date = 2022-01-05, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = f3ecd30f0b511a8e92cfa642409d559e7612c3f57a1659ca46c77aca809a00ac, id = cc93863b-1050-40ba-9d02-5ec9ce6a3a28, last_modified = 2022-01-26
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_8aa7b5d3 reference_sample = 5217f2a46cb93946e04ab00e385ad0fe0a2844b6ea04ef75ee9187aac3f3d52f, os = linux, severity = x86, creation_date = 2022-01-05, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = 02a2c18c362df4b1fceb33f3b605586514ba9a00c7afedf71c04fa54d8146444, id = 8aa7b5d3-e1eb-4b55-b36a-0d3a242c06e9, last_modified = 2022-01-26
Source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Mirai_Botnet_Malware date = 2016-10-04, hash5 = 420bf9215dfb04e5008c5e522eee9946599e2b323b17f17919cd802ebb012175, hash4 = 2efa09c124f277be2199bee58f49fc0ce6c64c0bef30079dfb3d94a6de492a69, hash3 = 20683ff7a5fec1237fc09224af40be029b9548c62c693844624089af568c89d4, hash2 = 05c78c3052b390435e53a87e3d31e9fb17f7c76bb4df2814313bca24735ce81c, hash1 = 05c78c3052b390435e53a87e3d31e9fb17f7c76bb4df2814313bca24735ce81c, author = Florian Roth, description = Detects Mirai Botnet Malware, hash10 = c61bf95146c68bfbbe01d7695337ed0e93ea759f59f651799f07eecdb339f83f, hash11 = d9573c3850e2ae35f371dff977fc3e5282a5e67db8e3274fd7818e8273fd5c89, hash12 = f1100c84abff05e0501e77781160d9815628e7fd2de9e53f5454dbcac7c84ca5, hash9 = bf0471b37dba7939524a30d7d5afc8fcfb8d4a7c9954343196737e72ea4e2dc4, hash8 = 89570ae59462e6472b6769545a999bde8457e47ae0d385caaa3499ab735b8147, hash7 = 70bb0ec35dd9afcfd52ec4e1d920e7045dc51dca0573cd4c753987c9d79405c0, hash6 = 62cdc8b7fffbaf5683a466f6503c03e68a15413a90f6afd5a13ba027631460c6, reference = Internal Research, license = https://creativecommons.org/licenses/by-nc/4.0/, hash13 = fb713ccf839362bf0fbe01aedd6796f4d74521b133011b408e42c1fd9ab8246b
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_fa3ad9d0 reference_sample = 8dc745a6de6f319cd6021c3e147597315cc1be02099d78fc8aae94de0e1e4bc6, os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = fe93a3552b72b107f95cc5a7e59da64fe84d31df833bf36c81d8f31d8d79d7ca, id = fa3ad9d0-7c55-4621-90fc-6b154c44a67b, last_modified = 2021-09-16
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_b14f4c5d os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = a70d052918dd2fbc66db241da6438015130f0fb6929229bfe573546fe98da817, id = b14f4c5d-054f-46e6-9fa8-3588f1ef68b7, last_modified = 2021-09-16
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_93fc3657 reference_sample = 8dc745a6de6f319cd6021c3e147597315cc1be02099d78fc8aae94de0e1e4bc6, os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = d01a9e85a01fad913ca048b60bda1e5a2762f534e5308132c1d3098ac3f561ee, id = 93fc3657-fd21-4e93-a728-c084fc0a6a4a, last_modified = 2021-09-16
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_804f8e7c reference_sample = 8dc745a6de6f319cd6021c3e147597315cc1be02099d78fc8aae94de0e1e4bc6, os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = 1080d8502848d532a0b38861437485d98a41d945acaf3cb676a7a2a2f6793ac6, id = 804f8e7c-4786-42bc-92e4-c68c24ca530e, last_modified = 2021-09-16
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_99d78950 reference_sample = 8dc745a6de6f319cd6021c3e147597315cc1be02099d78fc8aae94de0e1e4bc6, os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = 3008edc4e7a099b64139a77d15ec0e2c3c1b55fc23ab156304571c4d14bc654c, id = 99d78950-ea23-4166-a85a-7a029209f5b1, last_modified = 2021-09-16
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_a68e498c reference_sample = 8dc745a6de6f319cd6021c3e147597315cc1be02099d78fc8aae94de0e1e4bc6, os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = 951c9dfcba531e5112c872395f6c144c4bc8b71c666d2c7d9d8574a23c163883, id = a68e498c-0768-4321-ab65-42dd6ef85323, last_modified = 2021-09-16
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_88de437f reference_sample = 8dc745a6de6f319cd6021c3e147597315cc1be02099d78fc8aae94de0e1e4bc6, os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = c19eb595c2b444a809bef8500c20342c9f46694d3018e268833f9b884133a1ea, id = 88de437f-9c98-4e1d-96c0-7b433c99886a, last_modified = 2021-09-16
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_ae9d0fa6 os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = ca2bf2771844bec95563800d19a35dd230413f8eff0bd44c8ab0b4c596f81bfc, id = ae9d0fa6-be06-4656-9b13-8edfc0ee9e71, last_modified = 2021-09-16
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_389ee3e9 reference_sample = 5217f2a46cb93946e04ab00e385ad0fe0a2844b6ea04ef75ee9187aac3f3d52f, os = linux, severity = x86, creation_date = 2022-01-05, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = 59f2359dc1f41d385d639d157b4cd9fc73d76d8abb7cc09d47632bb4c9a39e6e, id = 389ee3e9-70c1-4c93-a999-292cf6ff1652, last_modified = 2022-01-26
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_cc93863b reference_sample = 5217f2a46cb93946e04ab00e385ad0fe0a2844b6ea04ef75ee9187aac3f3d52f, os = linux, severity = x86, creation_date = 2022-01-05, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = f3ecd30f0b511a8e92cfa642409d559e7612c3f57a1659ca46c77aca809a00ac, id = cc93863b-1050-40ba-9d02-5ec9ce6a3a28, last_modified = 2022-01-26
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_8aa7b5d3 reference_sample = 5217f2a46cb93946e04ab00e385ad0fe0a2844b6ea04ef75ee9187aac3f3d52f, os = linux, severity = x86, creation_date = 2022-01-05, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = 02a2c18c362df4b1fceb33f3b605586514ba9a00c7afedf71c04fa54d8146444, id = 8aa7b5d3-e1eb-4b55-b36a-0d3a242c06e9, last_modified = 2022-01-26
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_fa3ad9d0 reference_sample = 8dc745a6de6f319cd6021c3e147597315cc1be02099d78fc8aae94de0e1e4bc6, os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = fe93a3552b72b107f95cc5a7e59da64fe84d31df833bf36c81d8f31d8d79d7ca, id = fa3ad9d0-7c55-4621-90fc-6b154c44a67b, last_modified = 2021-09-16
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_b14f4c5d os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = a70d052918dd2fbc66db241da6438015130f0fb6929229bfe573546fe98da817, id = b14f4c5d-054f-46e6-9fa8-3588f1ef68b7, last_modified = 2021-09-16
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_93fc3657 reference_sample = 8dc745a6de6f319cd6021c3e147597315cc1be02099d78fc8aae94de0e1e4bc6, os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = d01a9e85a01fad913ca048b60bda1e5a2762f534e5308132c1d3098ac3f561ee, id = 93fc3657-fd21-4e93-a728-c084fc0a6a4a, last_modified = 2021-09-16
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_804f8e7c reference_sample = 8dc745a6de6f319cd6021c3e147597315cc1be02099d78fc8aae94de0e1e4bc6, os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = 1080d8502848d532a0b38861437485d98a41d945acaf3cb676a7a2a2f6793ac6, id = 804f8e7c-4786-42bc-92e4-c68c24ca530e, last_modified = 2021-09-16
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_99d78950 reference_sample = 8dc745a6de6f319cd6021c3e147597315cc1be02099d78fc8aae94de0e1e4bc6, os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = 3008edc4e7a099b64139a77d15ec0e2c3c1b55fc23ab156304571c4d14bc654c, id = 99d78950-ea23-4166-a85a-7a029209f5b1, last_modified = 2021-09-16
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_a68e498c reference_sample = 8dc745a6de6f319cd6021c3e147597315cc1be02099d78fc8aae94de0e1e4bc6, os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = 951c9dfcba531e5112c872395f6c144c4bc8b71c666d2c7d9d8574a23c163883, id = a68e498c-0768-4321-ab65-42dd6ef85323, last_modified = 2021-09-16
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_88de437f reference_sample = 8dc745a6de6f319cd6021c3e147597315cc1be02099d78fc8aae94de0e1e4bc6, os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = c19eb595c2b444a809bef8500c20342c9f46694d3018e268833f9b884133a1ea, id = 88de437f-9c98-4e1d-96c0-7b433c99886a, last_modified = 2021-09-16
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_ae9d0fa6 os = linux, severity = x86, creation_date = 2021-01-12, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = ca2bf2771844bec95563800d19a35dd230413f8eff0bd44c8ab0b4c596f81bfc, id = ae9d0fa6-be06-4656-9b13-8edfc0ee9e71, last_modified = 2021-09-16
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_389ee3e9 reference_sample = 5217f2a46cb93946e04ab00e385ad0fe0a2844b6ea04ef75ee9187aac3f3d52f, os = linux, severity = x86, creation_date = 2022-01-05, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = 59f2359dc1f41d385d639d157b4cd9fc73d76d8abb7cc09d47632bb4c9a39e6e, id = 389ee3e9-70c1-4c93-a999-292cf6ff1652, last_modified = 2022-01-26
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_cc93863b reference_sample = 5217f2a46cb93946e04ab00e385ad0fe0a2844b6ea04ef75ee9187aac3f3d52f, os = linux, severity = x86, creation_date = 2022-01-05, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = f3ecd30f0b511a8e92cfa642409d559e7612c3f57a1659ca46c77aca809a00ac, id = cc93863b-1050-40ba-9d02-5ec9ce6a3a28, last_modified = 2022-01-26
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_8aa7b5d3 reference_sample = 5217f2a46cb93946e04ab00e385ad0fe0a2844b6ea04ef75ee9187aac3f3d52f, os = linux, severity = x86, creation_date = 2022-01-05, scan_context = file, memory, license = Elastic License v2, threat_name = Linux.Trojan.Mirai, fingerprint = 02a2c18c362df4b1fceb33f3b605586514ba9a00c7afedf71c04fa54d8146444, id = 8aa7b5d3-e1eb-4b55-b36a-0d3a242c06e9, last_modified = 2022-01-26
Source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Mirai_Botnet_Malware date = 2016-10-04, hash5 = 420bf9215dfb04e5008c5e522eee9946599e2b323b17f17919cd802ebb012175, hash4 = 2efa09c124f277be2199bee58f49fc0ce6c64c0bef30079dfb3d94a6de492a69, hash3 = 20683ff7a5fec1237fc09224af40be029b9548c62c693844624089af568c89d4, hash2 = 05c78c3052b390435e53a87e3d31e9fb17f7c76bb4df2814313bca24735ce81c, hash1 = 05c78c3052b390435e53a87e3d31e9fb17f7c76bb4df2814313bca24735ce81c, author = Florian Roth, description = Detects Mirai Botnet Malware, hash10 = c61bf95146c68bfbbe01d7695337ed0e93ea759f59f651799f07eecdb339f83f, hash11 = d9573c3850e2ae35f371dff977fc3e5282a5e67db8e3274fd7818e8273fd5c89, hash12 = f1100c84abff05e0501e77781160d9815628e7fd2de9e53f5454dbcac7c84ca5, hash9 = bf0471b37dba7939524a30d7d5afc8fcfb8d4a7c9954343196737e72ea4e2dc4, hash8 = 89570ae59462e6472b6769545a999bde8457e47ae0d385caaa3499ab735b8147, hash7 = 70bb0ec35dd9afcfd52ec4e1d920e7045dc51dca0573cd4c753987c9d79405c0, hash6 = 62cdc8b7fffbaf5683a466f6503c03e68a15413a90f6afd5a13ba027631460c6, reference = Internal Research, license = https://creativecommons.org/licenses/by-nc/4.0/, hash13 = fb713ccf839362bf0fbe01aedd6796f4d74521b133011b408e42c1fd9ab8246b
Source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Mirai_Botnet_Malware date = 2016-10-04, hash5 = 420bf9215dfb04e5008c5e522eee9946599e2b323b17f17919cd802ebb012175, hash4 = 2efa09c124f277be2199bee58f49fc0ce6c64c0bef30079dfb3d94a6de492a69, hash3 = 20683ff7a5fec1237fc09224af40be029b9548c62c693844624089af568c89d4, hash2 = 05c78c3052b390435e53a87e3d31e9fb17f7c76bb4df2814313bca24735ce81c, hash1 = 05c78c3052b390435e53a87e3d31e9fb17f7c76bb4df2814313bca24735ce81c, author = Florian Roth, description = Detects Mirai Botnet Malware, hash10 = c61bf95146c68bfbbe01d7695337ed0e93ea759f59f651799f07eecdb339f83f, hash11 = d9573c3850e2ae35f371dff977fc3e5282a5e67db8e3274fd7818e8273fd5c89, hash12 = f1100c84abff05e0501e77781160d9815628e7fd2de9e53f5454dbcac7c84ca5, hash9 = bf0471b37dba7939524a30d7d5afc8fcfb8d4a7c9954343196737e72ea4e2dc4, hash8 = 89570ae59462e6472b6769545a999bde8457e47ae0d385caaa3499ab735b8147, hash7 = 70bb0ec35dd9afcfd52ec4e1d920e7045dc51dca0573cd4c753987c9d79405c0, hash6 = 62cdc8b7fffbaf5683a466f6503c03e68a15413a90f6afd5a13ba027631460c6, reference = Internal Research, license = https://creativecommons.org/licenses/by-nc/4.0/, hash13 = fb713ccf839362bf0fbe01aedd6796f4d74521b133011b408e42c1fd9ab8246b

Source: classification engine

Classification label: mal96.spre.troj.evad.linELF@0/24@95/0

Data Obfuscation

Sample is packed with UPX

Source: initial sample	String containing UPX found: $Info: This file is packed with the UPX executable packer http://upx.sf.net $
Source: initial sample	String containing UPX found: $Info: This file is packed with the UPX executable packer http://upx.sf.net $
Source: initial sample	String containing UPX found: $Id: UPX 3.96 Copyright (C) 1996-2020 the UPX Team. All Rights Reserved. $

Persistence and Installation Behavior

Sample reads /proc/mounts (often used for finding a writable filesystem)

Source: /usr/bin/dbus-daemon (PID: 6279)	File: /proc/6279/mounts	Jump to behavior
Source: /bin/fusermount (PID: 6282)	File: /proc/6282/mounts	Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6291)	File: /proc/6291/mounts	Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6375)	File: /proc/6375/mounts	Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6405)	File: /proc/6405/mounts	Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6423)	File: /proc/6423/mounts	Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6454)	File: /proc/6454/mounts	Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6470)	File: /proc/6470/mounts	Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6502)	File: /proc/6502/mounts	Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6515)	File: /proc/6515/mounts	Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6528)	File: /proc/6528/mounts	Jump to behavior

Source: /lib/systemd/systemd-logind (PID: 6304)	Directory: <invalid fd (18)>/..	Jump to behavior
Source: /lib/systemd/systemd-logind (PID: 6304)	Directory: <invalid fd (17)>/..	Jump to behavior
Source: /lib/systemd/systemd-logind (PID: 6304)	File: /run/systemd/seats/.#seat0ObhoQQ	Jump to behavior
Source: /usr/lib/policykit-1/polkitd (PID: 6402)	Directory: /root/.cache	Jump to behavior
Source: /usr/lib/policykit-1/polkitd (PID: 6466)	Directory: /root/.cache	Jump to behavior
Source: /usr/lib/policykit-1/polkitd (PID: 6496)	Directory: /root/.cache	Jump to behavior
Source: /lib/systemd/systemd-logind (PID: 6580)	Directory: <invalid fd (18)>/..	Jump to behavior
Source: /lib/systemd/systemd-logind (PID: 6580)	Directory: <invalid fd (17)>/..	Jump to behavior
Source: /lib/systemd/systemd-logind (PID: 6580)	File: /run/systemd/seats/.#seat085RphJ	Jump to behavior

Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6472/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6471/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6474/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6473/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/1582/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/3088/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6470/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/230/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/110/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/231/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/111/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/232/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/1579/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/112/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/233/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/113/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/234/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/1335/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/114/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/235/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/1334/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/1576/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/2302/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/115/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/236/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/116/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/237/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/117/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/118/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/910/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/119/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/912/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/10/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/2307/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/11/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/918/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6241/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/12/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6240/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6361/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/13/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6243/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/14/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/15/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6245/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/16/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6244/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/17/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6247/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/18/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6246/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/1594/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/120/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/121/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/1349/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/1/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/122/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/243/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/123/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/2/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/124/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/3/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/4/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/125/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/126/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/1344/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/1465/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/1586/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/127/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/248/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/128/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/249/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/1463/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/800/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6238/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/9/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/801/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/20/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/21/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/22/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6252/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/23/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6251/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/24/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6254/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6375/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6496/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/25/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6253/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/26/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6256/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6377/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6498/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/27/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6255/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6376/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6497/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/28/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6258/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6379/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/29/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6257/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/6378/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6241)	File opened: /proc/491/cmdline	Jump to behavior

Source: /usr/bin/gpu-manager (PID: 6381)	Shell command executed: sh -c "grep -G \"^blacklist.nvidia[[:space:]]$\" /etc/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6383)	Shell command executed: sh -c "grep -G \"^blacklist.nvidia[[:space:]]$\" /lib/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6388)	Shell command executed: sh -c "grep -G \"^blacklist.radeon[[:space:]]$\" /etc/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6391)	Shell command executed: sh -c "grep -G \"^blacklist.radeon[[:space:]]$\" /lib/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6395)	Shell command executed: sh -c "grep -G \"^blacklist.amdgpu[[:space:]]$\" /etc/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6404)	Shell command executed: sh -c "grep -G \"^blacklist.amdgpu[[:space:]]$\" /lib/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6433)	Shell command executed: sh -c "grep -G \"^blacklist.nvidia[[:space:]]$\" /etc/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6436)	Shell command executed: sh -c "grep -G \"^blacklist.nvidia[[:space:]]$\" /lib/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6438)	Shell command executed: sh -c "grep -G \"^blacklist.radeon[[:space:]]$\" /etc/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6440)	Shell command executed: sh -c "grep -G \"^blacklist.radeon[[:space:]]$\" /lib/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6442)	Shell command executed: sh -c "grep -G \"^blacklist.amdgpu[[:space:]]$\" /etc/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6446)	Shell command executed: sh -c "grep -G \"^blacklist.amdgpu[[:space:]]$\" /lib/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6478)	Shell command executed: sh -c "grep -G \"^blacklist.nvidia[[:space:]]$\" /etc/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6481)	Shell command executed: sh -c "grep -G \"^blacklist.nvidia[[:space:]]$\" /lib/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6485)	Shell command executed: sh -c "grep -G \"^blacklist.radeon[[:space:]]$\" /etc/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6487)	Shell command executed: sh -c "grep -G \"^blacklist.radeon[[:space:]]$\" /lib/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6491)	Shell command executed: sh -c "grep -G \"^blacklist.amdgpu[[:space:]]$\" /etc/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6497)	Shell command executed: sh -c "grep -G \"^blacklist.amdgpu[[:space:]]$\" /lib/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6523)	Shell command executed: sh -c "grep -G \"^blacklist.nvidia[[:space:]]$\" /etc/modprobe.d/*.conf"	Jump to behavior

Source: /bin/sh (PID: 6382)	Grep executable: /usr/bin/grep -> grep -G ^blacklist.nvidia[[:space:]]$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf	Jump to behavior
Source: /bin/sh (PID: 6387)	Grep executable: /usr/bin/grep -> grep -G ^blacklist.nvidia[[:space:]]$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf	Jump to behavior
Source: /bin/sh (PID: 6389)	Grep executable: /usr/bin/grep -> grep -G ^blacklist.radeon[[:space:]]$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf	Jump to behavior
Source: /bin/sh (PID: 6392)	Grep executable: /usr/bin/grep -> grep -G ^blacklist.radeon[[:space:]]$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf	Jump to behavior
Source: /bin/sh (PID: 6396)	Grep executable: /usr/bin/grep -> grep -G ^blacklist.amdgpu[[:space:]]$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf	Jump to behavior
Source: /bin/sh (PID: 6434)	Grep executable: /usr/bin/grep -> grep -G ^blacklist.nvidia[[:space:]]$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf	Jump to behavior
Source: /bin/sh (PID: 6437)	Grep executable: /usr/bin/grep -> grep -G ^blacklist.nvidia[[:space:]]$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf	Jump to behavior
Source: /bin/sh (PID: 6439)	Grep executable: /usr/bin/grep -> grep -G ^blacklist.radeon[[:space:]]$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf	Jump to behavior
Source: /bin/sh (PID: 6441)	Grep executable: /usr/bin/grep -> grep -G ^blacklist.radeon[[:space:]]$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf	Jump to behavior
Source: /bin/sh (PID: 6443)	Grep executable: /usr/bin/grep -> grep -G ^blacklist.amdgpu[[:space:]]$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf	Jump to behavior
Source: /bin/sh (PID: 6447)	Grep executable: /usr/bin/grep -> grep -G ^blacklist.amdgpu[[:space:]]$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf	Jump to behavior
Source: /bin/sh (PID: 6479)	Grep executable: /usr/bin/grep -> grep -G ^blacklist.nvidia[[:space:]]$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf	Jump to behavior
Source: /bin/sh (PID: 6484)	Grep executable: /usr/bin/grep -> grep -G ^blacklist.nvidia[[:space:]]$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf	Jump to behavior
Source: /bin/sh (PID: 6486)	Grep executable: /usr/bin/grep -> grep -G ^blacklist.radeon[[:space:]]$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf	Jump to behavior
Source: /bin/sh (PID: 6488)	Grep executable: /usr/bin/grep -> grep -G ^blacklist.radeon[[:space:]]$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf	Jump to behavior
Source: /bin/sh (PID: 6492)	Grep executable: /usr/bin/grep -> grep -G ^blacklist.amdgpu[[:space:]]$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf	Jump to behavior
Source: /bin/sh (PID: 6498)	Grep executable: /usr/bin/grep -> grep -G ^blacklist.amdgpu[[:space:]]$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf	Jump to behavior

Source: /usr/share/gdm/generate-config (PID: 6407)	Pkill executable: /usr/bin/pkill -> pkill --signal HUP --uid gdm dconf-service	Jump to behavior
Source: /usr/share/gdm/generate-config (PID: 6450)	Pkill executable: /usr/bin/pkill -> pkill --signal HUP --uid gdm dconf-service	Jump to behavior
Source: /usr/share/gdm/generate-config (PID: 6505)	Pkill executable: /usr/bin/pkill -> pkill --signal HUP --uid gdm dconf-service	Jump to behavior
Source: /usr/share/gdm/generate-config (PID: 6537)	Pkill executable: /usr/bin/pkill -> pkill --signal HUP --uid gdm dconf-service	Jump to behavior

Source: /usr/sbin/rsyslogd (PID: 6280)	Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6292)	Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6292)	Log file created: /var/log/auth.log
Source: /usr/sbin/rsyslogd (PID: 6379)	Log file created: /var/log/auth.log	Jump to dropped file
Source: /usr/sbin/rsyslogd (PID: 6379)	Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6409)	Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6427)	Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6452)	Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6472)	Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6506)	Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6516)	Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6526)	Log file created: /var/log/kern.log	Jump to dropped file

Source: byte.x86.elf

Submission file: segment LOAD with 7.9598 entropy (max. 8.0)

Source: /usr/bin/gpu-manager (PID: 6377)	Truncated file: /var/log/gpu-manager.log	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6429)	Truncated file: /var/log/gpu-manager.log	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6474)	Truncated file: /var/log/gpu-manager.log	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6519)	Truncated file: /var/log/gpu-manager.log	Jump to behavior

Source: /usr/bin/pkill (PID: 6407)	Reads CPU info from /sys: /sys/devices/system/cpu/online	Jump to behavior
Source: /usr/bin/pkill (PID: 6450)	Reads CPU info from /sys: /sys/devices/system/cpu/online	Jump to behavior
Source: /usr/bin/pkill (PID: 6505)	Reads CPU info from /sys: /sys/devices/system/cpu/online	Jump to behavior

Source: /usr/sbin/rsyslogd (PID: 6280)	Queries kernel information via 'uname':	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6292)	Queries kernel information via 'uname':	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6379)	Queries kernel information via 'uname':	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6409)	Queries kernel information via 'uname':	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6427)	Queries kernel information via 'uname':	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6452)	Queries kernel information via 'uname':	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6472)	Queries kernel information via 'uname':	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6506)	Queries kernel information via 'uname':	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6516)	Queries kernel information via 'uname':	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6526)	Queries kernel information via 'uname':	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6536)	Queries kernel information via 'uname':	Jump to behavior

Stealing of Sensitive Information

Yara detected Mirai

Source: Yara match	File source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6237, type: MEMORYSTR
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6239, type: MEMORYSTR
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6242, type: MEMORYSTR

Yara detected Okiru

Source: Yara match	File source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6237, type: MEMORYSTR
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6239, type: MEMORYSTR
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6242, type: MEMORYSTR

Remote Access Functionality

Yara detected Mirai

Source: Yara match	File source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6237, type: MEMORYSTR
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6239, type: MEMORYSTR
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6242, type: MEMORYSTR

Yara detected Okiru

Source: Yara match	File source: 6237.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: 6239.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: 6242.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6237, type: MEMORYSTR
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6239, type: MEMORYSTR
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6242, type: MEMORYSTR

Mitre Att&ck Matrix

Reconnaissance	Resource Development	Initial Access	Execution	Persistence	Privilege Escalation	Defense Evasion	Credential Access	Discovery	Lateral Movement	Collection	Command and Control	Exfiltration	Impact
Gather Victim Identity Information	1 Scripting	Valid Accounts	Windows Management Instrumentation	1 Scripting	Path Interception	1 Disable or Modify Tools	1 OS Credential Dumping	1 Security Software Discovery	Remote Services	Data from Local System	1 Encrypted Channel	Exfiltration Over Other Network Medium	2 Service Stop
Credentials	Domains	Default Accounts	Scheduled Task/Job	Boot or Logon Initialization Scripts	Boot or Logon Initialization Scripts	1 Hidden Files and Directories	LSASS Memory	11 File and Directory Discovery	Remote Desktop Protocol	Data from Removable Media	1 Non-Standard Port	Exfiltration Over Bluetooth	Network Denial of Service
Email Addresses	DNS Server	Domain Accounts	At	Logon Script (Windows)	Logon Script (Windows)	11 Obfuscated Files or Information	Security Account Manager	1 System Information Discovery	SMB/Windows Admin Shares	Data from Network Shared Drive	1 Non-Application Layer Protocol	Automated Exfiltration	Data Encrypted for Impact
Employee Names	Virtual Private Server	Local Accounts	Cron	Login Hook	Login Hook	1 Indicator Removal	NTDS	System Network Configuration Discovery	Distributed Component Object Model	Input Capture	2 Application Layer Protocol	Traffic Duplication	Data Destruction

Malware Configuration

⊘No configs have been found

Behavior Graph

Hide Legend

Legend:

Process
Signature
Created File
DNS/IP Info
Is Dropped
Number of created Files
Is malicious
Internet

Antivirus, Machine Learning and Genetic Malware Detection

Initial Sample

Source	Detection	Scanner	Label	Link
byte.x86.elf	40%	Virustotal		Browse
byte.x86.elf	39%	ReversingLabs	Linux.Trojan.Mirai
byte.x86.elf	100%	Joe Sandbox ML

Dropped Files

⊘No Antivirus matches

Domains

⊘No Antivirus matches

URLs

⊘No Antivirus matches

Domains and IPs

Contacted Domains

Name	IP	Active	Malicious	Antivirus Detection	Reputation
daisy.ubuntu.com	162.213.35.25	true	false		high
vbtgsze.r-e.kr	154.216.19.138	true	false		unknown

URLs from Memory and Binaries

Name	Source	Malicious	Antivirus Detection	Reputation
https://www.rsyslog.com	syslog.201.dr, syslog.143.dr, syslog.93.dr, syslog.221.dr, syslog.157.dr, syslog.103.dr, syslog.205.dr, syslog.23.dr, syslog.33.dr, syslog.53.dr	false		high
http://upx.sf.net	byte.x86.elf	false		high

World Map of Contacted IPs

No. of IPs < 25%
25% < No. of IPs < 50%
50% < No. of IPs < 75%
75% < No. of IPs

Public IPs

IP	Domain	Country	ASN	ASN Name	Malicious
154.216.19.138	vbtgsze.r-e.kr	Seychelles	135357	SKHT-ASShenzhenKatherineHengTechnologyInformationCo	false
109.202.202.202	unknown	Switzerland	13030	INIT7CH	false
91.189.91.43	unknown	United Kingdom	41231	CANONICAL-ASGB	false
91.189.91.42	unknown	United Kingdom	41231	CANONICAL-ASGB	false

Joe Sandbox View / Context

IPs

Match	Associated Sample Name / URL	SHA 256	Detection	Threat Name	Link	Context
109.202.202.202	kpLwzBouH4.elf	Get hash	malicious	Unknown	Browse	ch.archive.ubuntu.com/ubuntu/pool/main/f/firefox/firefox_92.0%2bbuild3-0ubuntu0.20.04.1_amd64.deb
91.189.91.43	nn.elf	Get hash	malicious	Nanominer, Xmrig	Browse
	arm6.nn.elf	Get hash	malicious	Mirai, Okiru	Browse
	vlxx.m68k.elf	Get hash	malicious	Mirai, Gafgyt, Okiru	Browse
	vlxx.arm.elf	Get hash	malicious	Mirai, Gafgyt, Okiru	Browse
	la.bot.m68k.elf	Get hash	malicious	Mirai	Browse
	la.bot.arm7.elf	Get hash	malicious	Mirai	Browse
	la.bot.arm5.elf	Get hash	malicious	Mirai	Browse
	la.bot.arm.elf	Get hash	malicious	Mirai	Browse
	la.bot.arm6.elf	Get hash	malicious	Mirai	Browse
	la.bot.sparc.elf	Get hash	malicious	Mirai	Browse
91.189.91.42	nn.elf	Get hash	malicious	Nanominer, Xmrig	Browse
	arm6.nn.elf	Get hash	malicious	Mirai, Okiru	Browse
	vlxx.m68k.elf	Get hash	malicious	Mirai, Gafgyt, Okiru	Browse
	vlxx.arm5.elf	Get hash	malicious	Mirai, Gafgyt, Okiru	Browse
	vlxx.arm.elf	Get hash	malicious	Mirai, Gafgyt, Okiru	Browse
	la.bot.m68k.elf	Get hash	malicious	Mirai	Browse
	la.bot.arm7.elf	Get hash	malicious	Mirai	Browse
	la.bot.arm5.elf	Get hash	malicious	Mirai	Browse
	la.bot.arm.elf	Get hash	malicious	Mirai	Browse
	la.bot.arm6.elf	Get hash	malicious	Mirai	Browse

Domains

Match	Associated Sample Name / URL	SHA 256	Detection	Threat Name	Link	Context
daisy.ubuntu.com	x86_64.nn.elf	Get hash	malicious	Mirai, Okiru	Browse	162.213.35.24
	m68k.nn.elf	Get hash	malicious	Mirai, Okiru	Browse	162.213.35.24
	vlxx.arm6.elf	Get hash	malicious	Mirai, Okiru	Browse	162.213.35.25
	la.bot.powerpc.elf	Get hash	malicious	Mirai	Browse	162.213.35.24
	la.bot.sh4.elf	Get hash	malicious	Mirai	Browse	162.213.35.25
	la.bot.mipsel.elf	Get hash	malicious	Mirai	Browse	162.213.35.25
	la.bot.mips.elf	Get hash	malicious	Mirai	Browse	162.213.35.24
	la.bot.mipsel.elf	Get hash	malicious	Mirai	Browse	162.213.35.25
	la.bot.arm7.elf	Get hash	malicious	Mirai	Browse	162.213.35.25
	la.bot.m68k.elf	Get hash	malicious	Mirai	Browse	162.213.35.25

ASNs

Match	Associated Sample Name / URL	SHA 256	Detection	Threat Name	Link	Context
CANONICAL-ASGB	nn.elf	Get hash	malicious	Nanominer, Xmrig	Browse	91.189.91.42
	arm6.nn.elf	Get hash	malicious	Mirai, Okiru	Browse	91.189.91.42
	vlxx.m68k.elf	Get hash	malicious	Mirai, Gafgyt, Okiru	Browse	91.189.91.42
	vlxx.arm5.elf	Get hash	malicious	Mirai, Gafgyt, Okiru	Browse	91.189.91.42
	vlxx.arm.elf	Get hash	malicious	Mirai, Gafgyt, Okiru	Browse	91.189.91.42
	vlxx.mpsl.elf	Get hash	malicious	Mirai, Gafgyt, Okiru	Browse	185.125.190.26
	la.bot.m68k.elf	Get hash	malicious	Mirai	Browse	91.189.91.42
	la.bot.arm7.elf	Get hash	malicious	Mirai	Browse	91.189.91.42
	la.bot.arm5.elf	Get hash	malicious	Mirai	Browse	91.189.91.42
	la.bot.arm.elf	Get hash	malicious	Mirai	Browse	91.189.91.42
CANONICAL-ASGB	nn.elf	Get hash	malicious	Nanominer, Xmrig	Browse	91.189.91.42
	arm6.nn.elf	Get hash	malicious	Mirai, Okiru	Browse	91.189.91.42
	vlxx.m68k.elf	Get hash	malicious	Mirai, Gafgyt, Okiru	Browse	91.189.91.42
	vlxx.arm5.elf	Get hash	malicious	Mirai, Gafgyt, Okiru	Browse	91.189.91.42
	vlxx.arm.elf	Get hash	malicious	Mirai, Gafgyt, Okiru	Browse	91.189.91.42
	vlxx.mpsl.elf	Get hash	malicious	Mirai, Gafgyt, Okiru	Browse	185.125.190.26
	la.bot.m68k.elf	Get hash	malicious	Mirai	Browse	91.189.91.42
	la.bot.arm7.elf	Get hash	malicious	Mirai	Browse	91.189.91.42
	la.bot.arm5.elf	Get hash	malicious	Mirai	Browse	91.189.91.42
	la.bot.arm.elf	Get hash	malicious	Mirai	Browse	91.189.91.42
SKHT-ASShenzhenKatherineHengTechnologyInformationCo	Brooming.vbs	Get hash	malicious	Remcos, GuLoader	Browse	154.216.20.209
	doc55334.html	Get hash	malicious	HTMLPhisher	Browse	154.216.19.40
	crypted_UClient.exe	Get hash	malicious	XWorm	Browse	154.216.18.132
	22TxDBB1.bat	Get hash	malicious	Unknown	Browse	154.216.17.110
	Arrival Notice.exe	Get hash	malicious	Remcos	Browse	154.216.17.190
	jew.ppc.elf	Get hash	malicious	Unknown	Browse	156.230.19.169
	http://kmaybelsrka.sbs:6793/bab.zip	Get hash	malicious	Unknown	Browse	154.216.17.175
	https://garfieldthecat.tech/Receipt.html	Get hash	malicious	WinSearchAbuse	Browse	154.216.17.175
	Sublabially.vbs	Get hash	malicious	Remcos, GuLoader	Browse	154.216.18.216
	ZppxPm0ASs.exe	Get hash	malicious	Xmrig	Browse	154.216.20.243
INIT7CH	nn.elf	Get hash	malicious	Nanominer, Xmrig	Browse	109.202.202.202
	arm6.nn.elf	Get hash	malicious	Mirai, Okiru	Browse	109.202.202.202
	vlxx.m68k.elf	Get hash	malicious	Mirai, Gafgyt, Okiru	Browse	109.202.202.202
	vlxx.arm5.elf	Get hash	malicious	Mirai, Gafgyt, Okiru	Browse	109.202.202.202
	vlxx.arm.elf	Get hash	malicious	Mirai, Gafgyt, Okiru	Browse	109.202.202.202
	la.bot.m68k.elf	Get hash	malicious	Mirai	Browse	109.202.202.202
	la.bot.arm7.elf	Get hash	malicious	Mirai	Browse	109.202.202.202
	la.bot.arm5.elf	Get hash	malicious	Mirai	Browse	109.202.202.202
	la.bot.arm.elf	Get hash	malicious	Mirai	Browse	109.202.202.202
	la.bot.arm6.elf	Get hash	malicious	Mirai	Browse	109.202.202.202

JA3 Fingerprints

⊘No context

Dropped Files

⊘No context

Created / dropped Files

/run/systemd/seats/.#seat085RphJ

Download File

Process:	/lib/systemd/systemd-logind
File Type:	ASCII text
Category:	dropped
Size (bytes):	95
Entropy (8bit):	4.921230646592726
Encrypted:	false
SSDEEP:	3:SbFVVmFyinKMsuH47rLg205vmLUbr+v:SbFuFyLwH47Pg20ggWv
MD5:	BE58CCABC942125F5E27AF6EB1BA2F88
SHA1:	07C20F55E36EE48869B223B8FC4DBC227C7353AC
SHA-256:	551B1D1C8E5953D5D0CF49C83C1568E2FBEF8BDDB69903B3DA82240B777B4629
SHA-512:	E5A270995FDE80530927E0BACD3BF76EE820C968AABD55D2E34579326F388AFD6DE7FB8C5D54F69D3F6AC30A5B587FD3B0456FC60326E7DF4F45789A900D046C
Malicious:	false
Reputation:	moderate, very likely benign file
Preview:	# This is private data. Do not parse..IS_SEAT0=1.CAN_MULTI_SESSION=1.CAN_TTY=1.CAN_GRAPHICAL=0.

/run/systemd/seats/.#seat0ObhoQQ

Download File

Process:	/lib/systemd/systemd-logind
File Type:	ASCII text
Category:	dropped
Size (bytes):	95
Entropy (8bit):	4.921230646592726
Encrypted:	false
SSDEEP:	3:SbFVVmFyinKMsuH47rLg205vmLUbr+v:SbFuFyLwH47Pg20ggWv
MD5:	BE58CCABC942125F5E27AF6EB1BA2F88
SHA1:	07C20F55E36EE48869B223B8FC4DBC227C7353AC
SHA-256:	551B1D1C8E5953D5D0CF49C83C1568E2FBEF8BDDB69903B3DA82240B777B4629
SHA-512:	E5A270995FDE80530927E0BACD3BF76EE820C968AABD55D2E34579326F388AFD6DE7FB8C5D54F69D3F6AC30A5B587FD3B0456FC60326E7DF4F45789A900D046C
Malicious:	false
Reputation:	moderate, very likely benign file
Preview:	# This is private data. Do not parse..IS_SEAT0=1.CAN_MULTI_SESSION=1.CAN_TTY=1.CAN_GRAPHICAL=0.

/var/log/auth.log

Download File

Process:	/usr/sbin/rsyslogd
File Type:	ASCII text
Category:	dropped
Size (bytes):	624
Entropy (8bit):	4.890697047226161
Encrypted:	false
SSDEEP:	12:nS3fWFNmS3fWFNDS3fWFN7S3fWFmMzS3fWFCAvmUS5FCA2+VRS5Fr:ne7kXAvhA2+V6
MD5:	86AECF6C8197E05951A64221F149FDC7
SHA1:	B519D5EB1167D736E6551240314B14ACC9376383
SHA-256:	5CB79F8A8BE62B0E38EC9A1C1DF4CAB514DCC803B4E48EFAC91E9AAD74DF1FAC
SHA-512:	D28ACA08E9A9E846FCD86A6CAF2D239C779D653FE779B5BDF5368A366EF8992CDB20BFA0C7D8FC33053C8C3CCFFD7FAA6A4678196B26BC8024430FADFDE81FE0
Malicious:	false
Reputation:	low
Preview:	Dec 22 05:57:00 galassia systemd-logind[6304]: User of session c2 not known..Dec 22 05:57:00 galassia systemd-logind[6304]: User of session 2 not known..Dec 22 05:57:00 galassia systemd-logind[6304]: User of session c1 not known..Dec 22 05:57:00 galassia systemd-logind[6304]: Session enumeration failed: No such file or directory.Dec 22 05:57:00 galassia systemd-logind[6304]: Watching system buttons on /dev/input/event0 (Power Button).Dec 22 05:57:01 galassia systemd-logind[6304]: Watching system buttons on /dev/input/event1 (AT Translated Set 2 keyboard).Dec 22 05:57:01 galassia systemd-logind[6304]: New seat seat0..

/var/log/kern.log

Download File

Process:	/usr/sbin/rsyslogd
File Type:	ASCII text
Category:	dropped
Size (bytes):	1234
Entropy (8bit):	4.72192508863896
Encrypted:	false
SSDEEP:	24:0F6pbFCUwFnNkhLFtolAFPlSFLGRSFoAIMmF2nAIMpFAAIn4FXVSFIPMFpYNFvYB:0FWbF0FNkLF2lAFdSFKSFmnFc0F+4FQ3
MD5:	208651641FA3FFFD27B4C3E321BA8FBC
SHA1:	280B64171297B9A191027675E8022EC69CFAB0D9
SHA-256:	7BEA1E6CBA9A5C203A56780B7A39C670CAA4D2BF7E1B5DA3BD3EEF4FA8F3DC35
SHA-512:	93E4ABA268B1BCA61C093832F65E16F3F466003F6E2DB3CD69D5F152EF3502CE533D104A79F00CC9994582B03B44915CB132959AAA8FAE656A955A876EFAEB47
Malicious:	false
Reputation:	low
Preview:	Dec 22 05:57:26 galassia kernel: [ 451.117063] blocking signal 9: 6241 -> 772.Dec 22 05:57:26 galassia kernel: [ 451.157711] blocking signal 9: 6241 -> 936.Dec 22 05:57:26 galassia kernel: [ 451.188452] blocking signal 9: 6241 -> 1601.Dec 22 05:57:26 galassia kernel: [ 451.199226] blocking signal 9: 6241 -> 2048.Dec 22 05:57:26 galassia kernel: [ 451.247583] blocking signal 9: 6238 -> 1.Dec 22 05:57:26 galassia kernel: [ 451.372965] blocking signal 9: 6241 -> 1.Dec 22 05:57:26 galassia kernel: [ 451.946772] New task spawned: old: (tgid 6526, tid 6526), new (tgid: 6526, tid: 6530).Dec 22 05:57:26 galassia kernel: [ 451.948329] New task spawned: old: (tgid 6526, tid 6526), new (tgid: 6526, tid: 6531).Dec 22 05:57:26 galassia kernel: [ 451.956311] New task spawned: old: (tgid 6526, tid 6530), new (tgid: 6526, tid: 6532).Dec 22 05:57:26 galassia kernel: [ 452.109282] blocking signal 9: 6238 -> 658.Dec 22 05:57:26 galassia kernel: [ 452.148110] blocking signal 9: 6238 -> 720.Dec

/var/log/syslog

Download File

Process:	/usr/sbin/rsyslogd
File Type:	ASCII text
Category:	dropped
Size (bytes):	4063
Entropy (8bit):	5.034479540946977
Encrypted:	false
SSDEEP:	96:SpDRrAKTzov91cbu+CAS5KPakvkglOfA165kc5:E9ANq4f
MD5:	29CCE8B58D68D637DB9E032457A52159
SHA1:	B549C302D600E42B6373065145208413CB18793C
SHA-256:	2E4DB172FC69521D2A4C4C894CCBB3C8013A7A24A7229989D962B88F7618C6A5
SHA-512:	63518939C414CE4C18C32998F09C38A19E6FD5E950A0261762AF1893932C6743AE3E5A3405BC4FE8D5D41E59D17E34CCC26BF7A966DCE26E4A4C408BE820123F
Malicious:	false
Reputation:	low
Preview:	Dec 22 05:57:25 galassia systemd[1]: rsyslog.service: Main process exited, code=killed, status=9/KILL.Dec 22 05:57:25 galassia systemd[1]: rsyslog.service: Failed with result 'signal'..Dec 22 05:57:25 galassia systemd[1]: whoopsie.service: Main process exited, code=killed, status=9/KILL.Dec 22 05:57:25 galassia systemd[1]: whoopsie.service: Failed with result 'signal'..Dec 22 05:57:25 galassia systemd[1860]: pulseaudio.service: Main process exited, code=killed, status=9/KILL.Dec 22 05:57:25 galassia systemd[1860]: pulseaudio.service: Failed with result 'signal'..Dec 22 05:57:25 galassia systemd[1860]: Failed to start Sound Service..Dec 22 05:57:25 galassia systemd[1]: gpu-manager.service: Main process exited, code=killed, status=9/KILL.Dec 22 05:57:25 galassia systemd[1]: gpu-manager.service: Failed with result 'signal'..Dec 22 05:57:25 galassia systemd[1]: Failed to start Detect the available GPUs and deal with any system changes..Dec 22 05:57:25 galassia systemd[1]: Starting GNOME Di

Static File Info

General

File type:	ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), statically linked, no section header
Entropy (8bit):	7.957529608157285
TrID:	ELF Executable and Linkable format (Linux) (4029/14) 50.16% ELF Executable and Linkable format (generic) (4004/1) 49.84%
File name:	byte.x86.elf
File size:	37'816 bytes
MD5:	7f450c92cd48f89e76cc42545287a95c
SHA1:	417afaa1961773ef81080998fbeeb04e112e8f30
SHA256:	883e0e27500a5dd5d22ebe043110896ec2223dfb1ce2dd152fe2da1a7f85aca0
SHA512:	f3e0c0e883fdec93644309bb4fb214c6b92adab7ca62ed34e4c2416157f5e336f88bf3093de474d0dca1784854078aa2561ffd7d61ca6244403afcdc82e24591
SSDEEP:	768:7SIF9NtuCtdnD4cqrgVJbKGbVDTETaOZHHYkRGnbcuyD7UFe:+hCn1qrgzbNmHrGnouy8U
TLSH:	B203F1B0B8DA8520D6FC38350015B59C5A10BA8E772FEDCB3B0D247140D13E96DAABCE
File Content Preview:	.ELF........................4...........4. ...(.............................................. ... ......`...........Q.td................................UPX!........0%..0%......W..........?.E.h;....#..\|`F..y..c.o.v........_5P....;..tn..{.....f.......%.....

Static ELF Info

ELF header
Class:	ELF32
Data:	2's complement, little endian
Version:	1 (current)
Machine:	Intel 80386
Version Number:	0x1
Type:	EXEC (Executable file)
OS/ABI:	UNIX - Linux
ABI Version:	0
Entry Point Address:	0x804ffe8
Flags:	0x0
ELF Header Size:	52
Program Header Offset:	52
Program Header Size:	32
Number of Program Headers:	3
Section Header Offset:	0
Section Header Size:	40
Number of Section Headers:	0
Header String Table Index:	0

Program Segments

Type	Offset	Virtual Address	Physical Address	File Size	Memory Size	Entropy	Flags	Flags Description	Align
LOAD	0x0	0x8048000	0x8048000	0x92c7	0x92c7	7.9598	0x5	R E	0x1000
LOAD	0x0	0x8052000	0x8052000	0x0	0xbb60	0.0000	0x6	RW	0x1000
GNU_STACK	0x0	0x0	0x0	0x0	0x0	0.0000	0x6	RW	0x4

Network Behavior

Network Port Distribution

TCP Packets

Timestamp	Source Port	Dest Port	Source IP	Dest IP
Dec 22, 2024 12:56:53.278242111 CET	43928	443	192.168.2.23	91.189.91.42
Dec 22, 2024 12:56:54.192795038 CET	43546	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:56:54.313894033 CET	777	43546	154.216.19.138	192.168.2.23
Dec 22, 2024 12:56:54.313957930 CET	43546	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:56:54.313976049 CET	43546	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:56:54.433553934 CET	777	43546	154.216.19.138	192.168.2.23
Dec 22, 2024 12:56:54.433598042 CET	43546	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:56:54.554137945 CET	777	43546	154.216.19.138	192.168.2.23
Dec 22, 2024 12:56:55.609148979 CET	777	43546	154.216.19.138	192.168.2.23
Dec 22, 2024 12:56:55.609241962 CET	43546	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:56:55.609241962 CET	43546	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:56:56.567007065 CET	43550	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:56:56.687030077 CET	777	43550	154.216.19.138	192.168.2.23
Dec 22, 2024 12:56:56.687086105 CET	43550	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:56:56.687108040 CET	43550	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:56:56.807178020 CET	777	43550	154.216.19.138	192.168.2.23
Dec 22, 2024 12:56:56.807228088 CET	43550	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:56:56.926750898 CET	777	43550	154.216.19.138	192.168.2.23
Dec 22, 2024 12:56:57.986587048 CET	777	43550	154.216.19.138	192.168.2.23
Dec 22, 2024 12:56:57.986660004 CET	43550	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:56:57.986660004 CET	43550	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:56:58.657475948 CET	42836	443	192.168.2.23	91.189.91.43
Dec 22, 2024 12:56:58.941706896 CET	43552	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:56:59.061382055 CET	777	43552	154.216.19.138	192.168.2.23
Dec 22, 2024 12:56:59.061441898 CET	43552	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:56:59.061471939 CET	43552	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:56:59.181044102 CET	777	43552	154.216.19.138	192.168.2.23
Dec 22, 2024 12:56:59.181143045 CET	43552	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:56:59.300971985 CET	777	43552	154.216.19.138	192.168.2.23
Dec 22, 2024 12:56:59.421384096 CET	42516	80	192.168.2.23	109.202.202.202
Dec 22, 2024 12:57:00.361601114 CET	777	43552	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:00.361696005 CET	43552	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:00.361696005 CET	43552	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:00.496033907 CET	43554	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:00.615609884 CET	777	43554	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:00.615695953 CET	43554	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:00.615695953 CET	43554	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:00.735336065 CET	777	43554	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:00.735388994 CET	43554	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:00.854973078 CET	777	43554	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:01.915170908 CET	777	43554	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:01.915419102 CET	43554	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:01.915419102 CET	43554	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:02.051660061 CET	43556	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:02.171298027 CET	777	43556	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:02.171410084 CET	43556	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:02.171410084 CET	43556	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:02.291341066 CET	777	43556	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:02.291413069 CET	43556	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:02.410870075 CET	777	43556	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:03.471945047 CET	777	43556	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:03.472037077 CET	43556	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:03.472037077 CET	43556	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:03.607276917 CET	43558	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:03.727699041 CET	777	43558	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:03.727787971 CET	43558	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:03.727787971 CET	43558	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:03.848901987 CET	777	43558	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:03.849009037 CET	43558	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:03.969870090 CET	777	43558	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:05.138797045 CET	777	43558	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:05.138878107 CET	43558	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:05.138879061 CET	43558	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:05.972373962 CET	43560	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:06.092001915 CET	777	43560	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:06.092075109 CET	43560	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:06.092123985 CET	43560	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:06.211740971 CET	777	43560	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:06.211802006 CET	43560	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:06.331490040 CET	777	43560	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:07.394670963 CET	777	43560	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:07.394743919 CET	43560	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:07.394817114 CET	43560	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:08.352583885 CET	43562	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:08.475519896 CET	777	43562	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:08.475652933 CET	43562	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:08.475652933 CET	43562	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:08.595612049 CET	777	43562	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:08.595696926 CET	43562	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:08.716922998 CET	777	43562	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:09.778342009 CET	777	43562	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:09.778448105 CET	43562	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:09.778448105 CET	43562	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:09.913055897 CET	43564	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:10.032685995 CET	777	43564	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:10.032749891 CET	43564	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:10.032793045 CET	43564	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:10.155694008 CET	777	43564	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:10.155767918 CET	43564	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:10.340100050 CET	777	43564	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:11.332165003 CET	777	43564	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:11.332227945 CET	43564	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:11.332256079 CET	43564	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:11.466360092 CET	43566	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:11.586086035 CET	777	43566	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:11.586143017 CET	43566	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:11.586184025 CET	43566	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:11.706583977 CET	777	43566	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:11.706635952 CET	43566	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:11.826281071 CET	777	43566	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:12.887988091 CET	777	43566	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:12.888058901 CET	43566	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:12.888101101 CET	43566	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:13.022685051 CET	43568	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:13.142409086 CET	777	43568	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:13.142528057 CET	43568	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:13.142528057 CET	43568	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:13.262204885 CET	777	43568	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:13.262286901 CET	43568	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:13.382424116 CET	777	43568	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:14.267369986 CET	43928	443	192.168.2.23	91.189.91.42
Dec 22, 2024 12:57:14.440063953 CET	777	43568	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:14.440144062 CET	43568	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:14.440144062 CET	43568	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:14.574932098 CET	43570	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:14.694701910 CET	777	43570	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:14.694768906 CET	43570	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:14.694783926 CET	43570	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:14.814378023 CET	777	43570	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:14.814425945 CET	43570	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:14.934174061 CET	777	43570	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:15.993043900 CET	777	43570	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:15.993109941 CET	43570	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:15.993134975 CET	43570	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:16.532928944 CET	43572	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:16.652483940 CET	777	43572	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:16.652597904 CET	43572	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:16.652597904 CET	43572	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:16.772336006 CET	777	43572	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:16.772396088 CET	43572	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:16.891916037 CET	777	43572	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:17.950921059 CET	777	43572	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:17.951010942 CET	43572	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:17.951010942 CET	43572	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:18.084920883 CET	43574	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:18.204597950 CET	777	43574	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:18.204689026 CET	43574	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:18.204689026 CET	43574	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:18.324615955 CET	777	43574	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:18.324682951 CET	43574	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:18.445025921 CET	777	43574	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:19.511750937 CET	777	43574	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:19.511842966 CET	43574	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:19.511842966 CET	43574	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:19.645900965 CET	43576	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:19.765445948 CET	777	43576	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:19.765513897 CET	43576	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:19.765575886 CET	43576	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:19.885124922 CET	777	43576	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:19.885186911 CET	43576	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:20.004668951 CET	777	43576	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:21.067959070 CET	777	43576	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:21.068046093 CET	43576	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:21.068046093 CET	43576	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:21.201982021 CET	43578	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:21.321568966 CET	777	43578	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:21.321697950 CET	43578	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:21.321698904 CET	43578	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:21.441373110 CET	777	43578	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:21.441450119 CET	43578	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:21.561001062 CET	777	43578	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:22.619774103 CET	777	43578	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:22.619867086 CET	43578	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:22.619867086 CET	43578	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:22.753884077 CET	43580	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:22.873594999 CET	777	43580	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:22.873667002 CET	43580	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:22.873734951 CET	43580	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:22.993248940 CET	777	43580	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:22.993304968 CET	43580	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:23.113049030 CET	777	43580	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:24.175458908 CET	777	43580	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:24.175527096 CET	43580	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:24.175591946 CET	43580	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:24.310256958 CET	43582	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:24.429877996 CET	777	43582	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:24.429991961 CET	43582	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:24.429991961 CET	43582	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:24.509951115 CET	42836	443	192.168.2.23	91.189.91.43
Dec 22, 2024 12:57:24.549787045 CET	777	43582	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:24.549860001 CET	43582	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:24.669384956 CET	777	43582	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:25.730863094 CET	777	43582	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:25.730956078 CET	43582	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:25.730956078 CET	43582	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:25.864970922 CET	43584	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:25.985261917 CET	777	43584	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:25.985321045 CET	43584	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:25.985411882 CET	43584	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:26.105071068 CET	777	43584	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:26.105123043 CET	43584	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:26.224693060 CET	777	43584	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:27.285531044 CET	777	43584	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:27.285609961 CET	43584	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:27.285609961 CET	43584	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:27.420145988 CET	43586	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:27.540293932 CET	777	43586	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:27.540404081 CET	43586	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:27.540405035 CET	43586	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:27.661994934 CET	777	43586	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:27.662086964 CET	43586	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:27.782860994 CET	777	43586	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:28.841651917 CET	777	43586	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:28.843458891 CET	43586	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:28.843460083 CET	43586	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:28.978518009 CET	43588	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:29.098412991 CET	777	43588	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:29.098520994 CET	43588	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:29.098520994 CET	43588	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:29.218099117 CET	777	43588	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:29.218144894 CET	43588	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:29.337785006 CET	777	43588	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:30.397362947 CET	777	43588	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:30.397439003 CET	43588	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:30.397439003 CET	43588	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:30.531308889 CET	43590	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:30.649127960 CET	42516	80	192.168.2.23	109.202.202.202
Dec 22, 2024 12:57:30.650731087 CET	777	43590	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:30.650791883 CET	43590	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:30.650827885 CET	43590	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:30.789012909 CET	777	43590	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:30.789067030 CET	43590	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:31.000013113 CET	777	43590	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:31.948031902 CET	777	43590	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:31.948117971 CET	43590	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:31.948118925 CET	43590	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:32.082182884 CET	43592	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:32.201948881 CET	777	43592	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:32.202013969 CET	43592	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:32.202065945 CET	43592	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:32.321624994 CET	777	43592	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:32.321681976 CET	43592	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:32.441237926 CET	777	43592	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:33.502331972 CET	777	43592	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:33.503410101 CET	43592	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:33.503431082 CET	43592	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:33.638889074 CET	43594	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:33.758542061 CET	777	43594	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:33.758656025 CET	43594	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:33.758656025 CET	43594	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:33.878361940 CET	777	43594	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:33.880326033 CET	43594	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:34.000468016 CET	777	43594	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:35.060872078 CET	777	43594	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:35.060926914 CET	43594	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:35.060949087 CET	43594	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:35.184674978 CET	43596	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:35.304272890 CET	777	43596	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:35.304344893 CET	43596	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:35.304394960 CET	43596	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:35.424005985 CET	777	43596	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:35.424072981 CET	43596	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:35.543665886 CET	777	43596	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:36.609879017 CET	777	43596	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:36.609988928 CET	43596	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:36.609988928 CET	43596	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:36.744024992 CET	43598	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:36.863723040 CET	777	43598	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:36.863812923 CET	43598	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:36.863812923 CET	43598	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:36.983397961 CET	777	43598	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:36.983453989 CET	43598	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:37.103138924 CET	777	43598	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:38.184422016 CET	777	43598	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:38.184560061 CET	43598	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:38.184560061 CET	43598	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:38.318856955 CET	43600	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:38.438391924 CET	777	43600	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:38.438443899 CET	43600	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:38.438457966 CET	43600	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:38.558017015 CET	777	43600	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:38.558096886 CET	43600	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:38.677731991 CET	777	43600	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:39.734411001 CET	777	43600	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:39.734483004 CET	43600	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:39.734530926 CET	43600	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:39.868617058 CET	43602	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:39.988240957 CET	777	43602	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:39.988295078 CET	43602	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:39.988322973 CET	43602	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:40.108109951 CET	777	43602	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:40.108159065 CET	43602	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:40.227868080 CET	777	43602	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:41.290636063 CET	777	43602	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:41.290707111 CET	43602	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:41.290775061 CET	43602	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:41.424669027 CET	43604	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:41.544267893 CET	777	43604	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:41.544327021 CET	43604	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:41.544387102 CET	43604	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:41.664000034 CET	777	43604	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:41.664053917 CET	43604	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:41.783741951 CET	777	43604	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:42.844574928 CET	777	43604	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:42.844669104 CET	43604	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:42.844669104 CET	43604	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:42.978746891 CET	43606	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:43.098424911 CET	777	43606	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:43.098479986 CET	43606	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:43.098520994 CET	43606	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:43.218054056 CET	777	43606	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:43.218107939 CET	43606	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:43.337687016 CET	777	43606	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:44.397763014 CET	777	43606	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:44.397834063 CET	43606	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:44.397834063 CET	43606	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:44.532126904 CET	43608	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:44.651953936 CET	777	43608	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:44.652013063 CET	43608	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:44.652061939 CET	43608	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:44.771595955 CET	777	43608	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:44.771657944 CET	43608	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:44.891235113 CET	777	43608	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:45.953175068 CET	777	43608	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:45.953250885 CET	43608	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:45.953250885 CET	43608	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:46.087994099 CET	43610	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:46.207818031 CET	777	43610	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:46.207873106 CET	43610	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:46.207926035 CET	43610	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:46.327470064 CET	777	43610	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:46.327527046 CET	43610	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:46.447132111 CET	777	43610	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:47.618220091 CET	777	43610	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:47.618321896 CET	43610	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:47.738204002 CET	777	43610	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:48.754268885 CET	43612	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:48.873864889 CET	777	43612	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:48.873929977 CET	43612	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:48.873977900 CET	43612	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:48.993460894 CET	777	43612	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:48.993535995 CET	43612	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:49.116029024 CET	777	43612	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:50.170012951 CET	777	43612	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:50.170110941 CET	43612	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:50.170135021 CET	43612	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:50.304297924 CET	43614	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:50.423820019 CET	777	43614	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:50.423890114 CET	43614	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:50.423923016 CET	43614	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:50.543494940 CET	777	43614	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:50.543576002 CET	43614	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:50.663254023 CET	777	43614	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:51.725927114 CET	777	43614	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:51.725991011 CET	43614	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:51.726015091 CET	43614	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:51.848944902 CET	43616	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:51.968641043 CET	777	43616	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:51.968719006 CET	43616	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:51.968719959 CET	43616	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:52.088577032 CET	777	43616	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:52.088624954 CET	43616	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:52.208229065 CET	777	43616	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:53.269671917 CET	777	43616	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:53.269728899 CET	43616	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:53.269766092 CET	43616	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:54.225909948 CET	43618	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:54.345482111 CET	777	43618	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:54.345541000 CET	43618	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:54.345581055 CET	43618	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:54.465022087 CET	777	43618	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:54.465065002 CET	43618	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:54.584530115 CET	777	43618	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:55.221796989 CET	43928	443	192.168.2.23	91.189.91.42
Dec 22, 2024 12:57:55.641671896 CET	777	43618	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:55.641738892 CET	43618	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:55.641765118 CET	43618	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:55.776408911 CET	43620	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:55.896019936 CET	777	43620	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:55.896100044 CET	43620	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:55.896147966 CET	43620	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:56.015880108 CET	777	43620	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:56.015944004 CET	43620	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:56.135595083 CET	777	43620	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:57.212583065 CET	777	43620	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:57.212686062 CET	43620	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:57.212686062 CET	43620	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:57.347261906 CET	43622	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:57.466933966 CET	777	43622	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:57.467012882 CET	43622	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:57.467050076 CET	43622	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:57.586644888 CET	777	43622	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:57.586711884 CET	43622	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:57.706316948 CET	777	43622	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:58.765980005 CET	777	43622	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:58.766084909 CET	43622	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:58.766084909 CET	43622	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:58.900290012 CET	43624	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:59.022253990 CET	777	43624	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:59.022332907 CET	43624	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:59.022387981 CET	43624	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:59.141953945 CET	777	43624	154.216.19.138	192.168.2.23
Dec 22, 2024 12:57:59.142020941 CET	43624	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:57:59.261698008 CET	777	43624	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:00.321063042 CET	777	43624	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:00.321132898 CET	43624	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:00.321132898 CET	43624	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:00.455085039 CET	43626	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:00.574712992 CET	777	43626	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:00.574778080 CET	43626	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:00.574819088 CET	43626	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:00.694541931 CET	777	43626	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:00.694605112 CET	43626	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:00.814218998 CET	777	43626	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:01.874676943 CET	777	43626	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:01.874757051 CET	43626	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:01.874757051 CET	43626	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:02.009372950 CET	43628	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:02.129842043 CET	777	43628	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:02.129933119 CET	43628	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:02.129933119 CET	43628	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:02.250303030 CET	777	43628	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:02.250365973 CET	43628	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:02.370511055 CET	777	43628	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:03.431248903 CET	777	43628	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:03.431359053 CET	43628	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:03.431389093 CET	43628	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:03.565439939 CET	43630	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:03.685765982 CET	777	43630	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:03.685834885 CET	43630	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:03.685883999 CET	43630	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:03.805397987 CET	777	43630	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:03.805479050 CET	43630	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:03.925719023 CET	777	43630	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:04.998505116 CET	777	43630	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:04.998580933 CET	43630	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:04.998657942 CET	43630	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:05.121530056 CET	43632	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:05.241388083 CET	777	43632	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:05.241465092 CET	43632	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:05.241502047 CET	43632	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:05.361332893 CET	777	43632	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:05.361390114 CET	43632	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:05.481054068 CET	777	43632	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:06.673773050 CET	777	43632	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:06.673862934 CET	43632	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:06.794218063 CET	777	43632	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:07.812176943 CET	43634	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:07.931720018 CET	777	43634	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:07.931843996 CET	43634	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:07.931859016 CET	43634	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:08.052023888 CET	777	43634	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:08.052081108 CET	43634	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:08.171732903 CET	777	43634	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:09.229123116 CET	777	43634	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:09.229180098 CET	43634	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:09.229199886 CET	43634	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:09.363020897 CET	43636	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:09.482850075 CET	777	43636	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:09.482971907 CET	43636	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:09.482971907 CET	43636	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:09.602957010 CET	777	43636	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:09.603063107 CET	43636	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:09.722656012 CET	777	43636	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:10.781801939 CET	777	43636	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:10.781868935 CET	43636	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:10.781898975 CET	43636	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:10.917628050 CET	43638	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:11.037269115 CET	777	43638	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:11.037328959 CET	43638	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:11.037348032 CET	43638	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:11.157227039 CET	777	43638	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:11.157278061 CET	43638	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:11.276915073 CET	777	43638	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:12.339839935 CET	777	43638	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:12.339910030 CET	43638	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:12.339947939 CET	43638	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:12.474581957 CET	43640	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:12.594072104 CET	777	43640	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:12.594162941 CET	43640	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:12.594203949 CET	43640	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:12.713937998 CET	777	43640	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:12.714015961 CET	43640	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:12.833662033 CET	777	43640	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:13.903286934 CET	777	43640	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:13.903364897 CET	43640	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:13.903398037 CET	43640	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:14.037498951 CET	43642	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:14.157303095 CET	777	43642	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:14.157377958 CET	43642	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:14.157422066 CET	43642	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:14.277396917 CET	777	43642	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:14.277463913 CET	43642	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:14.397061110 CET	777	43642	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:15.477201939 CET	777	43642	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:15.477274895 CET	43642	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:15.477303028 CET	43642	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:15.698978901 CET	42836	443	192.168.2.23	91.189.91.43
Dec 22, 2024 12:58:15.716227055 CET	43644	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:15.835896969 CET	777	43644	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:15.835953951 CET	43644	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:15.836016893 CET	43644	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:15.955657959 CET	777	43644	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:15.955764055 CET	43644	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:16.075371027 CET	777	43644	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:17.140502930 CET	777	43644	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:17.140582085 CET	43644	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:17.140582085 CET	43644	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:17.275429010 CET	43646	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:17.395201921 CET	777	43646	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:17.395262957 CET	43646	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:17.395302057 CET	43646	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:17.515038967 CET	777	43646	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:17.515105009 CET	43646	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:17.634948015 CET	777	43646	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:18.694740057 CET	777	43646	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:18.694818974 CET	43646	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:18.694819927 CET	43646	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:18.828808069 CET	43648	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:18.948386908 CET	777	43648	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:18.948494911 CET	43648	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:18.948508978 CET	43648	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:19.068345070 CET	777	43648	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:19.068470955 CET	43648	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:19.189050913 CET	777	43648	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:20.246299028 CET	777	43648	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:20.246371031 CET	43648	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:20.246392965 CET	43648	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:20.381078005 CET	43650	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:20.500623941 CET	777	43650	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:20.500693083 CET	43650	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:20.500727892 CET	43650	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:20.622210026 CET	777	43650	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:20.622279882 CET	43650	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:20.741848946 CET	777	43650	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:21.800492048 CET	777	43650	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:21.800565004 CET	43650	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:21.800590038 CET	43650	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:21.934448004 CET	43652	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:22.054131031 CET	777	43652	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:22.054315090 CET	43652	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:22.054315090 CET	43652	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:22.175578117 CET	777	43652	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:22.175658941 CET	43652	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:22.295594931 CET	777	43652	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:23.354399920 CET	777	43652	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:23.354515076 CET	43652	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:23.354515076 CET	43652	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:23.488763094 CET	43654	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:23.608418941 CET	777	43654	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:23.608489037 CET	43654	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:23.608546019 CET	43654	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:23.728226900 CET	777	43654	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:23.728296995 CET	43654	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:23.848004103 CET	777	43654	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:24.908571005 CET	777	43654	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:24.908648014 CET	43654	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:24.908720970 CET	43654	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:25.031559944 CET	43656	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:25.151355028 CET	777	43656	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:25.151415110 CET	43656	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:25.151432037 CET	43656	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:25.271073103 CET	777	43656	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:25.271126986 CET	43656	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:25.390759945 CET	777	43656	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:26.452815056 CET	777	43656	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:26.452887058 CET	43656	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:26.452920914 CET	43656	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:26.588098049 CET	43658	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:26.707782030 CET	777	43658	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:26.707844019 CET	43658	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:26.707874060 CET	43658	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:26.828013897 CET	777	43658	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:26.828079939 CET	43658	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:26.947901964 CET	777	43658	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:28.120212078 CET	777	43658	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:28.120313883 CET	43658	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:28.239962101 CET	777	43658	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:29.243876934 CET	43660	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:29.363481045 CET	777	43660	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:29.363554001 CET	43660	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:29.363581896 CET	43660	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:29.483350039 CET	777	43660	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:29.483406067 CET	43660	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:29.603143930 CET	777	43660	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:30.663619041 CET	777	43660	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:30.663718939 CET	43660	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:30.663758993 CET	43660	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:30.786530972 CET	43662	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:30.906450033 CET	777	43662	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:30.906519890 CET	43662	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:30.906553984 CET	43662	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:31.026313066 CET	777	43662	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:31.026376963 CET	43662	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:31.146102905 CET	777	43662	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:32.208841085 CET	777	43662	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:32.208910942 CET	43662	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:32.208961010 CET	43662	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:32.343095064 CET	43664	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:32.462940931 CET	777	43664	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:32.463011026 CET	43664	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:32.463063002 CET	43664	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:32.583997965 CET	777	43664	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:32.584048033 CET	43664	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:32.703881025 CET	777	43664	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:33.765971899 CET	777	43664	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:33.766045094 CET	43664	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:33.766045094 CET	43664	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:33.889031887 CET	43666	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:34.008632898 CET	777	43666	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:34.008698940 CET	43666	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:34.008744955 CET	43666	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:34.128391027 CET	777	43666	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:34.128463030 CET	43666	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:34.248121977 CET	777	43666	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:35.311433077 CET	777	43666	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:35.311496019 CET	43666	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:35.311597109 CET	43666	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:35.434171915 CET	43668	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:35.553749084 CET	777	43668	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:35.553806067 CET	43668	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:35.553838968 CET	43668	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:35.674078941 CET	777	43668	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:35.674137115 CET	43668	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:35.793711901 CET	777	43668	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:36.855073929 CET	777	43668	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:36.855151892 CET	43668	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:36.855191946 CET	43668	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:36.989636898 CET	43670	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:37.109308958 CET	777	43670	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:37.109379053 CET	43670	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:37.109424114 CET	43670	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:37.229131937 CET	777	43670	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:37.229224920 CET	43670	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:37.616033077 CET	43670	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:37.803778887 CET	777	43670	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:37.803797007 CET	777	43670	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:38.410471916 CET	777	43670	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:38.410569906 CET	43670	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:38.410569906 CET	43670	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:38.544928074 CET	43672	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:38.664612055 CET	777	43672	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:38.664690018 CET	43672	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:38.664724112 CET	43672	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:38.784293890 CET	777	43672	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:38.784362078 CET	43672	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:39.051842928 CET	777	43672	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:39.963212967 CET	777	43672	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:39.963279009 CET	43672	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:39.963316917 CET	43672	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:40.086055994 CET	43674	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:40.206007004 CET	777	43674	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:40.206073046 CET	43674	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:40.206073046 CET	43674	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:40.325668097 CET	777	43674	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:40.325723886 CET	43674	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:40.445436954 CET	777	43674	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:41.519190073 CET	777	43674	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:41.519257069 CET	43674	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:41.519300938 CET	43674	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:41.653594017 CET	43676	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:41.773236036 CET	777	43676	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:41.773324966 CET	43676	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:41.773406029 CET	43676	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:41.892967939 CET	777	43676	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:41.893032074 CET	43676	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:42.012634993 CET	777	43676	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:43.073318958 CET	777	43676	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:43.073399067 CET	43676	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:43.073400021 CET	43676	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:43.196753979 CET	43678	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:43.316488981 CET	777	43678	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:43.316601038 CET	43678	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:43.316653967 CET	43678	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:43.436383009 CET	777	43678	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:43.436451912 CET	43678	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:43.556061983 CET	777	43678	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:44.735857964 CET	777	43678	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:44.735959053 CET	43678	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:44.855504990 CET	777	43678	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:45.859693050 CET	43680	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:45.979624033 CET	777	43680	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:45.979723930 CET	43680	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:45.979890108 CET	43680	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:46.099910021 CET	777	43680	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:46.099983931 CET	43680	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:46.219809055 CET	777	43680	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:47.278919935 CET	777	43680	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:47.279026031 CET	43680	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:47.279124022 CET	43680	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:47.413268089 CET	43682	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:47.532907009 CET	777	43682	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:47.532974005 CET	43682	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:47.533006907 CET	43682	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:47.652559042 CET	777	43682	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:47.652616024 CET	43682	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:47.772181034 CET	777	43682	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:48.847424030 CET	777	43682	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:48.847492933 CET	43682	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:48.847549915 CET	43682	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:48.970418930 CET	43684	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:49.090293884 CET	777	43684	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:49.090352058 CET	43684	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:49.090377092 CET	43684	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:49.210319042 CET	777	43684	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:49.210400105 CET	43684	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:49.330146074 CET	777	43684	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:50.391793966 CET	777	43684	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:50.391871929 CET	43684	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:50.391910076 CET	43684	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:50.526659012 CET	43686	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:50.646322966 CET	777	43686	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:50.646533966 CET	43686	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:50.646533966 CET	43686	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:50.766200066 CET	777	43686	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:50.766266108 CET	43686	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:50.886163950 CET	777	43686	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:51.948296070 CET	777	43686	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:51.948368073 CET	43686	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:51.948462963 CET	43686	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:52.071089029 CET	43688	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:52.190747976 CET	777	43688	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:52.190800905 CET	43688	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:52.190839052 CET	43688	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:52.310697079 CET	777	43688	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:52.310760975 CET	43688	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:52.430450916 CET	777	43688	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:53.490533113 CET	777	43688	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:53.490598917 CET	43688	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:53.490642071 CET	43688	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:53.625164032 CET	43690	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:53.744923115 CET	777	43690	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:53.744992971 CET	43690	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:53.745033026 CET	43690	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:53.864620924 CET	777	43690	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:53.864660025 CET	43690	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:53.984318972 CET	777	43690	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:55.048158884 CET	777	43690	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:55.048218966 CET	43690	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:55.048261881 CET	43690	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:55.182326078 CET	43692	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:55.302077055 CET	777	43692	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:55.302149057 CET	43692	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:55.302186966 CET	43692	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:55.421969891 CET	777	43692	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:55.422036886 CET	43692	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:55.541919947 CET	777	43692	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:56.727912903 CET	777	43692	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:56.728074074 CET	43692	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:56.847944975 CET	777	43692	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:57.851759911 CET	43694	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:57.971400976 CET	777	43694	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:57.971496105 CET	43694	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:57.971497059 CET	43694	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:58.091187000 CET	777	43694	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:58.091242075 CET	43694	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:58.211071968 CET	777	43694	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:59.305591106 CET	777	43694	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:59.305676937 CET	43694	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:59.305763960 CET	43694	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:59.428564072 CET	43696	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:59.548675060 CET	777	43696	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:59.548744917 CET	43696	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:59.548788071 CET	43696	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:59.668401003 CET	777	43696	154.216.19.138	192.168.2.23
Dec 22, 2024 12:58:59.668453932 CET	43696	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:58:59.788140059 CET	777	43696	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:00.865864992 CET	777	43696	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:00.865972042 CET	43696	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:00.865972996 CET	43696	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:00.999947071 CET	43698	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:01.119666100 CET	777	43698	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:01.119731903 CET	43698	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:01.119777918 CET	43698	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:01.239414930 CET	777	43698	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:01.239490032 CET	43698	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:01.359294891 CET	777	43698	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:02.458256960 CET	777	43698	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:02.458345890 CET	43698	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:02.458345890 CET	43698	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:02.581046104 CET	43700	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:02.700726032 CET	777	43700	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:02.700896978 CET	43700	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:02.700896978 CET	43700	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:02.820645094 CET	777	43700	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:02.820718050 CET	43700	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:02.940445900 CET	777	43700	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:04.000556946 CET	777	43700	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:04.000699997 CET	43700	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:04.000744104 CET	43700	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:04.135936022 CET	43702	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:04.256577015 CET	777	43702	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:04.256637096 CET	43702	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:04.256697893 CET	43702	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:04.376265049 CET	777	43702	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:04.376358032 CET	43702	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:04.497668028 CET	777	43702	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:05.564507961 CET	777	43702	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:05.564582109 CET	43702	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:05.564672947 CET	43702	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:05.687374115 CET	43704	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:05.807143927 CET	777	43704	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:05.807198048 CET	43704	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:05.807219028 CET	43704	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:05.926841974 CET	777	43704	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:05.926898956 CET	43704	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:06.046768904 CET	777	43704	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:07.107101917 CET	777	43704	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:07.107155085 CET	43704	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:07.107196093 CET	43704	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:07.241137981 CET	43706	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:07.360734940 CET	777	43706	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:07.360794067 CET	43706	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:07.360816002 CET	43706	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:07.481415987 CET	777	43706	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:07.481471062 CET	43706	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:07.601178885 CET	777	43706	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:08.662353039 CET	777	43706	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:08.662475109 CET	43706	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:08.662496090 CET	43706	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:08.797221899 CET	43708	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:08.916959047 CET	777	43708	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:08.917021990 CET	43708	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:08.917081118 CET	43708	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:09.036684036 CET	777	43708	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:09.036751032 CET	43708	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:09.156505108 CET	777	43708	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:10.220077038 CET	777	43708	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:10.220155954 CET	43708	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:10.220247030 CET	43708	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:10.342953920 CET	43710	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:10.462587118 CET	777	43710	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:10.462657928 CET	43710	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:10.462719917 CET	43710	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:10.582339048 CET	777	43710	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:10.582401037 CET	43710	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:10.702039003 CET	777	43710	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:11.763096094 CET	777	43710	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:11.763158083 CET	43710	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:11.763206959 CET	43710	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:11.885948896 CET	43712	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:12.006094933 CET	777	43712	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:12.006181955 CET	43712	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:12.006220102 CET	43712	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:12.126110077 CET	777	43712	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:12.126194000 CET	43712	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:12.246073008 CET	777	43712	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:13.306540966 CET	777	43712	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:13.306626081 CET	43712	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:13.306708097 CET	43712	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:13.442095041 CET	43714	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:13.562149048 CET	777	43714	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:13.562231064 CET	43714	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:13.562305927 CET	43714	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:13.681981087 CET	777	43714	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:13.682046890 CET	43714	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:13.801712036 CET	777	43714	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:14.863198996 CET	777	43714	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:14.863308907 CET	43714	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:14.863431931 CET	43714	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:14.986073971 CET	43716	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:15.106014967 CET	777	43716	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:15.106128931 CET	43716	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:15.106194019 CET	43716	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:15.225817919 CET	777	43716	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:15.225894928 CET	43716	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:15.345684052 CET	777	43716	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:16.412986040 CET	777	43716	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:16.413068056 CET	43716	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:16.413176060 CET	43716	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:16.548171043 CET	43718	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:16.670200109 CET	777	43718	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:16.670269966 CET	43718	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:16.670325994 CET	43718	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:16.790431023 CET	777	43718	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:16.790494919 CET	43718	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:16.910154104 CET	777	43718	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:17.970994949 CET	777	43718	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:17.971060038 CET	43718	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:17.971106052 CET	43718	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:18.093765020 CET	43720	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:18.213464022 CET	777	43720	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:18.213531017 CET	43720	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:18.213573933 CET	43720	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:18.333141088 CET	777	43720	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:18.333215952 CET	43720	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:18.452922106 CET	777	43720	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:19.514518023 CET	777	43720	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:19.514595985 CET	43720	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:19.514643908 CET	43720	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:19.649261951 CET	43722	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:19.769018888 CET	777	43722	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:19.769088984 CET	43722	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:19.769143105 CET	43722	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:19.888662100 CET	777	43722	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:19.888731003 CET	43722	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:20.008280039 CET	777	43722	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:21.067873001 CET	777	43722	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:21.067945004 CET	43722	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:21.067989111 CET	43722	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:21.202898026 CET	43724	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:21.322518110 CET	777	43724	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:21.322571039 CET	43724	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:21.322607040 CET	43724	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:21.442471981 CET	777	43724	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:21.442523956 CET	43724	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:21.562082052 CET	777	43724	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:22.624142885 CET	777	43724	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:22.624206066 CET	43724	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:22.624245882 CET	43724	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:22.747173071 CET	43726	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:22.868175030 CET	777	43726	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:22.868232012 CET	43726	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:22.868263960 CET	43726	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:22.987973928 CET	777	43726	154.216.19.138	192.168.2.23
Dec 22, 2024 12:59:22.988046885 CET	43726	777	192.168.2.23	154.216.19.138
Dec 22, 2024 12:59:23.107841015 CET	777	43726	154.216.19.138	192.168.2.23

UDP Packets

Timestamp	Source Port	Dest Port	Source IP	Dest IP
Dec 22, 2024 12:56:53.617120028 CET	55372	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:56:54.192687035 CET	53	55372	8.8.8.8	192.168.2.23
Dec 22, 2024 12:56:55.609265089 CET	34991	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:56:56.566914082 CET	53	34991	8.8.8.8	192.168.2.23
Dec 22, 2024 12:56:57.986686945 CET	36387	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:56:58.941606045 CET	53	36387	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:00.361735106 CET	38192	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:00.495929956 CET	53	38192	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:00.588363886 CET	38533	53	192.168.2.23	1.1.1.1
Dec 22, 2024 12:57:00.588434935 CET	34592	53	192.168.2.23	1.1.1.1
Dec 22, 2024 12:57:00.812573910 CET	53	38533	1.1.1.1	192.168.2.23
Dec 22, 2024 12:57:00.816821098 CET	53	34592	1.1.1.1	192.168.2.23
Dec 22, 2024 12:57:01.915487051 CET	46020	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:02.051547050 CET	53	46020	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:03.472079992 CET	53540	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:03.607150078 CET	53	53540	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:05.138933897 CET	51655	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:05.175071001 CET	60314	53	192.168.2.23	1.1.1.1
Dec 22, 2024 12:57:05.321954966 CET	53	60314	1.1.1.1	192.168.2.23
Dec 22, 2024 12:57:05.972281933 CET	53	51655	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:07.394809961 CET	34145	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:08.352433920 CET	53	34145	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:08.921649933 CET	44144	53	192.168.2.23	1.1.1.1
Dec 22, 2024 12:57:09.059181929 CET	53	44144	1.1.1.1	192.168.2.23
Dec 22, 2024 12:57:09.778460979 CET	54921	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:09.912913084 CET	53	54921	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:11.332317114 CET	57842	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:11.466269970 CET	53	57842	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:12.888102055 CET	44452	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:13.022588968 CET	53	44452	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:14.440185070 CET	44466	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:14.574829102 CET	53	44466	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:15.993235111 CET	58197	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:16.532799959 CET	53	58197	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:17.234812975 CET	57646	53	192.168.2.23	1.1.1.1
Dec 22, 2024 12:57:17.373003006 CET	53	57646	1.1.1.1	192.168.2.23
Dec 22, 2024 12:57:17.951045036 CET	33562	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:18.084815979 CET	53	33562	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:19.511898041 CET	46308	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:19.645808935 CET	53	46308	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:21.068120003 CET	36523	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:21.201889038 CET	53	36523	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:22.619961977 CET	50115	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:22.753783941 CET	53	50115	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:24.175621986 CET	60001	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:24.310165882 CET	53	60001	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:25.731044054 CET	49583	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:25.864862919 CET	53	49583	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:27.285679102 CET	41721	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:27.420017958 CET	53	41721	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:28.843513012 CET	59007	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:28.978436947 CET	53	59007	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:30.397485018 CET	35450	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:30.531137943 CET	53	35450	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:31.948295116 CET	54253	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:32.082087040 CET	53	54253	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:33.504858017 CET	49737	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:33.638767004 CET	53	49737	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:35.061136961 CET	35896	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:35.184556007 CET	53	35896	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:36.610032082 CET	55200	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:36.743937969 CET	53	55200	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:38.184570074 CET	57541	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:38.318785906 CET	53	57541	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:39.734548092 CET	57653	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:39.868522882 CET	53	57653	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:41.290792942 CET	56002	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:41.424583912 CET	53	56002	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:42.844728947 CET	42140	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:42.978635073 CET	53	42140	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:44.397875071 CET	41246	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:44.532047987 CET	53	41246	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:45.953289986 CET	48867	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:46.087915897 CET	53	48867	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:48.619584084 CET	60911	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:48.754170895 CET	53	60911	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:50.170195103 CET	56524	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:50.304192066 CET	53	56524	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:51.726036072 CET	45731	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:51.848874092 CET	53	45731	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:53.269788027 CET	47500	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:54.225816965 CET	53	47500	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:55.641818047 CET	49465	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:55.776293993 CET	53	49465	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:57.212730885 CET	54450	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:57.347141981 CET	53	54450	8.8.8.8	192.168.2.23
Dec 22, 2024 12:57:58.766159058 CET	45284	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:57:58.900172949 CET	53	45284	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:00.321182966 CET	46505	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:00.455008030 CET	53	46505	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:01.874814034 CET	41812	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:02.009295940 CET	53	41812	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:03.431428909 CET	53222	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:03.565352917 CET	53	53222	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:04.998657942 CET	44689	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:05.121424913 CET	53	44689	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:07.674633980 CET	56190	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:07.812072992 CET	53	56190	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:09.229252100 CET	50846	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:09.362950087 CET	53	50846	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:10.781924009 CET	55400	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:10.917558908 CET	53	55400	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:12.340010881 CET	45338	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:12.474458933 CET	53	45338	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:13.903465986 CET	41808	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:14.037341118 CET	53	41808	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:15.477355957 CET	51564	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:15.716126919 CET	53	51564	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:17.140619040 CET	42478	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:17.275352955 CET	53	42478	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:18.694866896 CET	35415	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:18.828732967 CET	53	35415	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:20.246462107 CET	59736	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:20.380945921 CET	53	59736	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:21.800654888 CET	41907	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:21.934330940 CET	53	41907	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:23.354573011 CET	59268	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:23.488655090 CET	53	59268	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:24.908720970 CET	38933	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:25.031481028 CET	53	38933	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:26.452946901 CET	57617	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:26.588021040 CET	53	57617	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:29.121037960 CET	49749	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:29.243762970 CET	53	49749	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:30.663808107 CET	50487	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:30.786417961 CET	53	50487	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:32.208981991 CET	59813	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:32.343012094 CET	53	59813	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:33.766097069 CET	51105	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:33.888952971 CET	53	51105	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:35.311575890 CET	39332	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:35.434093952 CET	53	39332	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:36.855221033 CET	37824	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:36.989537954 CET	53	37824	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:38.410655975 CET	57588	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:38.544842958 CET	53	57588	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:39.963541985 CET	41258	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:40.085972071 CET	53	41258	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:41.519325972 CET	33732	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:41.653435946 CET	53	33732	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:43.073453903 CET	35476	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:43.196656942 CET	53	35476	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:45.736594915 CET	42513	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:45.859558105 CET	53	42513	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:47.279155970 CET	48497	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:47.413167000 CET	53	48497	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:48.847569942 CET	59586	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:48.970316887 CET	53	59586	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:50.391930103 CET	43557	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:50.526571989 CET	53	43557	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:51.948462963 CET	55670	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:52.070997953 CET	53	55670	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:53.490667105 CET	53967	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:53.625080109 CET	53	53967	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:55.048294067 CET	33549	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:55.182219982 CET	53	33549	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:57.728899956 CET	41167	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:57.851665020 CET	53	41167	8.8.8.8	192.168.2.23
Dec 22, 2024 12:58:59.305811882 CET	35046	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:58:59.428450108 CET	53	35046	8.8.8.8	192.168.2.23
Dec 22, 2024 12:59:00.866019964 CET	60960	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:59:00.999838114 CET	53	60960	8.8.8.8	192.168.2.23
Dec 22, 2024 12:59:02.458395958 CET	35950	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:59:02.580897093 CET	53	35950	8.8.8.8	192.168.2.23
Dec 22, 2024 12:59:04.000792980 CET	51203	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:59:04.135732889 CET	53	51203	8.8.8.8	192.168.2.23
Dec 22, 2024 12:59:05.564735889 CET	48625	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:59:05.687232971 CET	53	48625	8.8.8.8	192.168.2.23
Dec 22, 2024 12:59:07.107273102 CET	33263	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:59:07.241030931 CET	53	33263	8.8.8.8	192.168.2.23
Dec 22, 2024 12:59:08.662549019 CET	32846	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:59:08.797115088 CET	53	32846	8.8.8.8	192.168.2.23
Dec 22, 2024 12:59:10.220225096 CET	40879	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:59:10.342869997 CET	53	40879	8.8.8.8	192.168.2.23
Dec 22, 2024 12:59:11.763262987 CET	40864	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:59:11.885828018 CET	53	40864	8.8.8.8	192.168.2.23
Dec 22, 2024 12:59:13.306709051 CET	53701	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:59:13.441963911 CET	53	53701	8.8.8.8	192.168.2.23
Dec 22, 2024 12:59:14.863431931 CET	39486	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:59:14.985954046 CET	53	39486	8.8.8.8	192.168.2.23
Dec 22, 2024 12:59:16.413145065 CET	39993	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:59:16.548046112 CET	53	39993	8.8.8.8	192.168.2.23
Dec 22, 2024 12:59:17.971131086 CET	47568	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:59:18.093660116 CET	53	47568	8.8.8.8	192.168.2.23
Dec 22, 2024 12:59:19.514733076 CET	39241	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:59:19.649121046 CET	53	39241	8.8.8.8	192.168.2.23
Dec 22, 2024 12:59:21.068073034 CET	54995	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:59:21.202806950 CET	53	54995	8.8.8.8	192.168.2.23
Dec 22, 2024 12:59:22.624280930 CET	36046	53	192.168.2.23	8.8.8.8
Dec 22, 2024 12:59:22.747097969 CET	53	36046	8.8.8.8	192.168.2.23

ICMP Packets

Timestamp	Source IP	Dest IP	Checksum	Code	Type
Dec 22, 2024 12:57:02.692475080 CET	192.168.2.23	192.168.2.1	8283	(Port unreachable)	Destination Unreachable
Dec 22, 2024 12:58:22.708336115 CET	192.168.2.23	192.168.2.1	8283	(Port unreachable)	Destination Unreachable

DNS Queries

Timestamp	Source IP	Dest IP	Trans ID	OP Code	Name	Type	Class	DNS over HTTPS
Dec 22, 2024 12:56:53.617120028 CET	192.168.2.23	8.8.8.8	0xe89d	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:56:55.609265089 CET	192.168.2.23	8.8.8.8	0xec8f	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:56:57.986686945 CET	192.168.2.23	8.8.8.8	0xd765	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:00.361735106 CET	192.168.2.23	8.8.8.8	0xc2ec	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:00.588363886 CET	192.168.2.23	1.1.1.1	0xe386	Standard query (0)	daisy.ubuntu.com	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:00.588434935 CET	192.168.2.23	1.1.1.1	0x90b4	Standard query (0)	daisy.ubuntu.com	28	IN (0x0001)	false
Dec 22, 2024 12:57:01.915487051 CET	192.168.2.23	8.8.8.8	0x59a6	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:03.472079992 CET	192.168.2.23	8.8.8.8	0xd706	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:05.138933897 CET	192.168.2.23	8.8.8.8	0x9144	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:05.175071001 CET	192.168.2.23	1.1.1.1	0x219a	Standard query (0)	daisy.ubuntu.com	28	IN (0x0001)	false
Dec 22, 2024 12:57:07.394809961 CET	192.168.2.23	8.8.8.8	0x6814	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:08.921649933 CET	192.168.2.23	1.1.1.1	0x4b23	Standard query (0)	daisy.ubuntu.com	28	IN (0x0001)	false
Dec 22, 2024 12:57:09.778460979 CET	192.168.2.23	8.8.8.8	0xd20c	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:11.332317114 CET	192.168.2.23	8.8.8.8	0x60d4	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:12.888102055 CET	192.168.2.23	8.8.8.8	0x4a93	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:14.440185070 CET	192.168.2.23	8.8.8.8	0x2188	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:15.993235111 CET	192.168.2.23	8.8.8.8	0x8e8c	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:17.234812975 CET	192.168.2.23	1.1.1.1	0x9e9f	Standard query (0)	daisy.ubuntu.com	28	IN (0x0001)	false
Dec 22, 2024 12:57:17.951045036 CET	192.168.2.23	8.8.8.8	0xb721	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:19.511898041 CET	192.168.2.23	8.8.8.8	0xc53	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:21.068120003 CET	192.168.2.23	8.8.8.8	0x9c1c	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:22.619961977 CET	192.168.2.23	8.8.8.8	0xc1fe	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:24.175621986 CET	192.168.2.23	8.8.8.8	0x784b	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:25.731044054 CET	192.168.2.23	8.8.8.8	0x9d4f	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:27.285679102 CET	192.168.2.23	8.8.8.8	0xaf0a	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:28.843513012 CET	192.168.2.23	8.8.8.8	0xabfc	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:30.397485018 CET	192.168.2.23	8.8.8.8	0xe4ef	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:31.948295116 CET	192.168.2.23	8.8.8.8	0x782d	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:33.504858017 CET	192.168.2.23	8.8.8.8	0x2c1c	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:35.061136961 CET	192.168.2.23	8.8.8.8	0xba17	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:36.610032082 CET	192.168.2.23	8.8.8.8	0x574f	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:38.184570074 CET	192.168.2.23	8.8.8.8	0x1c65	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:39.734548092 CET	192.168.2.23	8.8.8.8	0x8536	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:41.290792942 CET	192.168.2.23	8.8.8.8	0x7b34	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:42.844728947 CET	192.168.2.23	8.8.8.8	0x720d	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:44.397875071 CET	192.168.2.23	8.8.8.8	0xf5e4	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:45.953289986 CET	192.168.2.23	8.8.8.8	0xa6e0	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:48.619584084 CET	192.168.2.23	8.8.8.8	0x954b	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:50.170195103 CET	192.168.2.23	8.8.8.8	0xea39	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:51.726036072 CET	192.168.2.23	8.8.8.8	0x8be	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:53.269788027 CET	192.168.2.23	8.8.8.8	0xcca8	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:55.641818047 CET	192.168.2.23	8.8.8.8	0x652f	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:57.212730885 CET	192.168.2.23	8.8.8.8	0x1261	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:58.766159058 CET	192.168.2.23	8.8.8.8	0xedc2	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:00.321182966 CET	192.168.2.23	8.8.8.8	0x6d1b	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:01.874814034 CET	192.168.2.23	8.8.8.8	0x1a17	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:03.431428909 CET	192.168.2.23	8.8.8.8	0x4210	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:04.998657942 CET	192.168.2.23	8.8.8.8	0xd97b	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:07.674633980 CET	192.168.2.23	8.8.8.8	0x1ad7	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:09.229252100 CET	192.168.2.23	8.8.8.8	0xbd04	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:10.781924009 CET	192.168.2.23	8.8.8.8	0xcdce	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:12.340010881 CET	192.168.2.23	8.8.8.8	0x67bc	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:13.903465986 CET	192.168.2.23	8.8.8.8	0x64b2	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:15.477355957 CET	192.168.2.23	8.8.8.8	0xbf2a	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:17.140619040 CET	192.168.2.23	8.8.8.8	0xd4e8	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:18.694866896 CET	192.168.2.23	8.8.8.8	0x3902	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:20.246462107 CET	192.168.2.23	8.8.8.8	0xfeca	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:21.800654888 CET	192.168.2.23	8.8.8.8	0x46f0	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:23.354573011 CET	192.168.2.23	8.8.8.8	0x9b14	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:24.908720970 CET	192.168.2.23	8.8.8.8	0x519e	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:26.452946901 CET	192.168.2.23	8.8.8.8	0x8449	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:29.121037960 CET	192.168.2.23	8.8.8.8	0xfc	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:30.663808107 CET	192.168.2.23	8.8.8.8	0xb294	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:32.208981991 CET	192.168.2.23	8.8.8.8	0x8103	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:33.766097069 CET	192.168.2.23	8.8.8.8	0xcac3	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:35.311575890 CET	192.168.2.23	8.8.8.8	0xa7a4	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:36.855221033 CET	192.168.2.23	8.8.8.8	0x25c3	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:38.410655975 CET	192.168.2.23	8.8.8.8	0xcce9	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:39.963541985 CET	192.168.2.23	8.8.8.8	0x7d24	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:41.519325972 CET	192.168.2.23	8.8.8.8	0x5f73	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:43.073453903 CET	192.168.2.23	8.8.8.8	0x4708	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:45.736594915 CET	192.168.2.23	8.8.8.8	0x8211	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:47.279155970 CET	192.168.2.23	8.8.8.8	0x7948	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:48.847569942 CET	192.168.2.23	8.8.8.8	0x84bf	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:50.391930103 CET	192.168.2.23	8.8.8.8	0x98a9	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:51.948462963 CET	192.168.2.23	8.8.8.8	0x732f	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:53.490667105 CET	192.168.2.23	8.8.8.8	0xb1c7	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:55.048294067 CET	192.168.2.23	8.8.8.8	0xdfa5	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:57.728899956 CET	192.168.2.23	8.8.8.8	0x169e	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:59.305811882 CET	192.168.2.23	8.8.8.8	0x8e52	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:00.866019964 CET	192.168.2.23	8.8.8.8	0xdef6	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:02.458395958 CET	192.168.2.23	8.8.8.8	0xb6e5	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:04.000792980 CET	192.168.2.23	8.8.8.8	0xffd6	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:05.564735889 CET	192.168.2.23	8.8.8.8	0xdcc4	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:07.107273102 CET	192.168.2.23	8.8.8.8	0x5864	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:08.662549019 CET	192.168.2.23	8.8.8.8	0xf2d5	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:10.220225096 CET	192.168.2.23	8.8.8.8	0xda3	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:11.763262987 CET	192.168.2.23	8.8.8.8	0x89be	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:13.306709051 CET	192.168.2.23	8.8.8.8	0xa6a4	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:14.863431931 CET	192.168.2.23	8.8.8.8	0x3cd1	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:16.413145065 CET	192.168.2.23	8.8.8.8	0xf793	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:17.971131086 CET	192.168.2.23	8.8.8.8	0xae4b	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:19.514733076 CET	192.168.2.23	8.8.8.8	0x83b3	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:21.068073034 CET	192.168.2.23	8.8.8.8	0x2c07	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:22.624280930 CET	192.168.2.23	8.8.8.8	0x689d	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false

DNS Answers

Timestamp	Source IP	Dest IP	Trans ID	Reply Code	Name	Address	Type	Class	DNS over HTTPS
Dec 22, 2024 12:56:54.192687035 CET	8.8.8.8	192.168.2.23	0xe89d	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:56:56.566914082 CET	8.8.8.8	192.168.2.23	0xec8f	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:56:58.941606045 CET	8.8.8.8	192.168.2.23	0xd765	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:00.495929956 CET	8.8.8.8	192.168.2.23	0xc2ec	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:00.812573910 CET	1.1.1.1	192.168.2.23	0xe386	No error (0)	daisy.ubuntu.com	162.213.35.25	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:00.812573910 CET	1.1.1.1	192.168.2.23	0xe386	No error (0)	daisy.ubuntu.com	162.213.35.24	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:02.051547050 CET	8.8.8.8	192.168.2.23	0x59a6	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:03.607150078 CET	8.8.8.8	192.168.2.23	0xd706	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:05.972281933 CET	8.8.8.8	192.168.2.23	0x9144	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:08.352433920 CET	8.8.8.8	192.168.2.23	0x6814	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:09.912913084 CET	8.8.8.8	192.168.2.23	0xd20c	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:11.466269970 CET	8.8.8.8	192.168.2.23	0x60d4	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:13.022588968 CET	8.8.8.8	192.168.2.23	0x4a93	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:14.574829102 CET	8.8.8.8	192.168.2.23	0x2188	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:16.532799959 CET	8.8.8.8	192.168.2.23	0x8e8c	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:18.084815979 CET	8.8.8.8	192.168.2.23	0xb721	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:19.645808935 CET	8.8.8.8	192.168.2.23	0xc53	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:21.201889038 CET	8.8.8.8	192.168.2.23	0x9c1c	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:22.753783941 CET	8.8.8.8	192.168.2.23	0xc1fe	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:24.310165882 CET	8.8.8.8	192.168.2.23	0x784b	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:25.864862919 CET	8.8.8.8	192.168.2.23	0x9d4f	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:27.420017958 CET	8.8.8.8	192.168.2.23	0xaf0a	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:28.978436947 CET	8.8.8.8	192.168.2.23	0xabfc	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:30.531137943 CET	8.8.8.8	192.168.2.23	0xe4ef	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:32.082087040 CET	8.8.8.8	192.168.2.23	0x782d	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:33.638767004 CET	8.8.8.8	192.168.2.23	0x2c1c	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:35.184556007 CET	8.8.8.8	192.168.2.23	0xba17	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:36.743937969 CET	8.8.8.8	192.168.2.23	0x574f	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:38.318785906 CET	8.8.8.8	192.168.2.23	0x1c65	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:39.868522882 CET	8.8.8.8	192.168.2.23	0x8536	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:41.424583912 CET	8.8.8.8	192.168.2.23	0x7b34	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:42.978635073 CET	8.8.8.8	192.168.2.23	0x720d	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:44.532047987 CET	8.8.8.8	192.168.2.23	0xf5e4	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:46.087915897 CET	8.8.8.8	192.168.2.23	0xa6e0	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:48.754170895 CET	8.8.8.8	192.168.2.23	0x954b	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:50.304192066 CET	8.8.8.8	192.168.2.23	0xea39	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:51.848874092 CET	8.8.8.8	192.168.2.23	0x8be	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:54.225816965 CET	8.8.8.8	192.168.2.23	0xcca8	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:55.776293993 CET	8.8.8.8	192.168.2.23	0x652f	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:57.347141981 CET	8.8.8.8	192.168.2.23	0x1261	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:57:58.900172949 CET	8.8.8.8	192.168.2.23	0xedc2	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:00.455008030 CET	8.8.8.8	192.168.2.23	0x6d1b	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:02.009295940 CET	8.8.8.8	192.168.2.23	0x1a17	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:03.565352917 CET	8.8.8.8	192.168.2.23	0x4210	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:05.121424913 CET	8.8.8.8	192.168.2.23	0xd97b	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:07.812072992 CET	8.8.8.8	192.168.2.23	0x1ad7	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:09.362950087 CET	8.8.8.8	192.168.2.23	0xbd04	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:10.917558908 CET	8.8.8.8	192.168.2.23	0xcdce	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:12.474458933 CET	8.8.8.8	192.168.2.23	0x67bc	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:14.037341118 CET	8.8.8.8	192.168.2.23	0x64b2	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:15.716126919 CET	8.8.8.8	192.168.2.23	0xbf2a	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:17.275352955 CET	8.8.8.8	192.168.2.23	0xd4e8	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:18.828732967 CET	8.8.8.8	192.168.2.23	0x3902	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:20.380945921 CET	8.8.8.8	192.168.2.23	0xfeca	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:21.934330940 CET	8.8.8.8	192.168.2.23	0x46f0	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:23.488655090 CET	8.8.8.8	192.168.2.23	0x9b14	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:25.031481028 CET	8.8.8.8	192.168.2.23	0x519e	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:26.588021040 CET	8.8.8.8	192.168.2.23	0x8449	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:29.243762970 CET	8.8.8.8	192.168.2.23	0xfc	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:30.786417961 CET	8.8.8.8	192.168.2.23	0xb294	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:32.343012094 CET	8.8.8.8	192.168.2.23	0x8103	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:33.888952971 CET	8.8.8.8	192.168.2.23	0xcac3	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:35.434093952 CET	8.8.8.8	192.168.2.23	0xa7a4	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:36.989537954 CET	8.8.8.8	192.168.2.23	0x25c3	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:38.544842958 CET	8.8.8.8	192.168.2.23	0xcce9	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:40.085972071 CET	8.8.8.8	192.168.2.23	0x7d24	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:41.653435946 CET	8.8.8.8	192.168.2.23	0x5f73	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:43.196656942 CET	8.8.8.8	192.168.2.23	0x4708	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:45.859558105 CET	8.8.8.8	192.168.2.23	0x8211	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:47.413167000 CET	8.8.8.8	192.168.2.23	0x7948	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:48.970316887 CET	8.8.8.8	192.168.2.23	0x84bf	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:50.526571989 CET	8.8.8.8	192.168.2.23	0x98a9	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:52.070997953 CET	8.8.8.8	192.168.2.23	0x732f	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:53.625080109 CET	8.8.8.8	192.168.2.23	0xb1c7	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:55.182219982 CET	8.8.8.8	192.168.2.23	0xdfa5	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:57.851665020 CET	8.8.8.8	192.168.2.23	0x169e	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:58:59.428450108 CET	8.8.8.8	192.168.2.23	0x8e52	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:00.999838114 CET	8.8.8.8	192.168.2.23	0xdef6	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:02.580897093 CET	8.8.8.8	192.168.2.23	0xb6e5	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:04.135732889 CET	8.8.8.8	192.168.2.23	0xffd6	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:05.687232971 CET	8.8.8.8	192.168.2.23	0xdcc4	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:07.241030931 CET	8.8.8.8	192.168.2.23	0x5864	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:08.797115088 CET	8.8.8.8	192.168.2.23	0xf2d5	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:10.342869997 CET	8.8.8.8	192.168.2.23	0xda3	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:11.885828018 CET	8.8.8.8	192.168.2.23	0x89be	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:13.441963911 CET	8.8.8.8	192.168.2.23	0xa6a4	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:14.985954046 CET	8.8.8.8	192.168.2.23	0x3cd1	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:16.548046112 CET	8.8.8.8	192.168.2.23	0xf793	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:18.093660116 CET	8.8.8.8	192.168.2.23	0xae4b	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:19.649121046 CET	8.8.8.8	192.168.2.23	0x83b3	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:21.202806950 CET	8.8.8.8	192.168.2.23	0x2c07	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false
Dec 22, 2024 12:59:22.747097969 CET	8.8.8.8	192.168.2.23	0x689d	No error (0)	vbtgsze.r-e.kr	154.216.19.138	A (IP address)	IN (0x0001)	false

System Behavior

Analysis Process: byte.x86.elf PID: 6237, Parent PID: 6163

General

Start time (UTC):	11:56:53
Start date (UTC):	22/12/2024
Path:	/tmp/byte.x86.elf
Arguments:	/tmp/byte.x86.elf
File size:	37816 bytes
MD5 hash:	7f450c92cd48f89e76cc42545287a95c

Chronological Activities

Analysis Process: byte.x86.elf PID: 6238, Parent PID: 6237

General

Start time (UTC):	11:56:53
Start date (UTC):	22/12/2024
Path:	/tmp/byte.x86.elf
Arguments:	-
File size:	37816 bytes
MD5 hash:	7f450c92cd48f89e76cc42545287a95c

Chronological Activities

Analysis Process: byte.x86.elf PID: 6239, Parent PID: 6237

General

Start time (UTC):	11:56:53
Start date (UTC):	22/12/2024
Path:	/tmp/byte.x86.elf
Arguments:	-
File size:	37816 bytes
MD5 hash:	7f450c92cd48f89e76cc42545287a95c

Chronological Activities

Analysis Process: byte.x86.elf PID: 6240, Parent PID: 6237

General

Start time (UTC):	11:56:53
Start date (UTC):	22/12/2024
Path:	/tmp/byte.x86.elf
Arguments:	-
File size:	37816 bytes
MD5 hash:	7f450c92cd48f89e76cc42545287a95c

Chronological Activities

Analysis Process: byte.x86.elf PID: 6241, Parent PID: 6240

General

Start time (UTC):	11:56:53
Start date (UTC):	22/12/2024
Path:	/tmp/byte.x86.elf
Arguments:	-
File size:	37816 bytes
MD5 hash:	7f450c92cd48f89e76cc42545287a95c

Chronological Activities

Analysis Process: byte.x86.elf PID: 6242, Parent PID: 6240

General

Start time (UTC):	11:56:53
Start date (UTC):	22/12/2024
Path:	/tmp/byte.x86.elf
Arguments:	-
File size:	37816 bytes
MD5 hash:	7f450c92cd48f89e76cc42545287a95c

Chronological Activities

Analysis Process: systemd PID: 6279, Parent PID: 1

General

Start time (UTC):	11:56:54
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: dbus-daemon PID: 6279, Parent PID: 1

General

Start time (UTC):	11:56:54
Start date (UTC):	22/12/2024
Path:	/usr/bin/dbus-daemon
Arguments:	/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
File size:	249032 bytes
MD5 hash:	3089d47e3f3ab84cd81c48fd406d7a8c

Chronological Activities

Analysis Process: systemd PID: 6280, Parent PID: 1

General

Start time (UTC):	11:56:54
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rsyslogd PID: 6280, Parent PID: 1

General

Start time (UTC):	11:56:54
Start date (UTC):	22/12/2024
Path:	/usr/sbin/rsyslogd
Arguments:	/usr/sbin/rsyslogd -n -iNONE
File size:	727248 bytes
MD5 hash:	0b8087fc907c42eb3c81a691db258e33

Chronological Activities

Analysis Process: systemd PID: 6281, Parent PID: 1860

General

Start time (UTC):	11:56:54
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: pulseaudio PID: 6281, Parent PID: 1860

General

Start time (UTC):	11:56:54
Start date (UTC):	22/12/2024
Path:	/usr/bin/pulseaudio
Arguments:	/usr/bin/pulseaudio --daemonize=no --log-target=journal
File size:	100832 bytes
MD5 hash:	0c3b4c789d8ffb12b25507f27e14c186

Chronological Activities

Analysis Process: gvfsd-fuse PID: 6282, Parent PID: 2038

General

Start time (UTC):	11:56:54
Start date (UTC):	22/12/2024
Path:	/usr/libexec/gvfsd-fuse
Arguments:	-
File size:	47632 bytes
MD5 hash:	d18fbf1cbf8eb57b17fac48b7b4be933

Chronological Activities

Analysis Process: fusermount PID: 6282, Parent PID: 2038

General

Start time (UTC):	11:56:54
Start date (UTC):	22/12/2024
Path:	/bin/fusermount
Arguments:	fusermount -u -q -z -- /run/user/1000/gvfs
File size:	39144 bytes
MD5 hash:	576a1b135c82bdcbc97a91acea900566

Chronological Activities

Analysis Process: systemd PID: 6291, Parent PID: 1

General

Start time (UTC):	11:56:55
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: dbus-daemon PID: 6291, Parent PID: 1

General

Start time (UTC):	11:56:55
Start date (UTC):	22/12/2024
Path:	/usr/bin/dbus-daemon
Arguments:	/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
File size:	249032 bytes
MD5 hash:	3089d47e3f3ab84cd81c48fd406d7a8c

Chronological Activities

Analysis Process: systemd PID: 6292, Parent PID: 1

General

Start time (UTC):	11:56:56
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rsyslogd PID: 6292, Parent PID: 1

General

Start time (UTC):	11:56:56
Start date (UTC):	22/12/2024
Path:	/usr/sbin/rsyslogd
Arguments:	/usr/sbin/rsyslogd -n -iNONE
File size:	727248 bytes
MD5 hash:	0b8087fc907c42eb3c81a691db258e33

Chronological Activities

Analysis Process: systemd PID: 6294, Parent PID: 1860

General

Start time (UTC):	11:56:56
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: pulseaudio PID: 6294, Parent PID: 1860

General

Start time (UTC):	11:56:56
Start date (UTC):	22/12/2024
Path:	/usr/bin/pulseaudio
Arguments:	/usr/bin/pulseaudio --daemonize=no --log-target=journal
File size:	100832 bytes
MD5 hash:	0c3b4c789d8ffb12b25507f27e14c186

Chronological Activities

Analysis Process: systemd PID: 6304, Parent PID: 1

General

Start time (UTC):	11:56:58
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: systemd-logind PID: 6304, Parent PID: 1

General

Start time (UTC):	11:56:58
Start date (UTC):	22/12/2024
Path:	/lib/systemd/systemd-logind
Arguments:	/lib/systemd/systemd-logind
File size:	268576 bytes
MD5 hash:	8dd58a1b4c12f7a1d5fe3ce18b2aaeef

Chronological Activities

Analysis Process: systemd PID: 6361, Parent PID: 1

General

Start time (UTC):	11:56:58
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rtkit-daemon PID: 6361, Parent PID: 1

General

Start time (UTC):	11:56:58
Start date (UTC):	22/12/2024
Path:	/usr/libexec/rtkit-daemon
Arguments:	/usr/libexec/rtkit-daemon
File size:	68096 bytes
MD5 hash:	df0cacf1db4ec95ac70f5b6e06b8ffd7

Chronological Activities

Analysis Process: gdm3 PID: 6362, Parent PID: 1320

General

Start time (UTC):	11:56:58
Start date (UTC):	22/12/2024
Path:	/usr/sbin/gdm3
Arguments:	-
File size:	453296 bytes
MD5 hash:	2492e2d8d34f9377e3e530a61a15674f

Chronological Activities

Analysis Process: Default PID: 6362, Parent PID: 1320

General

Start time (UTC):	11:56:58
Start date (UTC):	22/12/2024
Path:	/etc/gdm3/PrimeOff/Default
Arguments:	/etc/gdm3/PrimeOff/Default
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: gdm3 PID: 6365, Parent PID: 1320

General

Start time (UTC):	11:56:59
Start date (UTC):	22/12/2024
Path:	/usr/sbin/gdm3
Arguments:	-
File size:	453296 bytes
MD5 hash:	2492e2d8d34f9377e3e530a61a15674f

Chronological Activities

Analysis Process: Default PID: 6365, Parent PID: 1320

General

Start time (UTC):	11:56:59
Start date (UTC):	22/12/2024
Path:	/etc/gdm3/PrimeOff/Default
Arguments:	/etc/gdm3/PrimeOff/Default
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: gdm3 PID: 6366, Parent PID: 1320

General

Start time (UTC):	11:56:59
Start date (UTC):	22/12/2024
Path:	/usr/sbin/gdm3
Arguments:	-
File size:	453296 bytes
MD5 hash:	2492e2d8d34f9377e3e530a61a15674f

Chronological Activities

Analysis Process: Default PID: 6366, Parent PID: 1320

General

Start time (UTC):	11:56:59
Start date (UTC):	22/12/2024
Path:	/etc/gdm3/PrimeOff/Default
Arguments:	/etc/gdm3/PrimeOff/Default
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: systemd PID: 6370, Parent PID: 1

General

Start time (UTC):	11:56:59
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: polkitd PID: 6370, Parent PID: 1

General

Start time (UTC):	11:56:59
Start date (UTC):	22/12/2024
Path:	/usr/lib/policykit-1/polkitd
Arguments:	/usr/lib/policykit-1/polkitd --no-debug
File size:	121504 bytes
MD5 hash:	8efc9b4b5b524210ad2ea1954a9d0e69

Chronological Activities

Analysis Process: systemd PID: 6375, Parent PID: 1

General

Start time (UTC):	11:57:00
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: dbus-daemon PID: 6375, Parent PID: 1

General

Start time (UTC):	11:57:00
Start date (UTC):	22/12/2024
Path:	/usr/bin/dbus-daemon
Arguments:	/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
File size:	249032 bytes
MD5 hash:	3089d47e3f3ab84cd81c48fd406d7a8c

Chronological Activities

Analysis Process: systemd PID: 6377, Parent PID: 1

General

Start time (UTC):	11:57:00
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: gpu-manager PID: 6377, Parent PID: 1

General

Start time (UTC):	11:57:00
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	/usr/bin/gpu-manager --log /var/log/gpu-manager.log
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: gpu-manager PID: 6381, Parent PID: 6377

General

Start time (UTC):	11:57:01
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	-
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: sh PID: 6381, Parent PID: 6377

General

Start time (UTC):	11:57:01
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	sh -c "grep -G \"^blacklist.nvidia[[:space:]]$\" /etc/modprobe.d/*.conf"
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: sh PID: 6382, Parent PID: 6381

General

Start time (UTC):	11:57:01
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	-
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: grep PID: 6382, Parent PID: 6381

General

Start time (UTC):	11:57:01
Start date (UTC):	22/12/2024
Path:	/usr/bin/grep
Arguments:	grep -G ^blacklist.nvidia[[:space:]]$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf
File size:	199136 bytes
MD5 hash:	1e6ebb9dd094f774478f72727bdba0f5

Chronological Activities

Analysis Process: gpu-manager PID: 6383, Parent PID: 6377

General

Start time (UTC):	11:57:01
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	-
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: sh PID: 6383, Parent PID: 6377

General

Start time (UTC):	11:57:01
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	sh -c "grep -G \"^blacklist.nvidia[[:space:]]$\" /lib/modprobe.d/*.conf"
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: sh PID: 6387, Parent PID: 6383

General

Start time (UTC):	11:57:01
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	-
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: grep PID: 6387, Parent PID: 6383

General

Start time (UTC):	11:57:01
Start date (UTC):	22/12/2024
Path:	/usr/bin/grep
Arguments:	grep -G ^blacklist.nvidia[[:space:]]$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf
File size:	199136 bytes
MD5 hash:	1e6ebb9dd094f774478f72727bdba0f5

Chronological Activities

Analysis Process: gpu-manager PID: 6388, Parent PID: 6377

General

Start time (UTC):	11:57:02
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	-
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: sh PID: 6388, Parent PID: 6377

General

Start time (UTC):	11:57:02
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	sh -c "grep -G \"^blacklist.radeon[[:space:]]$\" /etc/modprobe.d/*.conf"
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: sh PID: 6389, Parent PID: 6388

General

Start time (UTC):	11:57:02
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	-
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: grep PID: 6389, Parent PID: 6388

General

Start time (UTC):	11:57:02
Start date (UTC):	22/12/2024
Path:	/usr/bin/grep
Arguments:	grep -G ^blacklist.radeon[[:space:]]$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf
File size:	199136 bytes
MD5 hash:	1e6ebb9dd094f774478f72727bdba0f5

Chronological Activities

Analysis Process: gpu-manager PID: 6391, Parent PID: 6377

General

Start time (UTC):	11:57:03
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	-
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: sh PID: 6391, Parent PID: 6377

General

Start time (UTC):	11:57:03
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	sh -c "grep -G \"^blacklist.radeon[[:space:]]$\" /lib/modprobe.d/*.conf"
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: sh PID: 6392, Parent PID: 6391

General

Start time (UTC):	11:57:03
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	-
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: grep PID: 6392, Parent PID: 6391

General

Start time (UTC):	11:57:03
Start date (UTC):	22/12/2024
Path:	/usr/bin/grep
Arguments:	grep -G ^blacklist.radeon[[:space:]]$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf
File size:	199136 bytes
MD5 hash:	1e6ebb9dd094f774478f72727bdba0f5

Chronological Activities

Analysis Process: gpu-manager PID: 6395, Parent PID: 6377

General

Start time (UTC):	11:57:03
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	-
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: sh PID: 6395, Parent PID: 6377

General

Start time (UTC):	11:57:03
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	sh -c "grep -G \"^blacklist.amdgpu[[:space:]]$\" /etc/modprobe.d/*.conf"
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: sh PID: 6396, Parent PID: 6395

General

Start time (UTC):	11:57:04
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	-
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: grep PID: 6396, Parent PID: 6395

General

Start time (UTC):	11:57:04
Start date (UTC):	22/12/2024
Path:	/usr/bin/grep
Arguments:	grep -G ^blacklist.amdgpu[[:space:]]$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf
File size:	199136 bytes
MD5 hash:	1e6ebb9dd094f774478f72727bdba0f5

Chronological Activities

Analysis Process: gpu-manager PID: 6404, Parent PID: 6377

General

Start time (UTC):	11:57:04
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	-
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: sh PID: 6404, Parent PID: 6377

General

Start time (UTC):	11:57:04
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	sh -c "grep -G \"^blacklist.amdgpu[[:space:]]$\" /lib/modprobe.d/*.conf"
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: systemd PID: 6378, Parent PID: 1860

General

Start time (UTC):	11:57:00
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: pulseaudio PID: 6378, Parent PID: 1860

General

Start time (UTC):	11:57:00
Start date (UTC):	22/12/2024
Path:	/usr/bin/pulseaudio
Arguments:	/usr/bin/pulseaudio --daemonize=no --log-target=journal
File size:	100832 bytes
MD5 hash:	0c3b4c789d8ffb12b25507f27e14c186

Chronological Activities

Analysis Process: systemd PID: 6379, Parent PID: 1

General

Start time (UTC):	11:57:00
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rsyslogd PID: 6379, Parent PID: 1

General

Start time (UTC):	11:57:00
Start date (UTC):	22/12/2024
Path:	/usr/sbin/rsyslogd
Arguments:	/usr/sbin/rsyslogd -n -iNONE
File size:	727248 bytes
MD5 hash:	0b8087fc907c42eb3c81a691db258e33

Chronological Activities

Analysis Process: systemd PID: 6394, Parent PID: 1

General

Start time (UTC):	11:57:03
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rtkit-daemon PID: 6394, Parent PID: 1

General

Start time (UTC):	11:57:03
Start date (UTC):	22/12/2024
Path:	/usr/libexec/rtkit-daemon
Arguments:	/usr/libexec/rtkit-daemon
File size:	68096 bytes
MD5 hash:	df0cacf1db4ec95ac70f5b6e06b8ffd7

Chronological Activities

Analysis Process: systemd PID: 6402, Parent PID: 1

General

Start time (UTC):	11:57:04
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: polkitd PID: 6402, Parent PID: 1

General

Start time (UTC):	11:57:04
Start date (UTC):	22/12/2024
Path:	/usr/lib/policykit-1/polkitd
Arguments:	/usr/lib/policykit-1/polkitd --no-debug
File size:	121504 bytes
MD5 hash:	8efc9b4b5b524210ad2ea1954a9d0e69

Chronological Activities

Analysis Process: systemd PID: 6405, Parent PID: 1

General

Start time (UTC):	11:57:04
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: dbus-daemon PID: 6405, Parent PID: 1

General

Start time (UTC):	11:57:04
Start date (UTC):	22/12/2024
Path:	/usr/bin/dbus-daemon
Arguments:	/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
File size:	249032 bytes
MD5 hash:	3089d47e3f3ab84cd81c48fd406d7a8c

Chronological Activities

Analysis Process: systemd PID: 6406, Parent PID: 1

General

Start time (UTC):	11:57:04
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: generate-config PID: 6406, Parent PID: 1

General

Start time (UTC):	11:57:04
Start date (UTC):	22/12/2024
Path:	/usr/share/gdm/generate-config
Arguments:	/usr/share/gdm/generate-config
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: generate-config PID: 6407, Parent PID: 6406

General

Start time (UTC):	11:57:04
Start date (UTC):	22/12/2024
Path:	/usr/share/gdm/generate-config
Arguments:	-
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: pkill PID: 6407, Parent PID: 6406

General

Start time (UTC):	11:57:04
Start date (UTC):	22/12/2024
Path:	/usr/bin/pkill
Arguments:	pkill --signal HUP --uid gdm dconf-service
File size:	30968 bytes
MD5 hash:	fa96a75a08109d8842e4865b2907d51f

Chronological Activities

Analysis Process: systemd PID: 6408, Parent PID: 1860

General

Start time (UTC):	11:57:04
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: pulseaudio PID: 6408, Parent PID: 1860

General

Start time (UTC):	11:57:04
Start date (UTC):	22/12/2024
Path:	/usr/bin/pulseaudio
Arguments:	/usr/bin/pulseaudio --daemonize=no --log-target=journal
File size:	100832 bytes
MD5 hash:	0c3b4c789d8ffb12b25507f27e14c186

Chronological Activities

Analysis Process: systemd PID: 6409, Parent PID: 1

General

Start time (UTC):	11:57:04
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rsyslogd PID: 6409, Parent PID: 1

General

Start time (UTC):	11:57:04
Start date (UTC):	22/12/2024
Path:	/usr/sbin/rsyslogd
Arguments:	/usr/sbin/rsyslogd -n -iNONE
File size:	727248 bytes
MD5 hash:	0b8087fc907c42eb3c81a691db258e33

Chronological Activities

Analysis Process: systemd PID: 6419, Parent PID: 1

General

Start time (UTC):	11:57:07
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rtkit-daemon PID: 6419, Parent PID: 1

General

Start time (UTC):	11:57:07
Start date (UTC):	22/12/2024
Path:	/usr/libexec/rtkit-daemon
Arguments:	/usr/libexec/rtkit-daemon
File size:	68096 bytes
MD5 hash:	df0cacf1db4ec95ac70f5b6e06b8ffd7

Chronological Activities

Analysis Process: systemd PID: 6423, Parent PID: 1

General

Start time (UTC):	11:57:08
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: dbus-daemon PID: 6423, Parent PID: 1

General

Start time (UTC):	11:57:08
Start date (UTC):	22/12/2024
Path:	/usr/bin/dbus-daemon
Arguments:	/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
File size:	249032 bytes
MD5 hash:	3089d47e3f3ab84cd81c48fd406d7a8c

Chronological Activities

Analysis Process: systemd PID: 6426, Parent PID: 1860

General

Start time (UTC):	11:57:09
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: pulseaudio PID: 6426, Parent PID: 1860

General

Start time (UTC):	11:57:09
Start date (UTC):	22/12/2024
Path:	/usr/bin/pulseaudio
Arguments:	/usr/bin/pulseaudio --daemonize=no --log-target=journal
File size:	100832 bytes
MD5 hash:	0c3b4c789d8ffb12b25507f27e14c186

Chronological Activities

Analysis Process: systemd PID: 6427, Parent PID: 1

General

Start time (UTC):	11:57:09
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rsyslogd PID: 6427, Parent PID: 1

General

Start time (UTC):	11:57:09
Start date (UTC):	22/12/2024
Path:	/usr/sbin/rsyslogd
Arguments:	/usr/sbin/rsyslogd -n -iNONE
File size:	727248 bytes
MD5 hash:	0b8087fc907c42eb3c81a691db258e33

Chronological Activities

Analysis Process: systemd PID: 6429, Parent PID: 1

General

Start time (UTC):	11:57:09
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: gpu-manager PID: 6429, Parent PID: 1

General

Start time (UTC):	11:57:09
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	/usr/bin/gpu-manager --log /var/log/gpu-manager.log
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: gpu-manager PID: 6433, Parent PID: 6429

General

Start time (UTC):	11:57:10
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	-
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: sh PID: 6433, Parent PID: 6429

General

Start time (UTC):	11:57:10
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	sh -c "grep -G \"^blacklist.nvidia[[:space:]]$\" /etc/modprobe.d/*.conf"
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: sh PID: 6434, Parent PID: 6433

General

Start time (UTC):	11:57:10
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	-
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: grep PID: 6434, Parent PID: 6433

General

Start time (UTC):	11:57:10
Start date (UTC):	22/12/2024
Path:	/usr/bin/grep
Arguments:	grep -G ^blacklist.nvidia[[:space:]]$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf
File size:	199136 bytes
MD5 hash:	1e6ebb9dd094f774478f72727bdba0f5

Chronological Activities

Analysis Process: gpu-manager PID: 6436, Parent PID: 6429

General

Start time (UTC):	11:57:10
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	-
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: sh PID: 6436, Parent PID: 6429

General

Start time (UTC):	11:57:10
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	sh -c "grep -G \"^blacklist.nvidia[[:space:]]$\" /lib/modprobe.d/*.conf"
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: sh PID: 6437, Parent PID: 6436

General

Start time (UTC):	11:57:10
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	-
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: grep PID: 6437, Parent PID: 6436

General

Start time (UTC):	11:57:10
Start date (UTC):	22/12/2024
Path:	/usr/bin/grep
Arguments:	grep -G ^blacklist.nvidia[[:space:]]$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf
File size:	199136 bytes
MD5 hash:	1e6ebb9dd094f774478f72727bdba0f5

Chronological Activities

Analysis Process: gpu-manager PID: 6438, Parent PID: 6429

General

Start time (UTC):	11:57:11
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	-
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: sh PID: 6438, Parent PID: 6429

General

Start time (UTC):	11:57:11
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	sh -c "grep -G \"^blacklist.radeon[[:space:]]$\" /etc/modprobe.d/*.conf"
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: sh PID: 6439, Parent PID: 6438

General

Start time (UTC):	11:57:11
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	-
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: grep PID: 6439, Parent PID: 6438

General

Start time (UTC):	11:57:11
Start date (UTC):	22/12/2024
Path:	/usr/bin/grep
Arguments:	grep -G ^blacklist.radeon[[:space:]]$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf
File size:	199136 bytes
MD5 hash:	1e6ebb9dd094f774478f72727bdba0f5

Chronological Activities

Analysis Process: gpu-manager PID: 6440, Parent PID: 6429

General

Start time (UTC):	11:57:11
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	-
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: sh PID: 6440, Parent PID: 6429

General

Start time (UTC):	11:57:11
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	sh -c "grep -G \"^blacklist.radeon[[:space:]]$\" /lib/modprobe.d/*.conf"
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: sh PID: 6441, Parent PID: 6440

General

Start time (UTC):	11:57:11
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	-
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: grep PID: 6441, Parent PID: 6440

General

Start time (UTC):	11:57:11
Start date (UTC):	22/12/2024
Path:	/usr/bin/grep
Arguments:	grep -G ^blacklist.radeon[[:space:]]$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf
File size:	199136 bytes
MD5 hash:	1e6ebb9dd094f774478f72727bdba0f5

Chronological Activities

Analysis Process: gpu-manager PID: 6442, Parent PID: 6429

General

Start time (UTC):	11:57:11
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	-
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: sh PID: 6442, Parent PID: 6429

General

Start time (UTC):	11:57:11
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	sh -c "grep -G \"^blacklist.amdgpu[[:space:]]$\" /etc/modprobe.d/*.conf"
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: sh PID: 6443, Parent PID: 6442

General

Start time (UTC):	11:57:11
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	-
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: grep PID: 6443, Parent PID: 6442

General

Start time (UTC):	11:57:11
Start date (UTC):	22/12/2024
Path:	/usr/bin/grep
Arguments:	grep -G ^blacklist.amdgpu[[:space:]]$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf
File size:	199136 bytes
MD5 hash:	1e6ebb9dd094f774478f72727bdba0f5

Chronological Activities

Analysis Process: gpu-manager PID: 6446, Parent PID: 6429

General

Start time (UTC):	11:57:12
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	-
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: sh PID: 6446, Parent PID: 6429

General

Start time (UTC):	11:57:12
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	sh -c "grep -G \"^blacklist.amdgpu[[:space:]]$\" /lib/modprobe.d/*.conf"
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: sh PID: 6447, Parent PID: 6446

General

Start time (UTC):	11:57:12
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	-
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: grep PID: 6447, Parent PID: 6446

General

Start time (UTC):	11:57:12
Start date (UTC):	22/12/2024
Path:	/usr/bin/grep
Arguments:	grep -G ^blacklist.amdgpu[[:space:]]$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf
File size:	199136 bytes
MD5 hash:	1e6ebb9dd094f774478f72727bdba0f5

Chronological Activities

Analysis Process: systemd PID: 6445, Parent PID: 1

General

Start time (UTC):	11:57:12
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rtkit-daemon PID: 6445, Parent PID: 1

General

Start time (UTC):	11:57:12
Start date (UTC):	22/12/2024
Path:	/usr/libexec/rtkit-daemon
Arguments:	/usr/libexec/rtkit-daemon
File size:	68096 bytes
MD5 hash:	df0cacf1db4ec95ac70f5b6e06b8ffd7

Chronological Activities

Analysis Process: systemd PID: 6448, Parent PID: 1

General

Start time (UTC):	11:57:12
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: dbus-daemon PID: 6448, Parent PID: 1

General

Start time (UTC):	11:57:12
Start date (UTC):	22/12/2024
Path:	/usr/bin/dbus-daemon
Arguments:	/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
File size:	249032 bytes
MD5 hash:	3089d47e3f3ab84cd81c48fd406d7a8c

Chronological Activities

Analysis Process: systemd PID: 6449, Parent PID: 1

General

Start time (UTC):	11:57:12
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: generate-config PID: 6449, Parent PID: 1

General

Start time (UTC):	11:57:12
Start date (UTC):	22/12/2024
Path:	/usr/share/gdm/generate-config
Arguments:	/usr/share/gdm/generate-config
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: generate-config PID: 6450, Parent PID: 6449

General

Start time (UTC):	11:57:12
Start date (UTC):	22/12/2024
Path:	/usr/share/gdm/generate-config
Arguments:	-
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: pkill PID: 6450, Parent PID: 6449

General

Start time (UTC):	11:57:12
Start date (UTC):	22/12/2024
Path:	/usr/bin/pkill
Arguments:	pkill --signal HUP --uid gdm dconf-service
File size:	30968 bytes
MD5 hash:	fa96a75a08109d8842e4865b2907d51f

Chronological Activities

Analysis Process: systemd PID: 6451, Parent PID: 1860

General

Start time (UTC):	11:57:12
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: pulseaudio PID: 6451, Parent PID: 1860

General

Start time (UTC):	11:57:12
Start date (UTC):	22/12/2024
Path:	/usr/bin/pulseaudio
Arguments:	/usr/bin/pulseaudio --daemonize=no --log-target=journal
File size:	100832 bytes
MD5 hash:	0c3b4c789d8ffb12b25507f27e14c186

Chronological Activities

Analysis Process: systemd PID: 6452, Parent PID: 1

General

Start time (UTC):	11:57:12
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rsyslogd PID: 6452, Parent PID: 1

General

Start time (UTC):	11:57:12
Start date (UTC):	22/12/2024
Path:	/usr/sbin/rsyslogd
Arguments:	/usr/sbin/rsyslogd -n -iNONE
File size:	727248 bytes
MD5 hash:	0b8087fc907c42eb3c81a691db258e33

Chronological Activities

Analysis Process: systemd PID: 6454, Parent PID: 1

General

Start time (UTC):	11:57:12
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: dbus-daemon PID: 6454, Parent PID: 1

General

Start time (UTC):	11:57:12
Start date (UTC):	22/12/2024
Path:	/usr/bin/dbus-daemon
Arguments:	/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
File size:	249032 bytes
MD5 hash:	3089d47e3f3ab84cd81c48fd406d7a8c

Chronological Activities

Analysis Process: systemd PID: 6462, Parent PID: 1

General

Start time (UTC):	11:57:15
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rtkit-daemon PID: 6462, Parent PID: 1

General

Start time (UTC):	11:57:15
Start date (UTC):	22/12/2024
Path:	/usr/libexec/rtkit-daemon
Arguments:	/usr/libexec/rtkit-daemon
File size:	68096 bytes
MD5 hash:	df0cacf1db4ec95ac70f5b6e06b8ffd7

Chronological Activities

Analysis Process: systemd PID: 6466, Parent PID: 1

General

Start time (UTC):	11:57:16
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: polkitd PID: 6466, Parent PID: 1

General

Start time (UTC):	11:57:16
Start date (UTC):	22/12/2024
Path:	/usr/lib/policykit-1/polkitd
Arguments:	/usr/lib/policykit-1/polkitd --no-debug
File size:	121504 bytes
MD5 hash:	8efc9b4b5b524210ad2ea1954a9d0e69

Chronological Activities

Analysis Process: systemd PID: 6470, Parent PID: 1

General

Start time (UTC):	11:57:17
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: dbus-daemon PID: 6470, Parent PID: 1

General

Start time (UTC):	11:57:17
Start date (UTC):	22/12/2024
Path:	/usr/bin/dbus-daemon
Arguments:	/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
File size:	249032 bytes
MD5 hash:	3089d47e3f3ab84cd81c48fd406d7a8c

Chronological Activities

Analysis Process: systemd PID: 6471, Parent PID: 1860

General

Start time (UTC):	11:57:17
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: pulseaudio PID: 6471, Parent PID: 1860

General

Start time (UTC):	11:57:17
Start date (UTC):	22/12/2024
Path:	/usr/bin/pulseaudio
Arguments:	/usr/bin/pulseaudio --daemonize=no --log-target=journal
File size:	100832 bytes
MD5 hash:	0c3b4c789d8ffb12b25507f27e14c186

Chronological Activities

Analysis Process: systemd PID: 6472, Parent PID: 1

General

Start time (UTC):	11:57:17
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rsyslogd PID: 6472, Parent PID: 1

General

Start time (UTC):	11:57:17
Start date (UTC):	22/12/2024
Path:	/usr/sbin/rsyslogd
Arguments:	/usr/sbin/rsyslogd -n -iNONE
File size:	727248 bytes
MD5 hash:	0b8087fc907c42eb3c81a691db258e33

Chronological Activities

Analysis Process: systemd PID: 6474, Parent PID: 1

General

Start time (UTC):	11:57:18
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: gpu-manager PID: 6474, Parent PID: 1

General

Start time (UTC):	11:57:18
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	/usr/bin/gpu-manager --log /var/log/gpu-manager.log
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: gpu-manager PID: 6478, Parent PID: 6474

General

Start time (UTC):	11:57:18
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	-
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: sh PID: 6478, Parent PID: 6474

General

Start time (UTC):	11:57:18
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	sh -c "grep -G \"^blacklist.nvidia[[:space:]]$\" /etc/modprobe.d/*.conf"
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: sh PID: 6479, Parent PID: 6478

General

Start time (UTC):	11:57:18
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	-
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: grep PID: 6479, Parent PID: 6478

General

Start time (UTC):	11:57:18
Start date (UTC):	22/12/2024
Path:	/usr/bin/grep
Arguments:	grep -G ^blacklist.nvidia[[:space:]]$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf
File size:	199136 bytes
MD5 hash:	1e6ebb9dd094f774478f72727bdba0f5

Chronological Activities

Analysis Process: gpu-manager PID: 6481, Parent PID: 6474

General

Start time (UTC):	11:57:18
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	-
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: sh PID: 6481, Parent PID: 6474

General

Start time (UTC):	11:57:18
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	sh -c "grep -G \"^blacklist.nvidia[[:space:]]$\" /lib/modprobe.d/*.conf"
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: sh PID: 6484, Parent PID: 6481

General

Start time (UTC):	11:57:19
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	-
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: grep PID: 6484, Parent PID: 6481

General

Start time (UTC):	11:57:19
Start date (UTC):	22/12/2024
Path:	/usr/bin/grep
Arguments:	grep -G ^blacklist.nvidia[[:space:]]$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf
File size:	199136 bytes
MD5 hash:	1e6ebb9dd094f774478f72727bdba0f5

Chronological Activities

Analysis Process: gpu-manager PID: 6485, Parent PID: 6474

General

Start time (UTC):	11:57:19
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	-
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: sh PID: 6485, Parent PID: 6474

General

Start time (UTC):	11:57:19
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	sh -c "grep -G \"^blacklist.radeon[[:space:]]$\" /etc/modprobe.d/*.conf"
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: sh PID: 6486, Parent PID: 6485

General

Start time (UTC):	11:57:19
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	-
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: grep PID: 6486, Parent PID: 6485

General

Start time (UTC):	11:57:19
Start date (UTC):	22/12/2024
Path:	/usr/bin/grep
Arguments:	grep -G ^blacklist.radeon[[:space:]]$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf
File size:	199136 bytes
MD5 hash:	1e6ebb9dd094f774478f72727bdba0f5

Chronological Activities

Analysis Process: gpu-manager PID: 6487, Parent PID: 6474

General

Start time (UTC):	11:57:19
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	-
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: sh PID: 6487, Parent PID: 6474

General

Start time (UTC):	11:57:19
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	sh -c "grep -G \"^blacklist.radeon[[:space:]]$\" /lib/modprobe.d/*.conf"
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: sh PID: 6488, Parent PID: 6487

General

Start time (UTC):	11:57:19
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	-
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: grep PID: 6488, Parent PID: 6487

General

Start time (UTC):	11:57:19
Start date (UTC):	22/12/2024
Path:	/usr/bin/grep
Arguments:	grep -G ^blacklist.radeon[[:space:]]$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf
File size:	199136 bytes
MD5 hash:	1e6ebb9dd094f774478f72727bdba0f5

Chronological Activities

Analysis Process: gpu-manager PID: 6491, Parent PID: 6474

General

Start time (UTC):	11:57:20
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	-
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: sh PID: 6491, Parent PID: 6474

General

Start time (UTC):	11:57:20
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	sh -c "grep -G \"^blacklist.amdgpu[[:space:]]$\" /etc/modprobe.d/*.conf"
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: sh PID: 6492, Parent PID: 6491

General

Start time (UTC):	11:57:20
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	-
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: grep PID: 6492, Parent PID: 6491

General

Start time (UTC):	11:57:20
Start date (UTC):	22/12/2024
Path:	/usr/bin/grep
Arguments:	grep -G ^blacklist.amdgpu[[:space:]]$ /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/amd64-microcode-blacklist.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/mdadm.conf
File size:	199136 bytes
MD5 hash:	1e6ebb9dd094f774478f72727bdba0f5

Chronological Activities

Analysis Process: gpu-manager PID: 6497, Parent PID: 6474

General

Start time (UTC):	11:57:21
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	-
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: sh PID: 6497, Parent PID: 6474

General

Start time (UTC):	11:57:21
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	sh -c "grep -G \"^blacklist.amdgpu[[:space:]]$\" /lib/modprobe.d/*.conf"
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: sh PID: 6498, Parent PID: 6497

General

Start time (UTC):	11:57:21
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	-
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: grep PID: 6498, Parent PID: 6497

General

Start time (UTC):	11:57:21
Start date (UTC):	22/12/2024
Path:	/usr/bin/grep
Arguments:	grep -G ^blacklist.amdgpu[[:space:]]$ /lib/modprobe.d/aliases.conf /lib/modprobe.d/blacklist_linux_5.4.0-72-generic.conf /lib/modprobe.d/blacklist_linux_5.4.0-81-generic.conf /lib/modprobe.d/fbdev-blacklist.conf /lib/modprobe.d/systemd.conf
File size:	199136 bytes
MD5 hash:	1e6ebb9dd094f774478f72727bdba0f5

Chronological Activities

Analysis Process: systemd PID: 6490, Parent PID: 1

General

Start time (UTC):	11:57:20
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rtkit-daemon PID: 6490, Parent PID: 1

General

Start time (UTC):	11:57:20
Start date (UTC):	22/12/2024
Path:	/usr/libexec/rtkit-daemon
Arguments:	/usr/libexec/rtkit-daemon
File size:	68096 bytes
MD5 hash:	df0cacf1db4ec95ac70f5b6e06b8ffd7

Chronological Activities

Analysis Process: systemd PID: 6496, Parent PID: 1

General

Start time (UTC):	11:57:20
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: polkitd PID: 6496, Parent PID: 1

General

Start time (UTC):	11:57:20
Start date (UTC):	22/12/2024
Path:	/usr/lib/policykit-1/polkitd
Arguments:	/usr/lib/policykit-1/polkitd --no-debug
File size:	121504 bytes
MD5 hash:	8efc9b4b5b524210ad2ea1954a9d0e69

Chronological Activities

Analysis Process: systemd PID: 6502, Parent PID: 1

General

Start time (UTC):	11:57:21
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: dbus-daemon PID: 6502, Parent PID: 1

General

Start time (UTC):	11:57:21
Start date (UTC):	22/12/2024
Path:	/usr/bin/dbus-daemon
Arguments:	/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
File size:	249032 bytes
MD5 hash:	3089d47e3f3ab84cd81c48fd406d7a8c

Chronological Activities

Analysis Process: systemd PID: 6503, Parent PID: 1

General

Start time (UTC):	11:57:21
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: generate-config PID: 6503, Parent PID: 1

General

Start time (UTC):	11:57:21
Start date (UTC):	22/12/2024
Path:	/usr/share/gdm/generate-config
Arguments:	/usr/share/gdm/generate-config
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: generate-config PID: 6505, Parent PID: 6503

General

Start time (UTC):	11:57:21
Start date (UTC):	22/12/2024
Path:	/usr/share/gdm/generate-config
Arguments:	-
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: pkill PID: 6505, Parent PID: 6503

General

Start time (UTC):	11:57:21
Start date (UTC):	22/12/2024
Path:	/usr/bin/pkill
Arguments:	pkill --signal HUP --uid gdm dconf-service
File size:	30968 bytes
MD5 hash:	fa96a75a08109d8842e4865b2907d51f

Chronological Activities

Analysis Process: systemd PID: 6504, Parent PID: 1860

General

Start time (UTC):	11:57:21
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: pulseaudio PID: 6504, Parent PID: 1860

General

Start time (UTC):	11:57:21
Start date (UTC):	22/12/2024
Path:	/usr/bin/pulseaudio
Arguments:	/usr/bin/pulseaudio --daemonize=no --log-target=journal
File size:	100832 bytes
MD5 hash:	0c3b4c789d8ffb12b25507f27e14c186

Chronological Activities

Analysis Process: systemd PID: 6506, Parent PID: 1

General

Start time (UTC):	11:57:21
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rsyslogd PID: 6506, Parent PID: 1

General

Start time (UTC):	11:57:21
Start date (UTC):	22/12/2024
Path:	/usr/sbin/rsyslogd
Arguments:	/usr/sbin/rsyslogd -n -iNONE
File size:	727248 bytes
MD5 hash:	0b8087fc907c42eb3c81a691db258e33

Chronological Activities

Analysis Process: systemd PID: 6515, Parent PID: 1

General

Start time (UTC):	11:57:24
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: dbus-daemon PID: 6515, Parent PID: 1

General

Start time (UTC):	11:57:24
Start date (UTC):	22/12/2024
Path:	/usr/bin/dbus-daemon
Arguments:	/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
File size:	249032 bytes
MD5 hash:	3089d47e3f3ab84cd81c48fd406d7a8c

Chronological Activities

Analysis Process: systemd PID: 6516, Parent PID: 1

General

Start time (UTC):	11:57:24
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rsyslogd PID: 6516, Parent PID: 1

General

Start time (UTC):	11:57:24
Start date (UTC):	22/12/2024
Path:	/usr/sbin/rsyslogd
Arguments:	/usr/sbin/rsyslogd -n -iNONE
File size:	727248 bytes
MD5 hash:	0b8087fc907c42eb3c81a691db258e33

Chronological Activities

Analysis Process: systemd PID: 6518, Parent PID: 1860

General

Start time (UTC):	11:57:24
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: pulseaudio PID: 6518, Parent PID: 1860

General

Start time (UTC):	11:57:24
Start date (UTC):	22/12/2024
Path:	/usr/bin/pulseaudio
Arguments:	/usr/bin/pulseaudio --daemonize=no --log-target=journal
File size:	100832 bytes
MD5 hash:	0c3b4c789d8ffb12b25507f27e14c186

Chronological Activities

Analysis Process: systemd PID: 6519, Parent PID: 1

General

Start time (UTC):	11:57:25
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: gpu-manager PID: 6519, Parent PID: 1

General

Start time (UTC):	11:57:25
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	/usr/bin/gpu-manager --log /var/log/gpu-manager.log
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: gpu-manager PID: 6523, Parent PID: 6519

General

Start time (UTC):	11:57:25
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	-
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: sh PID: 6523, Parent PID: 6519

General

Start time (UTC):	11:57:25
Start date (UTC):	22/12/2024
Path:	/bin/sh
Arguments:	sh -c "grep -G \"^blacklist.nvidia[[:space:]]$\" /etc/modprobe.d/*.conf"
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: systemd PID: 6524, Parent PID: 1

General

Start time (UTC):	11:57:25
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: dbus-daemon PID: 6524, Parent PID: 1

General

Start time (UTC):	11:57:25
Start date (UTC):	22/12/2024
Path:	/usr/bin/dbus-daemon
Arguments:	/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
File size:	249032 bytes
MD5 hash:	3089d47e3f3ab84cd81c48fd406d7a8c

Chronological Activities

Analysis Process: systemd PID: 6525, Parent PID: 1

General

Start time (UTC):	11:57:25
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: generate-config PID: 6525, Parent PID: 1

General

Start time (UTC):	11:57:25
Start date (UTC):	22/12/2024
Path:	/usr/share/gdm/generate-config
Arguments:	/usr/share/gdm/generate-config
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: systemd PID: 6526, Parent PID: 1

General

Start time (UTC):	11:57:25
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rsyslogd PID: 6526, Parent PID: 1

General

Start time (UTC):	11:57:25
Start date (UTC):	22/12/2024
Path:	/usr/sbin/rsyslogd
Arguments:	/usr/sbin/rsyslogd -n -iNONE
File size:	727248 bytes
MD5 hash:	0b8087fc907c42eb3c81a691db258e33

Chronological Activities

Analysis Process: systemd PID: 6528, Parent PID: 1

General

Start time (UTC):	11:57:25
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: dbus-daemon PID: 6528, Parent PID: 1

General

Start time (UTC):	11:57:25
Start date (UTC):	22/12/2024
Path:	/usr/bin/dbus-daemon
Arguments:	/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
File size:	249032 bytes
MD5 hash:	3089d47e3f3ab84cd81c48fd406d7a8c

Chronological Activities

Analysis Process: systemd PID: 6529, Parent PID: 1860

General

Start time (UTC):	11:57:26
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: pulseaudio PID: 6529, Parent PID: 1860

General

Start time (UTC):	11:57:26
Start date (UTC):	22/12/2024
Path:	/usr/bin/pulseaudio
Arguments:	/usr/bin/pulseaudio --daemonize=no --log-target=journal
File size:	100832 bytes
MD5 hash:	0c3b4c789d8ffb12b25507f27e14c186

Chronological Activities

Analysis Process: systemd PID: 6533, Parent PID: 1

General

Start time (UTC):	11:57:26
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: gpu-manager PID: 6533, Parent PID: 1

General

Start time (UTC):	11:57:26
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	/usr/bin/gpu-manager --log /var/log/gpu-manager.log
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: systemd PID: 6535, Parent PID: 1

General

Start time (UTC):	11:57:27
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: generate-config PID: 6535, Parent PID: 1

General

Start time (UTC):	11:57:27
Start date (UTC):	22/12/2024
Path:	/usr/share/gdm/generate-config
Arguments:	/usr/share/gdm/generate-config
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: generate-config PID: 6537, Parent PID: 6535

General

Start time (UTC):	11:57:27
Start date (UTC):	22/12/2024
Path:	/usr/share/gdm/generate-config
Arguments:	-
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: pkill PID: 6537, Parent PID: 6535

General

Start time (UTC):	11:57:27
Start date (UTC):	22/12/2024
Path:	/usr/bin/pkill
Arguments:	pkill --signal HUP --uid gdm dconf-service
File size:	30968 bytes
MD5 hash:	fa96a75a08109d8842e4865b2907d51f

Chronological Activities

Analysis Process: systemd PID: 6536, Parent PID: 1

General

Start time (UTC):	11:57:27
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rsyslogd PID: 6536, Parent PID: 1

General

Start time (UTC):	11:57:27
Start date (UTC):	22/12/2024
Path:	/usr/sbin/rsyslogd
Arguments:	/usr/sbin/rsyslogd -n -iNONE
File size:	727248 bytes
MD5 hash:	0b8087fc907c42eb3c81a691db258e33

Chronological Activities

Analysis Process: systemd PID: 6538, Parent PID: 1860

General

Start time (UTC):	11:57:27
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: pulseaudio PID: 6538, Parent PID: 1860

General

Start time (UTC):	11:57:27
Start date (UTC):	22/12/2024
Path:	/usr/bin/pulseaudio
Arguments:	/usr/bin/pulseaudio --daemonize=no --log-target=journal
File size:	100832 bytes
MD5 hash:	0c3b4c789d8ffb12b25507f27e14c186

Chronological Activities

Analysis Process: systemd PID: 6539, Parent PID: 1

General

Start time (UTC):	11:57:27
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rsyslogd PID: 6539, Parent PID: 1

General

Start time (UTC):	11:57:27
Start date (UTC):	22/12/2024
Path:	/usr/sbin/rsyslogd
Arguments:	/usr/sbin/rsyslogd -n -iNONE
File size:	727248 bytes
MD5 hash:	0b8087fc907c42eb3c81a691db258e33

Chronological Activities

Analysis Process: systemd PID: 6540, Parent PID: 1860

General

Start time (UTC):	11:57:27
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: pulseaudio PID: 6540, Parent PID: 1860

General

Start time (UTC):	11:57:27
Start date (UTC):	22/12/2024
Path:	/usr/bin/pulseaudio
Arguments:	/usr/bin/pulseaudio --daemonize=no --log-target=journal
File size:	100832 bytes
MD5 hash:	0c3b4c789d8ffb12b25507f27e14c186

Chronological Activities

Analysis Process: systemd PID: 6541, Parent PID: 1

General

Start time (UTC):	11:57:28
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rsyslogd PID: 6541, Parent PID: 1

General

Start time (UTC):	11:57:28
Start date (UTC):	22/12/2024
Path:	/usr/sbin/rsyslogd
Arguments:	/usr/sbin/rsyslogd -n -iNONE
File size:	727248 bytes
MD5 hash:	0b8087fc907c42eb3c81a691db258e33

Analysis Process: systemd PID: 6542, Parent PID: 1860

General

Start time (UTC):	11:57:28
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: pulseaudio PID: 6542, Parent PID: 1860

General

Start time (UTC):	11:57:28
Start date (UTC):	22/12/2024
Path:	/usr/bin/pulseaudio
Arguments:	/usr/bin/pulseaudio --daemonize=no --log-target=journal
File size:	100832 bytes
MD5 hash:	0c3b4c789d8ffb12b25507f27e14c186

Chronological Activities

Analysis Process: systemd PID: 6543, Parent PID: 1

General

Start time (UTC):	11:57:28
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rsyslogd PID: 6543, Parent PID: 1

General

Start time (UTC):	11:57:28
Start date (UTC):	22/12/2024
Path:	/usr/sbin/rsyslogd
Arguments:	/usr/sbin/rsyslogd -n -iNONE
File size:	727248 bytes
MD5 hash:	0b8087fc907c42eb3c81a691db258e33

Chronological Activities

Analysis Process: systemd PID: 6544, Parent PID: 1860

General

Start time (UTC):	11:57:28
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: systemd PID: 6545, Parent PID: 1

General

Start time (UTC):	11:57:28
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rsyslogd PID: 6545, Parent PID: 1

General

Start time (UTC):	11:57:28
Start date (UTC):	22/12/2024
Path:	/usr/sbin/rsyslogd
Arguments:	/usr/sbin/rsyslogd -n -iNONE
File size:	727248 bytes
MD5 hash:	0b8087fc907c42eb3c81a691db258e33

Chronological Activities

Analysis Process: systemd PID: 6546, Parent PID: 1860

General

Start time (UTC):	11:57:28
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: pulseaudio PID: 6546, Parent PID: 1860

General

Start time (UTC):	11:57:28
Start date (UTC):	22/12/2024
Path:	/usr/bin/pulseaudio
Arguments:	/usr/bin/pulseaudio --daemonize=no --log-target=journal
File size:	100832 bytes
MD5 hash:	0c3b4c789d8ffb12b25507f27e14c186

Chronological Activities

Analysis Process: systemd PID: 6547, Parent PID: 1

General

Start time (UTC):	11:57:28
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: gpu-manager PID: 6547, Parent PID: 1

General

Start time (UTC):	11:57:28
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	/usr/bin/gpu-manager --log /var/log/gpu-manager.log
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: systemd PID: 6548, Parent PID: 1

General

Start time (UTC):	11:57:28
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: generate-config PID: 6548, Parent PID: 1

General

Start time (UTC):	11:57:28
Start date (UTC):	22/12/2024
Path:	/usr/share/gdm/generate-config
Arguments:	/usr/share/gdm/generate-config
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: systemd PID: 6549, Parent PID: 1

General

Start time (UTC):	11:57:28
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: rsyslogd PID: 6549, Parent PID: 1

General

Start time (UTC):	11:57:28
Start date (UTC):	22/12/2024
Path:	/usr/sbin/rsyslogd
Arguments:	/usr/sbin/rsyslogd -n -iNONE
File size:	727248 bytes
MD5 hash:	0b8087fc907c42eb3c81a691db258e33

Chronological Activities

Analysis Process: systemd PID: 6552, Parent PID: 1

General

Start time (UTC):	11:57:29
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: gpu-manager PID: 6552, Parent PID: 1

General

Start time (UTC):	11:57:29
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	/usr/bin/gpu-manager --log /var/log/gpu-manager.log
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: systemd PID: 6553, Parent PID: 1

General

Start time (UTC):	11:57:29
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: generate-config PID: 6553, Parent PID: 1

General

Start time (UTC):	11:57:29
Start date (UTC):	22/12/2024
Path:	/usr/share/gdm/generate-config
Arguments:	/usr/share/gdm/generate-config
File size:	129816 bytes
MD5 hash:	1e6b1c887c59a315edb7eb9a315fc84c

Chronological Activities

Analysis Process: systemd PID: 6554, Parent PID: 1

General

Start time (UTC):	11:57:31
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: gpu-manager PID: 6554, Parent PID: 1

General

Start time (UTC):	11:57:31
Start date (UTC):	22/12/2024
Path:	/usr/bin/gpu-manager
Arguments:	/usr/bin/gpu-manager --log /var/log/gpu-manager.log
File size:	76616 bytes
MD5 hash:	8fae9dd5dd67e1f33d873089c2fd8761

Chronological Activities

Analysis Process: systemd PID: 6555, Parent PID: 1

General

Start time (UTC):	11:57:31
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: plymouth PID: 6555, Parent PID: 1

General

Start time (UTC):	11:57:31
Start date (UTC):	22/12/2024
Path:	/bin/plymouth
Arguments:	/bin/plymouth quit
File size:	51352 bytes
MD5 hash:	87003efd8dad470042f5e75360a8f49f

Chronological Activities

Analysis Process: systemd PID: 6580, Parent PID: 1

General

Start time (UTC):	11:58:28
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: systemd-logind PID: 6580, Parent PID: 1

General

Start time (UTC):	11:58:28
Start date (UTC):	22/12/2024
Path:	/lib/systemd/systemd-logind
Arguments:	/lib/systemd/systemd-logind
File size:	268576 bytes
MD5 hash:	8dd58a1b4c12f7a1d5fe3ce18b2aaeef

Chronological Activities

Analysis Process: systemd PID: 6659, Parent PID: 1

General

Start time (UTC):	11:58:29
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: systemd PID: 6660, Parent PID: 1

General

Start time (UTC):	11:58:29
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: dbus-daemon PID: 6660, Parent PID: 1

General

Start time (UTC):	11:58:29
Start date (UTC):	22/12/2024
Path:	/usr/bin/dbus-daemon
Arguments:	/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
File size:	249032 bytes
MD5 hash:	3089d47e3f3ab84cd81c48fd406d7a8c

Chronological Activities

Analysis Process: systemd PID: 6661, Parent PID: 1

General

Start time (UTC):	11:58:29
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: dbus-daemon PID: 6661, Parent PID: 1

General

Start time (UTC):	11:58:29
Start date (UTC):	22/12/2024
Path:	/usr/bin/dbus-daemon
Arguments:	/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
File size:	249032 bytes
MD5 hash:	3089d47e3f3ab84cd81c48fd406d7a8c

Analysis Process: systemd PID: 6662, Parent PID: 1

General

Start time (UTC):	11:58:29
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: dbus-daemon PID: 6662, Parent PID: 1

General

Start time (UTC):	11:58:29
Start date (UTC):	22/12/2024
Path:	/usr/bin/dbus-daemon
Arguments:	/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
File size:	249032 bytes
MD5 hash:	3089d47e3f3ab84cd81c48fd406d7a8c

Analysis Process: systemd PID: 6663, Parent PID: 1

General

Start time (UTC):	11:58:29
Start date (UTC):	22/12/2024
Path:	/usr/lib/systemd/systemd
Arguments:	-
File size:	1620224 bytes
MD5 hash:	9b2bec7092a40488108543f9334aab75

Chronological Activities

Analysis Process: dbus-daemon PID: 6663, Parent PID: 1

General

Start time (UTC):	11:58:29
Start date (UTC):	22/12/2024
Path:	/usr/bin/dbus-daemon
Arguments:	/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
File size:	249032 bytes
MD5 hash:	3089d47e3f3ab84cd81c48fd406d7a8c

Description:	This technique has been deprecated. Please use Command and Scripting Interpreter where appropriate.
Tactics:	Defense Evasion, Execution
Data Sources:
Platforms:	Linux, macOS, Windows
Url:	Open detailed description by Mitre

Description:	Adversaries may modify and/or disable security tools to avoid possible detection of their malware/tools and activities. This may take many forms, such as killing security software processes or services, modifying / deleting Registry keys or configuration files so that tools do not operate properly, or other methods to interfere with security tools scanning or reporting information. Adversaries may also disable updates to prevent the latest security patches from reaching tools on victim systems.
Tactics:	Defense Evasion
Data Sources:	Command: Command Execution, Driver: Driver Load, Process: Process Creation, Process: Process Termination, Sensor Health: Host Status, Service: Service Metadata, Windows Registry: Windows Registry Key Deletion, Windows Registry: Windows Registry Key Modification
Platforms:	Containers, IaaS, Linux, macOS, Network, Windows
Url:	Open detailed description by Mitre

Description:	Adversaries may set files and directories to be hidden to evade detection mechanisms. To prevent normal users from accidentally changing special files on a system, most operating systems have the concept of a ‘hidden’ file. These files don’t show up when a user browses the file system with a GUI or when using normal commands on the command line. Users must explicitly ask to show the hidden files either via a series of Graphical User Interface (GUI) prompts or with command line switches ( `dir /a` for Windows and `ls –a` for Linux and macOS).
Tactics:	Defense Evasion
Data Sources:	Command: Command Execution, File: File Creation, File: File Metadata, Process: Process Creation
Platforms:	Linux, macOS, Windows
Url:	Open detailed description by Mitre

Description:	Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit. This is common behavior that can be used across different platforms and the network to evade defenses.
Tactics:	Defense Evasion
Data Sources:	Command: Command Execution, File: File Creation, File: File Metadata, Module: Module Load, Process: OS API Execution, Process: Process Creation, Script: Script Execution, WMI: WMI Creation, Windows Registry: Windows Registry Key Creation
Platforms:	Linux, macOS, Windows
Url:	Open detailed description by Mitre

Description:	Adversaries may delete or modify artifacts generated within systems to remove evidence of their presence or hinder defenses. Various artifacts may be created by an adversary or something that can be attributed to an adversary’s actions. Typically these artifacts are used as defensive indicators related to monitored events, such as strings from downloaded files, logs that are generated from user actions, and other data analyzed by defenders. Location, format, and type of artifact (such as command or login history) are often specific to each platform.
Tactics:	Defense Evasion
Data Sources:	Application Log: Application Log Content, Command: Command Execution, File: File Deletion, File: File Metadata, File: File Modification, Firewall: Firewall Rule Modification, Network Traffic: Network Traffic Content, Process: OS API Execution, Process: Process Creation, Scheduled Job: Scheduled Job Modification, User Account: User Account Authentication, User Account: User Account Deletion, Windows Registry: Windows Registry Key Deletion, Windows Registry: Windows Registry Key Modification
Platforms:	Containers, Google Workspace, Linux, macOS, Network, Office 365, Windows
Url:	Open detailed description by Mitre

Description:	Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password, from the operating system and software. Credentials can then be used to perform Lateral Movement and access restricted information.
Tactics:	Credential Access
Data Sources:	Active Directory: Active Directory Object Access, Command: Command Execution, File: File Access, Network Traffic: Network Traffic Content, Network Traffic: Network Traffic Flow, Process: OS API Execution, Process: Process Access, Process: Process Creation, Windows Registry: Windows Registry Key Access
Platforms:	Linux, macOS, Windows
Url:	Open detailed description by Mitre

Description:	Adversaries may attempt to get a listing of security software, configurations, defensive tools, and sensors that are installed on a system or in a cloud environment. This may include things such as firewall rules and anti-virus. Adversaries may use the information from Security Software Discovery during automated discovery to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions.
Tactics:	Discovery
Data Sources:	Command: Command Execution, Firewall: Firewall Enumeration, Firewall: Firewall Metadata, Process: OS API Execution, Process: Process Creation
Platforms:	Azure AD, Google Workspace, IaaS, Linux, macOS, Office 365, SaaS, Windows
Url:	Open detailed description by Mitre

Description:	Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system. Adversaries may use the information from File and Directory Discovery during automated discovery to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions.
Tactics:	Discovery
Data Sources:	Command: Command Execution, Process: OS API Execution, Process: Process Creation
Platforms:	Linux, macOS, Network, Windows
Url:	Open detailed description by Mitre

Description:	An adversary may attempt to get detailed information about the operating system and hardware, including version, patches, hotfixes, service packs, and architecture. Adversaries may use the information from System Information Discovery during automated discovery to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions.
Tactics:	Discovery
Data Sources:	Command: Command Execution, Process: OS API Execution, Process: Process Creation
Platforms:	IaaS, Linux, macOS, Network, Windows
Url:	Open detailed description by Mitre

Description:	Adversaries may employ a known encryption algorithm to conceal command and control traffic rather than relying on any inherent protections provided by a communication protocol. Despite the use of a secure algorithm, these implementations may be vulnerable to reverse engineering if secret keys are encoded and/or generated within malware samples/configuration files.
Tactics:	Command and Control
Data Sources:	Network Traffic: Network Traffic Content
Platforms:	Linux, macOS, Windows
Url:	Open detailed description by Mitre

Description:	Adversaries may communicate using a protocol and port pairing that are typically not associated. For example, HTTPS over port 8088or port 587as opposed to the traditional port 443. Adversaries may make changes to the standard port used by a protocol to bypass filtering or muddle analysis/parsing of network data.
Tactics:	Command and Control
Data Sources:	Network Traffic: Network Traffic Content, Network Traffic: Network Traffic Flow
Platforms:	Linux, macOS, Windows
Url:	Open detailed description by Mitre

Description:	Adversaries may use an OSI non-application layer protocol for communication between host and C2 server or among infected hosts within a network. The list of possible protocols is extensive.Specific examples include use of network layer protocols, such as the Internet Control Message Protocol (ICMP), transport layer protocols, such as the User Datagram Protocol (UDP), session layer protocols, such as Socket Secure (SOCKS), as well as redirected/tunneled protocols, such as Serial over LAN (SOL).
Tactics:	Command and Control
Data Sources:	Network Traffic: Network Traffic Content, Network Traffic: Network Traffic Flow
Platforms:	Linux, macOS, Network, Windows
Url:	Open detailed description by Mitre

Description:	Adversaries may communicate using OSI application layer protocols to avoid detection/network filtering by blending in with existing traffic. Commands to the remote system, and often the results of those commands, will be embedded within the protocol traffic between the client and server.
Tactics:	Command and Control
Data Sources:	Network Traffic: Network Traffic Content, Network Traffic: Network Traffic Flow
Platforms:	Linux, macOS, Windows
Url:	Open detailed description by Mitre

Description:	Adversaries may stop or disable services on a system to render those services unavailable to legitimate users. Stopping critical services or processes can inhibit or stop response to an incident or aid in the adversary's overall objectives to cause damage to the environment.
Tactics:	Impact
Data Sources:	Command: Command Execution, File: File Modification, Process: OS API Execution, Process: Process Creation, Process: Process Termination, Service: Service Metadata, Windows Registry: Windows Registry Key Modification
Platforms:	Linux, macOS, Windows
Url:	Open detailed description by Mitre

Behavior Section

Behavior Chronological

Disassembly

Uncategorized

Graph

Loading Joe Sandbox Report ...

Warning!

Linux Analysis Report byte.x86.elf

Overview

General Information

Detection

Signatures

Classification

General Information

Warnings

Process Tree

Malware Threat Intel

Yara Signatures

Memory Dumps

Suricata Signatures

Joe Sandbox Signatures

AV Detection

Bitcoin Miner

Networking

System Summary

Data Obfuscation

Persistence and Installation Behavior

Hooking and other Techniques for Hiding and Protection

Malware Analysis System Evasion

Stealing of Sensitive Information

Remote Access Functionality

Mitre Att&ck Matrix

Malware Configuration

Behavior Graph

Antivirus, Machine Learning and Genetic Malware Detection

Initial Sample

Dropped Files

Domains

URLs

Domains and IPs

Contacted Domains

URLs from Memory and Binaries

World Map of Contacted IPs

Public IPs

Joe Sandbox View / Context

IPs

Domains

ASNs

JA3 Fingerprints

Dropped Files

Created / dropped Files

/run/systemd/seats/.#seat085RphJ

/run/systemd/seats/.#seat0ObhoQQ

/var/log/auth.log

/var/log/kern.log

/var/log/syslog

Static File Info

General

Static ELF Info

ELF header

Program Segments

Network Behavior

Network Port Distribution

TCP Packets

UDP Packets

ICMP Packets

DNS Queries

DNS Answers

System Behavior

Analysis Process: byte.x86.elf PID: 6237, Parent PID: 6163

General

Chronological Activities

Analysis Process: byte.x86.elf PID: 6238, Parent PID: 6237

General

Chronological Activities

Analysis Process: byte.x86.elf PID: 6239, Parent PID: 6237

General

Chronological Activities

Analysis Process: byte.x86.elf PID: 6240, Parent PID: 6237

General

Linux Analysis Report
byte.x86.elf