Edit tour

Linux Analysis Report
byte.x86.elf

Overview

General Information

Sample name:	byte.x86.elf
Analysis ID:	1581533
MD5:	f7eef7a952b17ab75b3bb24d03fbcdf2
SHA1:	83bf20a36a93b73c1f78ff224459a797de605fa5
SHA256:	9928c99ec2ef2eee7df7c786dbc35f5b765e9701de45e194ab59123bdf535983
Tags:	elfuser-abuse_ch
Infos:

Detection

Mirai, Okiru

Score:	100
Range:	0 - 100
Whitelisted:	false

Signatures

Antivirus / Scanner detection for submitted sample

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 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

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

Found strings indicative of a multi-platform dropper

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

Reads the 'hosts' file potentially containing internal network hosts

Sample contains strings indicative of BusyBox which embeds multiple Unix commands in a single executable

Sample has stripped symbol table

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:	1581533
Start date and time:	2024-12-28 02:22:05 +01:00
Joe Sandbox product:	CloudBasic
Overall analysis duration:	0h 4m 0s
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:	mal100.spre.troj.linELF@0/24@96/0

Warnings

Connection to analysis system has been lost, crash info: Unknown

Process Tree

system is lnxubuntu20

byte.x86.elf (PID: 6247, Parent: 6163, MD5: f7eef7a952b17ab75b3bb24d03fbcdf2) Arguments: /tmp/byte.x86.elf

byte.x86.elf New Fork (PID: 6249, Parent: 6247)

byte.x86.elf New Fork (PID: 6250, Parent: 6247)

byte.x86.elf New Fork (PID: 6251, Parent: 6247)

byte.x86.elf New Fork (PID: 6252, Parent: 6251)

byte.x86.elf New Fork (PID: 6253, Parent: 6251)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

grep (PID: 6394, Parent: 6392, 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: 6395, Parent: 6391)

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

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

grep (PID: 6396, Parent: 6395, 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: 6397, Parent: 6391)

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

sh New Fork (PID: 6398, Parent: 6397)

grep (PID: 6398, Parent: 6397, 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: 6401, Parent: 6391)

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

sh New Fork (PID: 6402, Parent: 6401)

grep (PID: 6402, Parent: 6401, 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: 6406, Parent: 6391)

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

sh New Fork (PID: 6408, Parent: 6406)

grep (PID: 6408, Parent: 6406, 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

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

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

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

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

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

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

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

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

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

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

generate-config New Fork (PID: 6414, Parent: 6413)

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

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

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

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

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

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

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

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

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

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: 6431, Parent: 1)

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

gpu-manager New Fork (PID: 6432, Parent: 6431)

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

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

grep (PID: 6434, Parent: 6432, 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: 6435, Parent: 6431)

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

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

grep (PID: 6436, Parent: 6435, 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: 6440, Parent: 6431)

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

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

grep (PID: 6441, Parent: 6440, 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: 6443, Parent: 6431)

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

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

grep (PID: 6446, Parent: 6443, 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

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

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

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

dbus-daemon (PID: 6447, 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: 1)

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

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

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

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

dbus-daemon (PID: 6461, 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)

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

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

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

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

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

gpu-manager New Fork (PID: 6470, Parent: 6468)

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

sh New Fork (PID: 6471, Parent: 6470)

grep (PID: 6471, Parent: 6470, 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: 6472, Parent: 6468)

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

sh New Fork (PID: 6473, Parent: 6472)

grep (PID: 6473, Parent: 6472, 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: 6474, Parent: 6468)

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

sh New Fork (PID: 6475, Parent: 6474)

grep (PID: 6475, Parent: 6474, 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: 6476, Parent: 6468)

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

sh New Fork (PID: 6477, Parent: 6476)

grep (PID: 6477, Parent: 6476, 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: 6483, Parent: 6468)

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

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

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

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

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

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

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

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

generate-config New Fork (PID: 6487, Parent: 6486)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

generate-config New Fork (PID: 6508, Parent: 6507)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

gpu-manager (PID: 6534, 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

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

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

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

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

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

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

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

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

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

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

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

dbus-daemon (PID: 6644, 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

Initial Sample

Source	Rule	Description	Author	Strings
byte.x86.elf	JoeSecurity_Okiru	Yara detected Okiru	Joe Security
byte.x86.elf	JoeSecurity_Mirai_9	Yara detected Mirai	Joe Security
byte.x86.elf	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
byte.x86.elf	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
byte.x86.elf	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
byte.x86.elf	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
byte.x86.elf	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
byte.x86.elf	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
byte.x86.elf	Linux_Trojan_Mirai_88de437f	unknown	unknown	0x96e2:$a: 24 08 8B 4C 24 04 85 D2 74 0D 31 C0 89 F6 C6 04 08 00 40 39 D0
byte.x86.elf	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
byte.x86.elf	Linux_Trojan_Mirai_389ee3e9	unknown	unknown	0xccab:$a: 89 45 00 EB 2C 8B 4B 04 8B 13 8B 7B 18 8B 01 01 02 8B 02 83
byte.x86.elf	Linux_Trojan_Mirai_cc93863b	unknown	unknown	0xb5b0:$a: C3 57 8B 44 24 0C 8B 4C 24 10 8B 7C 24 08 F3 AA 8B 44 24 08
byte.x86.elf	Linux_Trojan_Mirai_8aa7b5d3	unknown	unknown	0x96b2:$a: 8B 4C 24 14 8B 74 24 0C 8B 5C 24 10 85 C9 74 0D 31 D2 8A 04 1A 88
byte.x86.elf	Mirai_Botnet_Malware	Detects Mirai Botnet Malware	Florian Roth	0xea80:$x1: POST /cdn-cgi/ 0xfdb0:$s1: LCOGQGPTGP
Click to see the 9 entries

Memory Dumps

Source	Rule	Description	Author	Strings
6247.1.0000000008048000.000000000805a000.r-x.sdmp	JoeSecurity_Okiru	Yara detected Okiru	Joe Security
6247.1.0000000008048000.000000000805a000.r-x.sdmp	JoeSecurity_Mirai_9	Yara detected Mirai	Joe Security
6247.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
6247.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
6247.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
6247.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
6247.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
6247.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
6247.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_88de437f	unknown	unknown	0x96e2:$a: 24 08 8B 4C 24 04 85 D2 74 0D 31 C0 89 F6 C6 04 08 00 40 39 D0
6247.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
6247.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_389ee3e9	unknown	unknown	0xccab:$a: 89 45 00 EB 2C 8B 4B 04 8B 13 8B 7B 18 8B 01 01 02 8B 02 83
6247.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_cc93863b	unknown	unknown	0xb5b0:$a: C3 57 8B 44 24 0C 8B 4C 24 10 8B 7C 24 08 F3 AA 8B 44 24 08
6247.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_8aa7b5d3	unknown	unknown	0x96b2:$a: 8B 4C 24 14 8B 74 24 0C 8B 5C 24 10 85 C9 74 0D 31 D2 8A 04 1A 88
6247.1.0000000008048000.000000000805a000.r-x.sdmp	Mirai_Botnet_Malware	Detects Mirai Botnet Malware	Florian Roth	0xea80:$x1: POST /cdn-cgi/ 0xfdb0:$s1: LCOGQGPTGP
6253.1.0000000008048000.000000000805a000.r-x.sdmp	JoeSecurity_Okiru	Yara detected Okiru	Joe Security
6253.1.0000000008048000.000000000805a000.r-x.sdmp	JoeSecurity_Mirai_9	Yara detected Mirai	Joe Security
6253.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
6253.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
6253.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
6253.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
6253.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
6253.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
6253.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_88de437f	unknown	unknown	0x96e2:$a: 24 08 8B 4C 24 04 85 D2 74 0D 31 C0 89 F6 C6 04 08 00 40 39 D0
6253.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
6253.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_389ee3e9	unknown	unknown	0xccab:$a: 89 45 00 EB 2C 8B 4B 04 8B 13 8B 7B 18 8B 01 01 02 8B 02 83
6253.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_cc93863b	unknown	unknown	0xb5b0:$a: C3 57 8B 44 24 0C 8B 4C 24 10 8B 7C 24 08 F3 AA 8B 44 24 08
6253.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_8aa7b5d3	unknown	unknown	0x96b2:$a: 8B 4C 24 14 8B 74 24 0C 8B 5C 24 10 85 C9 74 0D 31 D2 8A 04 1A 88
6253.1.0000000008048000.000000000805a000.r-x.sdmp	Mirai_Botnet_Malware	Detects Mirai Botnet Malware	Florian Roth	0xea80:$x1: POST /cdn-cgi/ 0xfdb0:$s1: LCOGQGPTGP
6250.1.0000000008048000.000000000805a000.r-x.sdmp	JoeSecurity_Okiru	Yara detected Okiru	Joe Security
6250.1.0000000008048000.000000000805a000.r-x.sdmp	JoeSecurity_Mirai_9	Yara detected Mirai	Joe Security
6250.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
6250.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
6250.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
6250.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
6250.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
6250.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
6250.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_88de437f	unknown	unknown	0x96e2:$a: 24 08 8B 4C 24 04 85 D2 74 0D 31 C0 89 F6 C6 04 08 00 40 39 D0
6250.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
6250.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_389ee3e9	unknown	unknown	0xccab:$a: 89 45 00 EB 2C 8B 4B 04 8B 13 8B 7B 18 8B 01 01 02 8B 02 83
6250.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_cc93863b	unknown	unknown	0xb5b0:$a: C3 57 8B 44 24 0C 8B 4C 24 10 8B 7C 24 08 F3 AA 8B 44 24 08
6250.1.0000000008048000.000000000805a000.r-x.sdmp	Linux_Trojan_Mirai_8aa7b5d3	unknown	unknown	0x96b2:$a: 8B 4C 24 14 8B 74 24 0C 8B 5C 24 10 85 C9 74 0D 31 D2 8A 04 1A 88
6250.1.0000000008048000.000000000805a000.r-x.sdmp	Mirai_Botnet_Malware	Detects Mirai Botnet Malware	Florian Roth	0xea80:$x1: POST /cdn-cgi/ 0xfdb0:$s1: LCOGQGPTGP
Process Memory Space: byte.x86.elf PID: 6247	JoeSecurity_Okiru	Yara detected Okiru	Joe Security
Process Memory Space: byte.x86.elf PID: 6247	JoeSecurity_Mirai_9	Yara detected Mirai	Joe Security
Process Memory Space: byte.x86.elf PID: 6250	JoeSecurity_Okiru	Yara detected Okiru	Joe Security
Process Memory Space: byte.x86.elf PID: 6250	JoeSecurity_Mirai_9	Yara detected Mirai	Joe Security
Process Memory Space: byte.x86.elf PID: 6253	JoeSecurity_Okiru	Yara detected Okiru	Joe Security
Process Memory Space: byte.x86.elf PID: 6253	JoeSecurity_Mirai_9	Yara detected Mirai	Joe Security
Click to see the 43 entries

String: byte/proc//proc/%s/exe/proc/self/exe/proc/proc/%d/cmdlinenetstatwgettftpcurlreboot/bin/busyboxvar/Challengeapp/hi3511gmDVRiboxusr/dvr_main _8182T_1108mnt/mtd/app/guivar/Kylinl0 c/udevdvar/tmp/soniahicorestm_hi3511_dvr/usr/lib/systemd/systemdshellmnt/sys/boot/media/srv/var/run/sbin/lib/etc/dev/home/Davincitelnetsshwatchdog/var/spool/var/Sofiasshd/usr/compress/bin//compress/bin/compress/usr/bashhttpdtelnetddropbearencodersystem/root/dvr_gui//root/dvr_app//anko-app//opt/soraJoshohajime902i13BzSxLxBxeYHOHO-LUGO7HOHO-U79OLJuYfouyf87NiGGeR69xdSO190Ij1XLOLKIKEEEDDEekjheory98escansh4MDMAfdevalvexscanspcMELTEDNINJAREALZflexsonskidsscanx86MISAKI-U79OLfoAxi102kxeswodjwodjwojMmKiy7f87lfreecookiex86sysgpufrgegesysupdater0DnAzepdNiGGeRD0nks69frgreu0x766f6964NiGGeRd0nks1337gafturasgbsigboa120i3UI49OaF3geaevaiolmao123123aOfurain0n4H34DggTrexewwasads1293194hjXDOthLaLosnggtwget-log1337SoraLOADERSAIAKINAggtq1378bfp919GRB1Q2SAIAKUSOggtr14FaSEXSLAVE1337ggtt1902a3u912u3u4haetrghbr19ju3dSORAojkf120hehahejeje922U2JDJA901F91SlaVLav12helpmedaddthhhhh2wgg9qphbqSlav3Th3seD3viceshzSmYZjYMQ5GbfSoRAxD123LOLiaGv5aA3SoRAxD420LOLinsomni640277SoraBeReppin1337ipcamCache66tlGg9QjUYfouyf876ke3TOKYO3lyEeaXul2dULCVxh93OfjHZ2zTY2gD6MZvKc7KU6rmMkiy6f87lA023UU4U24UIUTheWeekndmioribitchesA5p9TheWeekndsmnblkjpoiAbAdTokyosnebAkiruU8inTznetstatsAlexW9RCAKM20TnewnetwordAyo215WordnloadsWordmanenotyakuzaaBelchWordnetsobpBigN0gg0r420X0102I34fofhasfhiafhoiX19I239124UIUoismXSHJEHHEIIHWOolsVNwo12DeportedDeportedXkTer0GbA1onry0v03FortniteDownLOLZY0urM0mGaypussyfartlmaojkGrAcEnIgGeRaNnYvdGkqndCOqGeoRBe6BEGuiltyCrownZEuS69s4beBsEQhdHOHO-KSNDOZEuz69sat1234aj93hJ23scanHAalie293z0k2LscanJoshoARMHellInSideayyyGangShitscanJoshoARM5HighFryb1glscanJoshoARM6IWhPyucDbJboatnetzscanJoshoARM7IuYgujeIqnbtbatrtahzexsexscanJoshoM68KJJDUHEWBBBIBscanJoshoMIPSJSDGIEVIVAVIGcKbVkzGOPascanJoshoMPSLccADscanJoshoPPCKAZEN-OIU97chickenxingsscanJoshoSH4yakuskzm8KAZEN-PO78HcleanerscanJoshoSPCKAZEN-U79OLdbeefscanJoshoX86yakuz4c24KETASHI32ddrwelperscanarm5zPnr6HpQj2Kaishi-Iz90Ydeexecscanarm6zdrtfxcgyKatrina32doCP3fVjscanarm7zxcfhuioKsif91je39scanm68kKuasadvrhelperl33t_feetl33tl33tfeetscanmipsKuasaBinsMateeQnOhRk85rscanmpslLOLHHHOHOHBUIeXK20CL12ZnyamezyQBotBladeSPOOKYhikariwasherep4029x91xx32uhj4gbejhwizardzhra.outboatnetcondiheroshimaskid.dbglzrdPownedSecurity69.aresfxlyazsxhyUNSTABLEmoobotjnsd9sdoilayourmomgaeissdfjiougsiojOasisSEGRJIJHFVNHSNHEIHFOSapep999KOWAI-BAdAsVKOWAI-SADjHKipU7Ylairdropmalwareyour_verry_fucking_gayBig-Bro-Brightsefaexecshirololieagle.For-Gai-Mezy0x6axNLcloqkisvspookymythSwergjmioGKILLEJW(IU(JIWERGFJGJWJRGHetrhwewrtheIuFdKssCxzjSDFJIjioOnrYoXd666ewrtkjokethajbdf89wu823AAaasrdgsWsGA4@F6FGhostWuzHere666BOGOMIPSbeastmodedvrHelperbestmodesfc6aJfIuYDemon.xeno-is-godICY-P-0ODIJgSHUIHIfhwrgLhu87VhvQPzlunadakuexecbinTacoBellGodYololigangExecutionorbitclientAmnesiaOwariUnHAnaAWz3hirobbomiorieagledoxxRollielessie.hax.yakuzawordminerminerwordSinixV4hohog0dbu7tuorphicfurasshuhorizonassailantAresKawaiihelperECHOBOTDEMONS

Source: global traffic

TCP traffic: 192.168.2.23:33872 -> 154.213.190.254:777

Source: /usr/sbin/rsyslogd (PID: 6289)	Reads hosts file: /etc/hosts	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6302)	Reads hosts file: /etc/hosts	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6383)	Reads hosts file: /etc/hosts	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6412)	Reads hosts file: /etc/hosts	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6425)	Reads hosts file: /etc/hosts	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6451)	Reads hosts file: /etc/hosts	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6462)	Reads hosts file: /etc/hosts	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6488)	Reads hosts file: /etc/hosts	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6500)	Reads hosts file: /etc/hosts	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6510)	Reads hosts file: /etc/hosts	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6520)	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: global traffic	DNS traffic detected: DNS query: vbtgsze.r-e.kr
Source: global traffic	DNS traffic detected: DNS query: daisy.ubuntu.com

Source: syslog.25.dr, syslog.198.dr, syslog.87.dr, syslog.133.dr, syslog.184.dr, syslog.101.dr, syslog.33.dr, syslog.53.dr, syslog.176.dr, syslog.141.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: byte.x86.elf, type: SAMPLE	Matched rule: Linux_Trojan_Mirai_fa3ad9d0 Author: unknown
Source: byte.x86.elf, type: SAMPLE	Matched rule: Linux_Trojan_Mirai_b14f4c5d Author: unknown
Source: byte.x86.elf, type: SAMPLE	Matched rule: Linux_Trojan_Mirai_93fc3657 Author: unknown
Source: byte.x86.elf, type: SAMPLE	Matched rule: Linux_Trojan_Mirai_804f8e7c Author: unknown
Source: byte.x86.elf, type: SAMPLE	Matched rule: Linux_Trojan_Mirai_99d78950 Author: unknown
Source: byte.x86.elf, type: SAMPLE	Matched rule: Linux_Trojan_Mirai_a68e498c Author: unknown
Source: byte.x86.elf, type: SAMPLE	Matched rule: Linux_Trojan_Mirai_88de437f Author: unknown
Source: byte.x86.elf, type: SAMPLE	Matched rule: Linux_Trojan_Mirai_ae9d0fa6 Author: unknown
Source: byte.x86.elf, type: SAMPLE	Matched rule: Linux_Trojan_Mirai_389ee3e9 Author: unknown
Source: byte.x86.elf, type: SAMPLE	Matched rule: Linux_Trojan_Mirai_cc93863b Author: unknown
Source: byte.x86.elf, type: SAMPLE	Matched rule: Linux_Trojan_Mirai_8aa7b5d3 Author: unknown
Source: byte.x86.elf, type: SAMPLE	Matched rule: Detects Mirai Botnet Malware Author: Florian Roth
Source: 6247.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_fa3ad9d0 Author: unknown
Source: 6247.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_b14f4c5d Author: unknown
Source: 6247.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_93fc3657 Author: unknown
Source: 6247.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_804f8e7c Author: unknown
Source: 6247.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_99d78950 Author: unknown
Source: 6247.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_a68e498c Author: unknown
Source: 6247.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_88de437f Author: unknown
Source: 6247.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_ae9d0fa6 Author: unknown
Source: 6247.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_389ee3e9 Author: unknown
Source: 6247.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_cc93863b Author: unknown
Source: 6247.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_8aa7b5d3 Author: unknown
Source: 6247.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Detects Mirai Botnet Malware Author: Florian Roth
Source: 6253.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_fa3ad9d0 Author: unknown
Source: 6253.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_b14f4c5d Author: unknown
Source: 6253.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_93fc3657 Author: unknown
Source: 6253.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_804f8e7c Author: unknown
Source: 6253.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_99d78950 Author: unknown
Source: 6253.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_a68e498c Author: unknown
Source: 6253.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_88de437f Author: unknown
Source: 6253.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_ae9d0fa6 Author: unknown
Source: 6253.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_389ee3e9 Author: unknown
Source: 6253.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_cc93863b Author: unknown
Source: 6253.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_8aa7b5d3 Author: unknown
Source: 6253.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Detects Mirai Botnet Malware Author: Florian Roth
Source: 6250.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_fa3ad9d0 Author: unknown
Source: 6250.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_b14f4c5d Author: unknown
Source: 6250.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_93fc3657 Author: unknown
Source: 6250.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_804f8e7c Author: unknown
Source: 6250.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_99d78950 Author: unknown
Source: 6250.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_a68e498c Author: unknown
Source: 6250.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_88de437f Author: unknown
Source: 6250.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_ae9d0fa6 Author: unknown
Source: 6250.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_389ee3e9 Author: unknown
Source: 6250.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_cc93863b Author: unknown
Source: 6250.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY	Matched rule: Linux_Trojan_Mirai_8aa7b5d3 Author: unknown
Source: 6250.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: 6249)	SIGKILL sent to PID below 1000: pid: 1 (init), result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 2, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 3, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 4, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 6, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 9, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 10, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 11, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 12, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 13, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 14, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 15, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 16, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 17, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 18, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 20, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 21, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 22, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 23, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 24, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 25, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 26, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 27, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 28, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 29, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 30, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 35, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 77, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 78, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 79, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 80, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 81, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 82, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 83, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 84, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 85, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 88, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 89, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 91, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 92, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 93, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 94, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 95, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 96, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 97, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 98, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 99, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 100, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 101, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 102, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 103, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 104, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 105, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 106, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 107, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 108, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 109, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 110, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 111, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 112, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 113, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 114, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 115, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 116, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 117, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 118, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 119, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 120, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 121, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 122, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 123, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 124, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 125, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 126, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 127, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 128, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 130, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 132, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 141, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 144, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 157, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 201, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 202, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 203, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 204, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 205, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 206, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 207, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 208, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 209, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 210, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 211, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 212, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 213, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 214, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 215, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 216, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 217, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 218, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 219, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 220, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 221, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 222, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 223, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 224, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 225, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 226, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 227, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 228, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 229, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 230, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 231, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 232, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 233, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 234, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 235, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 236, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 237, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 243, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 248, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 249, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 250, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 251, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 252, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 253, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 254, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 255, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 256, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 257, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 258, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 259, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 260, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 261, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 262, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 263, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 264, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 265, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 266, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 267, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 269, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 270, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 272, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 274, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 278, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 281, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 286, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 322, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 324, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 326, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 327, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 328, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 333, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 346, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 379, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 419, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 420, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 658, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 667, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 670, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 674, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 675, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 676, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 677, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 720, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 721, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 772, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 777, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 785, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 793, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 936, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 840, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 896, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent to PID below 1000: pid: 910, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 1 (init), result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 2, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 3, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 4, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 6, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 9, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 10, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 11, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 12, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 13, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 14, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 15, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 16, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 17, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 18, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 20, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 21, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 22, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 23, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 24, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 25, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 26, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 27, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 28, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 29, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 30, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 35, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 77, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 78, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 79, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 80, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 81, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 82, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 83, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 84, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 85, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 88, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 89, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 91, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 92, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 93, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 94, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 95, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 96, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 97, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 98, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 99, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 100, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 101, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 102, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 103, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 104, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 105, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 106, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 107, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 108, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 109, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 110, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 111, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 112, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 113, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 114, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 115, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 116, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 117, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 118, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 119, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 120, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 121, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 122, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 123, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 124, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 125, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 126, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 127, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 128, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 130, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 132, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 141, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 144, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 157, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 201, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 202, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 203, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 204, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 205, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 206, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 207, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 208, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 209, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 210, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 211, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 212, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 213, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 214, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 215, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 216, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 217, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 218, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 219, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 220, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 221, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 222, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 223, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 224, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 225, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 226, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 227, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 228, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 229, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 230, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 231, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 232, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 233, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 234, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 235, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 236, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 237, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 243, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 248, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 249, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 250, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 251, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 252, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 253, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 254, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 255, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 256, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 257, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 258, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 259, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 260, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 261, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 262, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 263, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 264, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 265, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 266, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 267, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 269, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 270, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 272, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 274, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 278, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 281, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 286, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 322, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 324, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 326, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 327, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 328, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 333, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 346, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 379, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 419, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 420, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 658, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 667, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 670, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 674, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 675, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 676, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 677, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 720, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 772, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 936, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 840, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent to PID below 1000: pid: 896, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	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: 6249)	SIGKILL sent: pid: 1 (init), result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 2, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 3, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 4, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 9, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 10, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 11, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 12, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 13, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 14, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 15, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 16, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 17, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 18, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 20, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 21, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 22, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 23, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 24, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 25, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 26, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 27, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 28, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 29, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 30, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 35, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 77, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 78, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 79, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 80, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 81, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 82, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 83, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 84, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 85, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 88, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 89, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 91, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 92, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 93, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 94, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 95, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 96, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 97, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 98, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 99, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 100, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 101, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 102, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 103, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 104, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 105, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 106, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 107, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 108, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 109, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 110, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 111, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 112, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 113, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 114, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 115, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 116, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 117, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 118, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 119, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 120, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 121, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 122, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 123, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 124, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 125, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 126, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 127, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 128, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 130, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 132, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 141, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 144, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 157, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 201, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 202, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 203, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 204, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 205, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 206, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 207, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 208, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 209, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 210, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 211, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 212, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 213, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 214, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 215, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 216, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 217, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 218, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 219, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 220, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 221, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 222, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 223, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 224, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 225, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 226, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 227, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 228, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 229, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 230, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 231, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 232, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 233, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 234, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 235, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 236, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 237, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 243, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 248, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 249, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 250, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 251, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 252, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 253, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 254, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 255, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 256, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 257, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 258, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 259, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 260, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 261, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 262, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 263, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 264, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 265, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 266, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 267, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 269, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 270, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 272, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 274, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 278, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 281, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 286, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 322, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 324, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 326, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 327, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 328, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 333, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 346, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 379, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 419, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 420, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 658, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 667, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 670, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 674, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 675, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 676, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 677, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 720, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 721, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 772, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 777, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 785, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 793, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 936, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 1207, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 1320, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 1344, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 1601, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 1886, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 1983, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 2048, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 2746, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 2749, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 2761, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 2882, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 3021, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 3088, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 4445, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 4446, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 4447, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 4448, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 4471, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 4480, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6226, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6284, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6287, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6288, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6289, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 840, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 896, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 910, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6301, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6302, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6303, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6304, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6409, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6424, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6425, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6426, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6427, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6431, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6451, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6452, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6453, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6461, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6462, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6463, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6464, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6468, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6484, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6486, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6488, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6489, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6490, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6498, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6499, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6500, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6501, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6505, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6509, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6510, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6511, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6512, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 1 (init), result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 2, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 3, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 4, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 9, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 10, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 11, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 12, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 13, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 14, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 15, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 16, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 17, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 18, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 20, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 21, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 22, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 23, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 24, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 25, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 26, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 27, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 28, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 29, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 30, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 35, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 77, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 78, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 79, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 80, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 81, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 82, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 83, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 84, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 85, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 88, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 89, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 91, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 92, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 93, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 94, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 95, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 96, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 97, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 98, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 99, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 100, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 101, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 102, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 103, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 104, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 105, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 106, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 107, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 108, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 109, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 110, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 111, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 112, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 113, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 114, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 115, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 116, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 117, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 118, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 119, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 120, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 121, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 122, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 123, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 124, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 125, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 126, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 127, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 128, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 130, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 132, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 141, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 144, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 157, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 201, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 202, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 203, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 204, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 205, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 206, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 207, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 208, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 209, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 210, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 211, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 212, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 213, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 214, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 215, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 216, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 217, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 218, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 219, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 220, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 221, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 222, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 223, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 224, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 225, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 226, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 227, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 228, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 229, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 230, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 231, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 232, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 233, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 234, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 235, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 236, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 237, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 243, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 248, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 249, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 250, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 251, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 252, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 253, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 254, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 255, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 256, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 257, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 258, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 259, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 260, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 261, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 262, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 263, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 264, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 265, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 266, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 267, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 269, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 270, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 272, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 274, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 278, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 281, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 286, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 322, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 324, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 326, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 327, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 328, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 333, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 346, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 379, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 419, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 420, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 658, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 667, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 670, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 674, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 675, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 676, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 677, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 720, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 772, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 936, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 1207, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 1320, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 1601, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 1983, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 2048, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 2746, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 2749, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 2761, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 2882, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 3021, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 3088, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 4445, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 4446, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 4447, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 4448, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 4471, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 4480, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 840, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 896, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 910, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6380, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6383, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6384, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6385, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6391, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6412, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6413, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6415, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6416, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6417, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6424, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6425, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6426, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6427, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6431, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6447, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6448, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6449, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6451, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6452, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6453, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6506, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6507, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6518, result: successful	Jump to behavior

Source: Initial sample	String containing 'busybox' found: /bin/busybox
Source: Initial sample	String containing 'busybox' found: busyboxxx
Source: Initial sample	String containing 'busybox' found: busyboxx
Source: Initial sample	String containing 'busybox' found: byte/proc//proc/%s/exe/proc/self/exe/proc/proc/%d/cmdlinenetstatwgettftpcurlreboot/bin/busyboxvar/Challengeapp/hi3511gmDVRiboxusr/dvr_main _8182T_1108mnt/mtd/app/guivar/Kylinl0 c/udevdvar/tmp/soniahicorestm_hi3511_dvr/usr/lib/systemd/systemdshellmnt/sys/boot/media/srv/var/run/sbin/lib/etc/dev/home/Davincitelnetsshwatchdog/var/spool/var/Sofiasshd/usr/compress/bin//compress/bin/compress/usr/bashhttpdtelnetddropbearencodersystem/root/dvr_gui//root/dvr_app//anko-app//opt/soraJoshohajime902i13BzSxLxBxeYHOHO-LUGO7HOHO-U79OLJuYfouyf87NiGGeR69xdSO190Ij1XLOLKIKEEEDDEekjheory98escansh4MDMAfdevalvexscanspcMELTEDNINJAREALZflexsonskidsscanx86MISAKI-U79OLfoAxi102kxeswodjwodjwojMmKiy7f87lfreecookiex86sysgpufrgegesysupdater0DnAzepdNiGGeRD0nks69frgreu0x766f6964NiGGeRd0nks1337gafturasgbsigboa120i3UI49OaF3geaevaiolmao123123aOfurain0n4H34DggTrexewwasads1293194hjXDOthLaLosnggtwget-log1337SoraLOADERSAIAKINAggtq1378bfp919GRB1Q2SAIAKUSOggtr14FaSEXSLAVE1337ggtt1902a3u912u3u4haetrghbr19ju3dSORAojkf120hehahejeje922U2JDJA901F91SlaVLav12

Source: ELF static info symbol of initial sample

.symtab present: no

Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 1 (init), result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 2, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 3, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 4, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 9, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 10, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 11, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 12, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 13, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 14, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 15, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 16, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 17, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 18, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 20, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 21, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 22, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 23, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 24, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 25, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 26, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 27, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 28, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 29, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 30, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 35, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 77, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 78, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 79, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 80, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 81, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 82, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 83, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 84, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 85, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 88, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 89, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 91, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 92, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 93, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 94, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 95, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 96, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 97, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 98, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 99, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 100, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 101, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 102, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 103, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 104, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 105, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 106, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 107, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 108, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 109, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 110, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 111, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 112, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 113, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 114, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 115, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 116, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 117, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 118, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 119, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 120, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 121, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 122, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 123, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 124, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 125, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 126, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 127, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 128, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 130, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 132, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 141, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 144, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 157, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 201, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 202, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 203, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 204, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 205, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 206, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 207, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 208, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 209, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 210, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 211, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 212, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 213, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 214, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 215, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 216, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 217, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 218, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 219, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 220, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 221, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 222, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 223, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 224, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 225, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 226, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 227, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 228, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 229, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 230, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 231, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 232, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 233, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 234, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 235, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 236, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 237, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 243, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 248, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 249, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 250, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 251, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 252, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 253, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 254, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 255, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 256, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 257, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 258, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 259, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 260, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 261, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 262, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 263, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 264, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 265, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 266, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 267, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 269, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 270, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 272, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 274, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 278, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 281, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 286, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 322, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 324, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 326, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 327, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 328, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 333, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 346, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 379, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 419, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 420, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 658, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 667, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 670, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 674, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 675, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 676, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 677, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 720, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 721, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 772, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 777, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 785, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 793, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 936, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 1207, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 1320, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 1344, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 1601, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 1886, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 1983, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 2048, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 2746, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 2749, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 2761, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 2882, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 3021, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 3088, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 4445, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 4446, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 4447, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 4448, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 4471, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 4480, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6226, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6284, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6287, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6288, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6289, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 840, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 896, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 910, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6301, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6302, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6303, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6304, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6409, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6424, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6425, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6426, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6427, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6431, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6451, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6452, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6453, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6461, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6462, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6463, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6464, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6468, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6484, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6486, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6488, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6489, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6490, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6498, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6499, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6500, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6501, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6505, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6509, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6510, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6511, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6249)	SIGKILL sent: pid: 6512, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 1 (init), result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 2, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 3, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 4, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 9, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 10, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 11, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 12, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 13, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 14, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 15, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 16, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 17, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 18, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 20, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 21, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 22, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 23, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 24, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 25, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 26, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 27, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 28, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 29, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 30, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 35, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 77, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 78, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 79, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 80, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 81, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 82, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 83, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 84, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 85, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 88, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 89, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 91, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 92, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 93, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 94, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 95, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 96, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 97, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 98, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 99, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 100, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 101, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 102, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 103, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 104, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 105, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 106, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 107, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 108, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 109, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 110, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 111, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 112, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 113, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 114, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 115, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 116, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 117, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 118, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 119, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 120, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 121, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 122, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 123, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 124, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 125, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 126, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 127, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 128, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 130, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 132, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 141, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 144, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 157, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 201, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 202, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 203, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 204, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 205, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 206, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 207, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 208, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 209, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 210, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 211, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 212, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 213, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 214, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 215, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 216, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 217, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 218, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 219, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 220, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 221, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 222, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 223, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 224, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 225, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 226, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 227, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 228, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 229, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 230, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 231, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 232, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 233, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 234, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 235, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 236, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 237, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 243, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 248, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 249, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 250, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 251, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 252, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 253, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 254, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 255, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 256, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 257, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 258, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 259, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 260, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 261, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 262, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 263, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 264, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 265, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 266, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 267, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 269, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 270, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 272, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 274, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 278, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 281, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 286, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 322, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 324, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 326, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 327, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 328, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 333, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 346, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 379, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 419, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 420, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 658, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 667, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 670, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 674, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 675, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 676, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 677, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 720, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 772, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 936, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 1207, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 1320, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 1601, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 1983, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 2048, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 2746, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 2749, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 2761, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 2882, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 3021, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 3088, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 4445, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 4446, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 4447, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 4448, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 4471, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 4480, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 840, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 896, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 910, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6380, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6383, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6384, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6385, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6391, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6412, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6413, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6415, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6416, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6417, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6424, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6425, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6426, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6427, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6431, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6447, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6448, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6449, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6451, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6452, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6453, result: no such process	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6506, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6507, result: successful	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	SIGKILL sent: pid: 6518, result: successful	Jump to behavior

Source: byte.x86.elf, type: SAMPLE	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: byte.x86.elf, type: SAMPLE	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: byte.x86.elf, type: SAMPLE	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: byte.x86.elf, type: SAMPLE	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: byte.x86.elf, type: SAMPLE	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: byte.x86.elf, type: SAMPLE	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: byte.x86.elf, type: SAMPLE	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: byte.x86.elf, type: SAMPLE	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: byte.x86.elf, type: SAMPLE	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: byte.x86.elf, type: SAMPLE	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: byte.x86.elf, type: SAMPLE	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: byte.x86.elf, type: SAMPLE	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: 6247.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: 6247.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: 6247.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: 6247.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: 6247.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: 6247.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: 6247.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: 6247.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: 6247.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: 6247.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: 6247.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: 6247.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: 6253.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: 6253.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: 6253.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: 6253.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: 6253.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: 6253.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: 6253.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: 6253.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: 6253.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: 6253.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: 6253.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: 6253.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: 6250.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: 6250.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: 6250.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: 6250.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: 6250.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: 6250.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: 6250.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: 6250.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: 6250.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: 6250.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: 6250.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: 6250.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: mal100.spre.troj.linELF@0/24@96/0

Persistence and Installation Behavior

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

Source: /usr/bin/dbus-daemon (PID: 6287)	File: /proc/6287/mounts	Jump to behavior
Source: /bin/fusermount (PID: 6290)	File: /proc/6290/mounts	Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6301)	File: /proc/6301/mounts	Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6380)	File: /proc/6380/mounts	Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6415)	File: /proc/6415/mounts	Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6424)	File: /proc/6424/mounts	Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6447)	File: /proc/6447/mounts	Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6461)	File: /proc/6461/mounts	Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6484)	File: /proc/6484/mounts	Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6498)	File: /proc/6498/mounts	Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6506)	File: /proc/6506/mounts	Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6509)	File: /proc/6509/mounts	Jump to behavior

Source: /lib/systemd/systemd-logind (PID: 6314)	Directory: <invalid fd (18)>/..	Jump to behavior
Source: /lib/systemd/systemd-logind (PID: 6314)	Directory: <invalid fd (17)>/..	Jump to behavior
Source: /lib/systemd/systemd-logind (PID: 6314)	File: /run/systemd/seats/.#seat0baEeJC	Jump to behavior
Source: /usr/lib/policykit-1/polkitd (PID: 6375)	Directory: /root/.cache	Jump to behavior
Source: /usr/lib/policykit-1/polkitd (PID: 6407)	Directory: /root/.cache	Jump to behavior
Source: /lib/systemd/systemd-logind (PID: 6566)	Directory: <invalid fd (18)>/..	Jump to behavior
Source: /lib/systemd/systemd-logind (PID: 6566)	Directory: <invalid fd (17)>/..	Jump to behavior
Source: /lib/systemd/systemd-logind (PID: 6566)	File: /run/systemd/seats/.#seat0r15kqI	Jump to behavior

Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6476/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/3088/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/230/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/110/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/231/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/111/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/232/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/112/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/233/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/113/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/234/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/1335/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/114/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/235/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/1334/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/2302/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/115/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/236/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/116/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/237/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/117/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/118/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/910/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/119/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6468/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6228/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/10/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/2307/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/11/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/12/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/13/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/14/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6484/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/15/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6487/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/16/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6486/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/17/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6489/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/18/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6488/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6360/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6481/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/120/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/121/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/1/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/122/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/243/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/123/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/2/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/124/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/3/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/4/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/125/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/126/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/248/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/127/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/128/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/249/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/9/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/20/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/21/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/22/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6252/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/23/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6251/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/24/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6254/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6375/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/25/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/26/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6256/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/27/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6255/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/28/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6258/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/29/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6257/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/491/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6490/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/250/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/130/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/251/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/252/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/132/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/253/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/254/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/255/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/256/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/257/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/1476/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/379/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/258/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/259/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6249/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/4502/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/936/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/30/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/2208/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6263/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6384/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6262/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/6383/cmdline	Jump to behavior
Source: /tmp/byte.x86.elf (PID: 6252)	File opened: /proc/35/cmdline	Jump to behavior

Source: /usr/bin/gpu-manager (PID: 6392)	Shell command executed: sh -c "grep -G \"^blacklist.nvidia[[:space:]]$\" /etc/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6395)	Shell command executed: sh -c "grep -G \"^blacklist.nvidia[[:space:]]$\" /lib/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6397)	Shell command executed: sh -c "grep -G \"^blacklist.radeon[[:space:]]$\" /etc/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6401)	Shell command executed: sh -c "grep -G \"^blacklist.radeon[[:space:]]$\" /lib/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6406)	Shell command executed: sh -c "grep -G \"^blacklist.amdgpu[[:space:]]$\" /etc/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6432)	Shell command executed: sh -c "grep -G \"^blacklist.nvidia[[:space:]]$\" /etc/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6435)	Shell command executed: sh -c "grep -G \"^blacklist.nvidia[[:space:]]$\" /lib/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6440)	Shell command executed: sh -c "grep -G \"^blacklist.radeon[[:space:]]$\" /etc/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6443)	Shell command executed: sh -c "grep -G \"^blacklist.radeon[[:space:]]$\" /lib/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6470)	Shell command executed: sh -c "grep -G \"^blacklist.nvidia[[:space:]]$\" /etc/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6472)	Shell command executed: sh -c "grep -G \"^blacklist.nvidia[[:space:]]$\" /lib/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6474)	Shell command executed: sh -c "grep -G \"^blacklist.radeon[[:space:]]$\" /etc/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6476)	Shell command executed: sh -c "grep -G \"^blacklist.radeon[[:space:]]$\" /lib/modprobe.d/*.conf"	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6483)	Shell command executed: sh -c "grep -G \"^blacklist.amdgpu[[:space:]]$\" /etc/modprobe.d/*.conf"	Jump to behavior

Source: /bin/sh (PID: 6394)	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: 6396)	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: 6398)	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: 6402)	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: 6408)	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: 6436)	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: 6441)	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: 6446)	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: 6471)	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: 6473)	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: 6475)	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: 6477)	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: /usr/share/gdm/generate-config (PID: 6414)	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: 6487)	Pkill executable: /usr/bin/pkill -> pkill --signal HUP --uid gdm dconf-service	Jump to behavior
Source: /usr/share/gdm/generate-config (PID: 6508)	Pkill executable: /usr/bin/pkill -> pkill --signal HUP --uid gdm dconf-service	Jump to behavior

Source: /usr/sbin/rsyslogd (PID: 6289)	Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6302)	Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6302)	Log file created: /var/log/auth.log
Source: /usr/sbin/rsyslogd (PID: 6383)	Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6383)	Log file created: /var/log/auth.log	Jump to dropped file
Source: /usr/sbin/rsyslogd (PID: 6412)	Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6425)	Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6451)	Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6462)	Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6488)	Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6500)	Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6510)	Log file created: /var/log/kern.log	Jump to dropped file

Source: /usr/bin/gpu-manager (PID: 6391)	Truncated file: /var/log/gpu-manager.log	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6431)	Truncated file: /var/log/gpu-manager.log	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6468)	Truncated file: /var/log/gpu-manager.log	Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6523)	Truncated file: /var/log/gpu-manager.log	Jump to behavior

Source: /usr/bin/pkill (PID: 6414)	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: 6487)	Reads CPU info from /sys: /sys/devices/system/cpu/online	Jump to behavior

Source: /usr/sbin/rsyslogd (PID: 6289)	Queries kernel information via 'uname':	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6302)	Queries kernel information via 'uname':	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6383)	Queries kernel information via 'uname':	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6412)	Queries kernel information via 'uname':	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6425)	Queries kernel information via 'uname':	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6451)	Queries kernel information via 'uname':	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6462)	Queries kernel information via 'uname':	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6488)	Queries kernel information via 'uname':	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6500)	Queries kernel information via 'uname':	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6510)	Queries kernel information via 'uname':	Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6520)	Queries kernel information via 'uname':	Jump to behavior

Stealing of Sensitive Information

Yara detected Mirai

Source: Yara match	File source: byte.x86.elf, type: SAMPLE
Source: Yara match	File source: 6247.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: 6253.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: 6250.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6247, type: MEMORYSTR
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6250, type: MEMORYSTR
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6253, type: MEMORYSTR

Yara detected Okiru

Source: Yara match	File source: byte.x86.elf, type: SAMPLE
Source: Yara match	File source: 6247.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: 6253.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: 6250.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6247, type: MEMORYSTR
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6250, type: MEMORYSTR
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6253, type: MEMORYSTR

Remote Access Functionality

Yara detected Mirai

Source: Yara match	File source: byte.x86.elf, type: SAMPLE
Source: Yara match	File source: 6247.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: 6253.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: 6250.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6247, type: MEMORYSTR
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6250, type: MEMORYSTR
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6253, type: MEMORYSTR

Yara detected Okiru

Source: Yara match	File source: byte.x86.elf, type: SAMPLE
Source: Yara match	File source: 6247.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: 6253.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: 6250.1.0000000008048000.000000000805a000.r-x.sdmp, type: MEMORY
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6247, type: MEMORYSTR
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6250, type: MEMORYSTR
Source: Yara match	File source: Process Memory Space: byte.x86.elf PID: 6253, 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	2 Scripting	Valid Accounts	Windows Management Instrumentation	2 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)	1 Indicator Removal	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	Binary Padding	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	74%	ReversingLabs	Linux.Trojan.Mirai
byte.x86.elf	67%	Virustotal		Browse
byte.x86.elf	100%	Avira	EXP/ELF.Mirai.M
byte.x86.elf	100%	Joe Sandbox ML

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

URLs from Memory and Binaries

Name	Source	Malicious	Antivirus Detection	Reputation
https://www.rsyslog.com	syslog.25.dr, syslog.198.dr, syslog.87.dr, syslog.133.dr, syslog.184.dr, syslog.101.dr, syslog.33.dr, syslog.53.dr, syslog.176.dr, syslog.141.dr	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.213.190.254	vbtgsze.r-e.kr	Seychelles	22769	DDOSING-BGP-NETWORKUS	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
154.213.190.254	byte.ppc.elf	Get hash	malicious	Mirai, Okiru	Browse
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	byte.ppc.elf	Get hash	malicious	Mirai, Okiru	Browse
	109.176.30.237-boatnet.mips-2024-12-27T21_21_18.elf	Get hash	malicious	Mirai	Browse
	mpsl.elf	Get hash	malicious	Unknown	Browse
	https://greensofttech1-my.sharepoint.com/:f:/g/personal/stella_huang_greensofttech1_onmicrosoft_com/EuOSopXBEUpFhaHAwqFRDM8BeWLY-Gsl0U9Az2fOy4x80A?e=GhPegT&xsdata=MDV8MDJ8TVB1Z2FAaHljaXRlLmNvbXxjMDM5NmJhZjcxOTM0YzBkMTc3ZDA4ZGQxMzcwNWQ3MnxmYzVjNjhmNjk3ZjM0ZWZlYjY4OWViNWMxMjM0ZjgyMXwwfDB8NjM4Njg4MDk1NTQ0NTA0NzA2fFVua25vd258VFdGcGJHWnNiM2Q4ZXlKRmJYQjBlVTFoY0draU9uUnlkV1VzSWxZaU9pSXdMakF1TURBd01DSXNJbEFpT2lKWGFXNHpNaUlzSWtGT0lqb2lUV0ZwYkNJc0lsZFVJam95ZlE9PXwwfHx8&sdata=SVpsejJNYUlwY213VjNreGxSNU1LaFJXcnpXS3pwWjhYR2k5ZUthLzlsMD0%3d	Get hash	malicious	HTMLPhisher	Browse
	Electrum-bch-4.4.2-x86_64.AppImage.elf	Get hash	malicious	Unknown	Browse
	mips.elf	Get hash	malicious	Unknown	Browse
	mips.elf	Get hash	malicious	Unknown	Browse
	byte.mpsl.elf	Get hash	malicious	Mirai, Okiru	Browse
	dlr.arm.elf	Get hash	malicious	Unknown	Browse
	byte.mpsl.elf	Get hash	malicious	Mirai, Okiru	Browse
91.189.91.42	byte.ppc.elf	Get hash	malicious	Mirai, Okiru	Browse
	109.176.30.237-boatnet.mips-2024-12-27T21_21_18.elf	Get hash	malicious	Mirai	Browse
	mpsl.elf	Get hash	malicious	Unknown	Browse
	https://greensofttech1-my.sharepoint.com/:f:/g/personal/stella_huang_greensofttech1_onmicrosoft_com/EuOSopXBEUpFhaHAwqFRDM8BeWLY-Gsl0U9Az2fOy4x80A?e=GhPegT&xsdata=MDV8MDJ8TVB1Z2FAaHljaXRlLmNvbXxjMDM5NmJhZjcxOTM0YzBkMTc3ZDA4ZGQxMzcwNWQ3MnxmYzVjNjhmNjk3ZjM0ZWZlYjY4OWViNWMxMjM0ZjgyMXwwfDB8NjM4Njg4MDk1NTQ0NTA0NzA2fFVua25vd258VFdGcGJHWnNiM2Q4ZXlKRmJYQjBlVTFoY0draU9uUnlkV1VzSWxZaU9pSXdMakF1TURBd01DSXNJbEFpT2lKWGFXNHpNaUlzSWtGT0lqb2lUV0ZwYkNJc0lsZFVJam95ZlE9PXwwfHx8&sdata=SVpsejJNYUlwY213VjNreGxSNU1LaFJXcnpXS3pwWjhYR2k5ZUthLzlsMD0%3d	Get hash	malicious	HTMLPhisher	Browse
	Electrum-bch-4.4.2-x86_64.AppImage.elf	Get hash	malicious	Unknown	Browse
	mips.elf	Get hash	malicious	Unknown	Browse
	mips.elf	Get hash	malicious	Unknown	Browse
	byte.mpsl.elf	Get hash	malicious	Mirai, Okiru	Browse
	dlr.arm.elf	Get hash	malicious	Unknown	Browse
	byte.mpsl.elf	Get hash	malicious	Mirai, Okiru	Browse

Domains

Match	Associated Sample Name / URL	SHA 256	Detection	Threat Name	Link	Context
daisy.ubuntu.com	byte.ppc.elf	Get hash	malicious	Mirai, Okiru	Browse	162.213.35.24
	109.176.30.237-boatnet.mpsl-2024-12-27T20_20_43.elf	Get hash	malicious	Mirai	Browse	162.213.35.24
	byte.mpsl.elf	Get hash	malicious	Mirai, Okiru	Browse	162.213.35.25
	byte.mpsl.elf	Get hash	malicious	Mirai, Okiru	Browse	162.213.35.25
	byte.ppc.elf	Get hash	malicious	Mirai, Okiru	Browse	162.213.35.25
	llklllklld.x86.elf	Get hash	malicious	Mirai, Okiru	Browse	162.213.35.25
	RpcSecurity.arm6.elf	Get hash	malicious	Unknown	Browse	162.213.35.24
	x86_64.nn.elf	Get hash	malicious	Okiru	Browse	162.213.35.24
	arm6.nn.elf	Get hash	malicious	Okiru	Browse	162.213.35.25
	arm5.nn.elf	Get hash	malicious	Okiru	Browse	162.213.35.24
vbtgsze.r-e.kr	byte.ppc.elf	Get hash	malicious	Mirai, Okiru	Browse	154.213.190.254
	byte.mpsl.elf	Get hash	malicious	Mirai, Okiru	Browse	154.213.190.246
	byte.mips.elf	Get hash	malicious	Mirai, Okiru	Browse	154.213.190.246
	drp.x86.elf	Get hash	malicious	Mirai, Okiru	Browse	154.213.190.246
	byte.arm7.elf	Get hash	malicious	Mirai, Okiru	Browse	154.213.190.246
	byte.arm.elf	Get hash	malicious	Mirai, Okiru	Browse	154.216.19.138
	byte.spc.elf	Get hash	malicious	Mirai, Okiru	Browse	154.216.19.138
	byte.m68k.elf	Get hash	malicious	Mirai, Okiru	Browse	154.216.19.138
	byte.sh4.elf	Get hash	malicious	Mirai, Okiru	Browse	154.216.19.138
	byte.x86.elf	Get hash	malicious	Mirai, Okiru	Browse	154.216.19.138

ASNs

Match	Associated Sample Name / URL	SHA 256	Detection	Threat Name	Link	Context
CANONICAL-ASGB	byte.ppc.elf	Get hash	malicious	Mirai, Okiru	Browse	91.189.91.42
	109.176.30.237-boatnet.mips-2024-12-27T21_21_18.elf	Get hash	malicious	Mirai	Browse	91.189.91.42
	109.176.30.237-boatnet.mpsl-2024-12-27T20_20_43.elf	Get hash	malicious	Mirai	Browse	185.125.190.26
	mpsl.elf	Get hash	malicious	Unknown	Browse	91.189.91.42
	https://greensofttech1-my.sharepoint.com/:f:/g/personal/stella_huang_greensofttech1_onmicrosoft_com/EuOSopXBEUpFhaHAwqFRDM8BeWLY-Gsl0U9Az2fOy4x80A?e=GhPegT&xsdata=MDV8MDJ8TVB1Z2FAaHljaXRlLmNvbXxjMDM5NmJhZjcxOTM0YzBkMTc3ZDA4ZGQxMzcwNWQ3MnxmYzVjNjhmNjk3ZjM0ZWZlYjY4OWViNWMxMjM0ZjgyMXwwfDB8NjM4Njg4MDk1NTQ0NTA0NzA2fFVua25vd258VFdGcGJHWnNiM2Q4ZXlKRmJYQjBlVTFoY0draU9uUnlkV1VzSWxZaU9pSXdMakF1TURBd01DSXNJbEFpT2lKWGFXNHpNaUlzSWtGT0lqb2lUV0ZwYkNJc0lsZFVJam95ZlE9PXwwfHx8&sdata=SVpsejJNYUlwY213VjNreGxSNU1LaFJXcnpXS3pwWjhYR2k5ZUthLzlsMD0%3d	Get hash	malicious	HTMLPhisher	Browse	91.189.91.42
	Electrum-bch-4.4.2-x86_64.AppImage.elf	Get hash	malicious	Unknown	Browse	91.189.91.42
	mips.elf	Get hash	malicious	Unknown	Browse	91.189.91.42
	mips.elf	Get hash	malicious	Unknown	Browse	91.189.91.42
	byte.mpsl.elf	Get hash	malicious	Mirai, Okiru	Browse	91.189.91.42
	drp.x86.elf	Get hash	malicious	Mirai, Okiru	Browse	185.125.190.26
DDOSING-BGP-NETWORKUS	byte.ppc.elf	Get hash	malicious	Mirai, Okiru	Browse	154.213.190.254
	byte.mpsl.elf	Get hash	malicious	Mirai, Okiru	Browse	154.213.190.246
	byte.mips.elf	Get hash	malicious	Mirai, Okiru	Browse	154.213.190.246
	drp.x86.elf	Get hash	malicious	Mirai, Okiru	Browse	154.213.190.246
	byte.arm7.elf	Get hash	malicious	Mirai, Okiru	Browse	154.213.190.246
	byte.mpsl.elf	Get hash	malicious	Mirai, Okiru	Browse	154.213.190.246
	byte.ppc.elf	Get hash	malicious	Mirai, Okiru	Browse	154.213.190.246
	llklllklld.x86.elf	Get hash	malicious	Mirai, Okiru	Browse	154.213.190.246
	87.120.127.227-arm-2024-12-25T12_37_29.elf	Get hash	malicious	Unknown	Browse	154.213.187.125
	jackmymips.elf	Get hash	malicious	Gafgyt, Mirai	Browse	154.213.186.115
INIT7CH	byte.ppc.elf	Get hash	malicious	Mirai, Okiru	Browse	109.202.202.202
	109.176.30.237-boatnet.mips-2024-12-27T21_21_18.elf	Get hash	malicious	Mirai	Browse	109.202.202.202
	mpsl.elf	Get hash	malicious	Unknown	Browse	109.202.202.202
	https://greensofttech1-my.sharepoint.com/:f:/g/personal/stella_huang_greensofttech1_onmicrosoft_com/EuOSopXBEUpFhaHAwqFRDM8BeWLY-Gsl0U9Az2fOy4x80A?e=GhPegT&xsdata=MDV8MDJ8TVB1Z2FAaHljaXRlLmNvbXxjMDM5NmJhZjcxOTM0YzBkMTc3ZDA4ZGQxMzcwNWQ3MnxmYzVjNjhmNjk3ZjM0ZWZlYjY4OWViNWMxMjM0ZjgyMXwwfDB8NjM4Njg4MDk1NTQ0NTA0NzA2fFVua25vd258VFdGcGJHWnNiM2Q4ZXlKRmJYQjBlVTFoY0draU9uUnlkV1VzSWxZaU9pSXdMakF1TURBd01DSXNJbEFpT2lKWGFXNHpNaUlzSWtGT0lqb2lUV0ZwYkNJc0lsZFVJam95ZlE9PXwwfHx8&sdata=SVpsejJNYUlwY213VjNreGxSNU1LaFJXcnpXS3pwWjhYR2k5ZUthLzlsMD0%3d	Get hash	malicious	HTMLPhisher	Browse	109.202.202.202
	Electrum-bch-4.4.2-x86_64.AppImage.elf	Get hash	malicious	Unknown	Browse	109.202.202.202
	mips.elf	Get hash	malicious	Unknown	Browse	109.202.202.202
	mips.elf	Get hash	malicious	Unknown	Browse	109.202.202.202
	byte.mpsl.elf	Get hash	malicious	Mirai, Okiru	Browse	109.202.202.202
	dlr.arm.elf	Get hash	malicious	Unknown	Browse	109.202.202.202
	byte.mpsl.elf	Get hash	malicious	Mirai, Okiru	Browse	109.202.202.202

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/.#seat0r15kqI

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):	293
Entropy (8bit):	4.964566851866874
Encrypted:	false
SSDEEP:	6:eSF6+fOCnAvmYqSF6+fOCnAbKRkFVtqSF6+fP2kj4:DF7Avm+F7A2+VBFZY
MD5:	B08E495D704697DEEEDB111779704DFB
SHA1:	3A9B3FDFDF1918267FF985CF68481DBE87B5D4C3
SHA-256:	8E1F5F5438B9B678123E2D830B025BAB5C1110CEBB32BC2526F2EFBDF2D1EF30
SHA-512:	8BC3F1D279E041C8280588AE0D1BD4ADD45CFFCC557974036059C5337C35D9D6AF5225E31D2849C70CC868438C48B5A7E8BE2170B77351CAD49D09FE8B52F756
Malicious:	false
Reputation:	low
Preview:	Dec 27 19:22:48 galassia systemd-logind[6314]: Watching system buttons on /dev/input/event0 (Power Button).Dec 27 19:22:48 galassia systemd-logind[6314]: Watching system buttons on /dev/input/event1 (AT Translated Set 2 keyboard).Dec 27 19:22:48 galassia systemd-logind[6314]: New seat seat0..

/var/log/kern.log

Download File

Process:	/usr/sbin/rsyslogd
File Type:	ASCII text
Category:	dropped
Size (bytes):	1594
Entropy (8bit):	4.760848721532706
Encrypted:	false
SSDEEP:	48:4alMsmVaN8IbqlMBIJ34wi4m3T2MWB0EuekpeLl2:RsMsiFv9b
MD5:	1CF2F3BC9158C192FA24AA7FB3846E5F
SHA1:	B20E249E12104AE40EDB1449C3D924C8295090F8
SHA-256:	7E9322ED1D0BFABCF2DCD6C65B58FAC6BB080E7E27E44B07D5B3A69EDB40F366
SHA-512:	5A134927A59975BE2A78311391EAEA42E8FF9F610C3844E2EAE6F72900D2196D07638C15117FD538C0FE3896460CFF5A3C78BAFE94141F9C9BCCA13711826985
Malicious:	false
Reputation:	low
Preview:	Dec 27 19:23:09 galassia kernel: [ 433.596641] blocking signal 9: 6249 -> 2048.Dec 27 19:23:09 galassia kernel: [ 433.772202] blocking signal 9: 6249 -> 1.Dec 27 19:23:09 galassia kernel: [ 433.784359] blocking signal 9: 6252 -> 658.Dec 27 19:23:09 galassia kernel: [ 433.805992] blocking signal 9: 6252 -> 720.Dec 27 19:23:09 galassia kernel: [ 433.809114] blocking signal 9: 6252 -> 772.Dec 27 19:23:09 galassia kernel: [ 433.825708] blocking signal 9: 6252 -> 936.Dec 27 19:23:09 galassia kernel: [ 433.832805] blocking signal 9: 6252 -> 1601.Dec 27 19:23:09 galassia kernel: [ 433.836381] blocking signal 9: 6252 -> 2048.Dec 27 19:23:09 galassia kernel: [ 433.846441] New task spawned: old: (tgid 6507, tid 6507), new (tgid: 6508, tid: 6508).Dec 27 19:23:09 galassia kernel: [ 434.020643] blocking signal 9: 6252 -> 1.Dec 27 19:23:09 galassia kernel: [ 434.546420] blocking signal 9: 6249 -> 658.Dec 27 19:23:09 galassia kernel: [ 434.581507] blocking signal 9: 6249 -> 720.Dec 27 19:

/var/log/syslog

Download File

Process:	/usr/sbin/rsyslogd
File Type:	ASCII text
Category:	dropped
Size (bytes):	4600
Entropy (8bit):	5.057192698232585
Encrypted:	false
SSDEEP:	48:w3sC6zHW0v30E3PXRo73WToU3U3UPh0V6V4VMalMsmVaN8IbqlMBIJ34wi4m3T2Z:XfXRCWTfEEZ0Y2vsMsiFxk9b
MD5:	AFF17320FEC2DB3FB7EC07EAA4207AFB
SHA1:	B7D4520141E11C1F547A7C1E9EC3335FDE05749D
SHA-256:	C636034005AB9B22D7A995D9E6A8D27245F0C526A8070C600A85E07575575593
SHA-512:	E5C2CA6E6F11CC5CC179F0BDC9DD70927334715C1794A45E6927CAC87CCB199D69556749C5ED7CDB407DCA14D8A1D1D8F411F5B7FE0255162162492752A24218
Malicious:	false
Reputation:	low
Preview:	Dec 27 19:23:09 galassia systemd[1]: rsyslog.service: Main process exited, code=killed, status=9/KILL.Dec 27 19:23:09 galassia systemd[1]: rsyslog.service: Failed with result 'signal'..Dec 27 19:23:09 galassia systemd[1]: whoopsie.service: Main process exited, code=killed, status=9/KILL.Dec 27 19:23:09 galassia systemd[1]: whoopsie.service: Failed with result 'signal'..Dec 27 19:23:09 galassia systemd[1]: gpu-manager.service: Main process exited, code=killed, status=9/KILL.Dec 27 19:23:09 galassia systemd[1]: gpu-manager.service: Failed with result 'signal'..Dec 27 19:23:09 galassia systemd[1]: Failed to start Detect the available GPUs and deal with any system changes..Dec 27 19:23:09 galassia systemd[1]: Starting GNOME Display Manager....Dec 27 19:23:09 galassia systemd[1]: dbus.service: Main process exited, code=killed, status=9/KILL.Dec 27 19:23:09 galassia systemd[1]: dbus.service: Failed with result 'signal'..Dec 27 19:23:09 galassia systemd[1]: whoopsie.service: Scheduled restart

Static File Info

General

File type:	ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, stripped
Entropy (8bit):	6.608849551891724
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:	75'088 bytes
MD5:	f7eef7a952b17ab75b3bb24d03fbcdf2
SHA1:	83bf20a36a93b73c1f78ff224459a797de605fa5
SHA256:	9928c99ec2ef2eee7df7c786dbc35f5b765e9701de45e194ab59123bdf535983
SHA512:	889239c925d90300423aa621777259f4d621fb232f5765b321a851e1815d1a54cc33b2535b2ab9662f08b3d8a8ddb6464a44f7f3ce3cda55a15a122b2611d2f1
SSDEEP:	1536:6SYXBbpKbF+5AQZKOtRDXVFx4bgMj+B3bEKoui0QOo/Y0TB3:SbobF+5QOth3+bgMj+xbyuPXopt3
TLSH:	EC736CC9A693E8F6FC160A751173FB325B77E17F2029CA83C7985D32D906A02E51239D
File Content Preview:	.ELF....................d...4....#......4. ...(..........................................................3..........Q.td............................U..S........'...h........[]...$.............U......=.....t..5...................u........t....h............

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 - System V
ABI Version:	0
Entry Point Address:	0x8048164
Flags:	0x0
ELF Header Size:	52
Program Header Offset:	52
Program Header Size:	32
Number of Program Headers:	3
Section Header Offset:	74688
Section Header Size:	40
Number of Section Headers:	10
Header String Table Index:	9

Sections

Name	Type	Address	Offset	Size	EntSize	Flags	Flags Description	Align
	NULL	0x0	0x0	0x0	0x0	0x0		0
.init	PROGBITS	0x8048094	0x94	0x1c	0x0	0x6	AX	1
.text	PROGBITS	0x80480b0	0xb0	0xe9a6	0x0	0x6	AX	16
.fini	PROGBITS	0x8056a56	0xea56	0x17	0x0	0x6	AX	1
.rodata	PROGBITS	0x8056a80	0xea80	0x2d1c	0x0	0x2	A	32
.ctors	PROGBITS	0x805a7a0	0x117a0	0x8	0x0	0x3	WA	4
.dtors	PROGBITS	0x805a7a8	0x117a8	0x8	0x0	0x3	WA	4
.data	PROGBITS	0x805a7c0	0x117c0	0xbc0	0x0	0x3	WA	32
.bss	NOBITS	0x805b380	0x12380	0x2800	0x0	0x3	WA	32
.shstrtab	STRTAB	0x0	0x12380	0x3e	0x0	0x0		1

Program Segments

Type	Offset	Virtual Address	Physical Address	File Size	Memory Size	Entropy	Flags	Flags Description	Align	Section Mappings
LOAD	0x0	0x8048000	0x8048000	0x1179c	0x1179c	6.6277	0x5	R E	0x1000	.init .text .fini .rodata
LOAD	0x117a0	0x805a7a0	0x805a7a0	0xbe0	0x33e0	4.9502	0x6	RW	0x1000	.ctors .dtors .data .bss
GNU_STACK	0x0	0x0	0x0	0x0	0x0	0.0000	0x6	RW	0x4

Timestamp	Source Port	Dest Port	Source IP	Dest IP
Dec 28, 2024 02:22:44.213501930 CET	33872	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:44.333153009 CET	777	33872	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:44.333230019 CET	33872	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:44.333295107 CET	33872	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:44.452858925 CET	777	33872	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:44.452924013 CET	33872	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:44.572513103 CET	777	33872	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:45.669197083 CET	777	33872	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:45.669292927 CET	33872	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:45.669375896 CET	33872	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:45.763633013 CET	43928	443	192.168.2.23	91.189.91.42
Dec 28, 2024 02:22:46.240550041 CET	33876	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:46.360070944 CET	777	33876	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:46.360148907 CET	33876	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:46.360176086 CET	33876	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:46.479760885 CET	777	33876	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:46.479821920 CET	33876	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:46.599431038 CET	777	33876	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:47.733819008 CET	777	33876	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:47.734004021 CET	33876	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:47.853518963 CET	777	33876	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:48.889266968 CET	33878	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:49.008822918 CET	777	33878	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:49.008892059 CET	33878	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:49.008930922 CET	33878	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:49.128460884 CET	777	33878	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:49.128519058 CET	33878	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:49.248167038 CET	777	33878	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:50.293292999 CET	777	33878	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:50.293359041 CET	33878	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:50.293391943 CET	33878	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:50.428169966 CET	33880	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:50.547691107 CET	777	33880	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:50.547770977 CET	33880	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:50.547796011 CET	33880	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:50.667392969 CET	777	33880	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:50.667577982 CET	33880	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:50.787080050 CET	777	33880	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:51.394831896 CET	42836	443	192.168.2.23	91.189.91.43
Dec 28, 2024 02:22:51.836761951 CET	777	33880	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:51.836961031 CET	33880	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:51.836961031 CET	33880	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:52.726416111 CET	33882	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:52.846010923 CET	777	33882	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:52.846085072 CET	33882	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:52.846141100 CET	33882	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:52.930593967 CET	42516	80	192.168.2.23	109.202.202.202
Dec 28, 2024 02:22:52.965665102 CET	777	33882	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:52.965713024 CET	33882	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:53.085247993 CET	777	33882	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:54.146146059 CET	777	33882	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:54.146205902 CET	33882	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:54.146246910 CET	33882	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:54.280054092 CET	33884	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:54.399715900 CET	777	33884	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:54.399801016 CET	33884	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:54.399801016 CET	33884	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:54.519471884 CET	777	33884	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:54.519530058 CET	33884	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:54.639023066 CET	777	33884	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:55.688503027 CET	777	33884	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:55.688607931 CET	33884	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:55.688608885 CET	33884	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:56.626198053 CET	33886	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:56.745789051 CET	777	33886	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:56.745876074 CET	33886	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:56.745959997 CET	33886	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:56.865413904 CET	777	33886	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:56.865500927 CET	33886	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:56.985001087 CET	777	33886	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:58.043997049 CET	777	33886	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:58.044092894 CET	33886	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:58.044092894 CET	33886	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:58.178167105 CET	33888	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:58.297751904 CET	777	33888	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:58.297828913 CET	33888	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:58.297887087 CET	33888	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:58.417397976 CET	777	33888	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:58.417468071 CET	33888	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:58.537013054 CET	777	33888	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:59.592210054 CET	777	33888	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:59.592282057 CET	33888	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:59.592282057 CET	33888	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:59.726763010 CET	33890	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:59.846335888 CET	777	33890	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:59.846434116 CET	33890	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:59.846435070 CET	33890	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:22:59.965953112 CET	777	33890	154.213.190.254	192.168.2.23
Dec 28, 2024 02:22:59.966018915 CET	33890	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:00.085640907 CET	777	33890	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:01.090784073 CET	777	33890	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:01.090912104 CET	33890	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:01.090912104 CET	33890	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:01.225131035 CET	33892	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:01.344655991 CET	777	33892	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:01.344741106 CET	33892	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:01.344741106 CET	33892	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:01.464291096 CET	777	33892	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:01.464358091 CET	33892	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:01.583844900 CET	777	33892	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:02.588078976 CET	777	33892	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:02.588148117 CET	33892	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:02.588148117 CET	33892	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:02.723195076 CET	33894	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:02.842679024 CET	777	33894	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:02.842730999 CET	33894	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:02.842750072 CET	33894	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:02.962421894 CET	777	33894	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:02.962477922 CET	33894	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:03.082227945 CET	777	33894	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:04.143958092 CET	777	33894	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:04.144010067 CET	33894	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:04.144037962 CET	33894	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:04.279020071 CET	33896	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:04.398556948 CET	777	33896	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:04.398621082 CET	33896	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:04.398659945 CET	33896	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:04.518138885 CET	777	33896	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:04.518224001 CET	33896	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:04.637715101 CET	777	33896	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:05.735030890 CET	777	33896	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:05.735104084 CET	33896	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:05.735155106 CET	33896	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:05.869050980 CET	33898	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:05.989068031 CET	777	33898	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:05.989140034 CET	33898	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:05.989181995 CET	33898	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:06.109019041 CET	777	33898	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:06.109080076 CET	33898	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:06.228686094 CET	777	33898	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:06.756757021 CET	43928	443	192.168.2.23	91.189.91.42
Dec 28, 2024 02:23:07.318269968 CET	777	33898	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:07.318340063 CET	33898	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:07.318382978 CET	33898	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:07.452965975 CET	33900	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:07.572626114 CET	777	33900	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:07.572686911 CET	33900	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:07.572725058 CET	33900	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:07.692291975 CET	777	33900	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:07.692343950 CET	33900	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:07.811866045 CET	777	33900	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:08.886151075 CET	777	33900	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:08.886215925 CET	33900	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:08.886251926 CET	33900	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:09.020260096 CET	33902	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:09.140177011 CET	777	33902	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:09.140269041 CET	33902	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:09.140311956 CET	33902	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:09.259783983 CET	777	33902	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:09.259840012 CET	33902	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:09.379407883 CET	777	33902	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:10.476314068 CET	777	33902	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:10.476396084 CET	33902	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:10.476396084 CET	33902	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:11.056129932 CET	33904	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:11.175904989 CET	777	33904	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:11.176027060 CET	33904	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:11.176027060 CET	33904	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:11.295855999 CET	777	33904	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:11.295922995 CET	33904	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:11.415687084 CET	777	33904	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:12.512640953 CET	777	33904	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:12.512720108 CET	33904	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:12.512720108 CET	33904	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:12.646756887 CET	33906	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:12.766416073 CET	777	33906	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:12.766484976 CET	33906	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:12.766536951 CET	33906	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:12.886037111 CET	777	33906	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:12.886101961 CET	33906	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:13.005623102 CET	777	33906	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:14.069835901 CET	777	33906	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:14.069905996 CET	33906	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:14.069941998 CET	33906	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:14.192883015 CET	33908	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:14.312591076 CET	777	33908	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:14.312652111 CET	33908	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:14.312685966 CET	33908	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:14.432244062 CET	777	33908	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:14.432373047 CET	33908	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:14.551937103 CET	777	33908	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:15.618670940 CET	777	33908	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:15.618772030 CET	33908	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:15.618772030 CET	33908	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:15.752878904 CET	33910	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:15.872499943 CET	777	33910	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:15.872570992 CET	33910	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:15.872612953 CET	33910	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:15.992163897 CET	777	33910	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:15.994508982 CET	33910	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:16.114304066 CET	777	33910	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:16.991300106 CET	42836	443	192.168.2.23	91.189.91.43
Dec 28, 2024 02:23:17.116149902 CET	777	33910	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:17.116236925 CET	33910	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:17.116236925 CET	33910	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:17.250315905 CET	33912	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:17.369867086 CET	777	33912	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:17.369926929 CET	33912	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:17.369961977 CET	33912	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:17.489597082 CET	777	33912	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:17.489650011 CET	33912	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:17.609217882 CET	777	33912	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:18.782421112 CET	777	33912	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:18.782471895 CET	33912	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:18.782497883 CET	33912	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:19.357652903 CET	33914	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:19.477260113 CET	777	33914	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:19.477327108 CET	33914	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:19.477349997 CET	33914	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:19.596842051 CET	777	33914	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:19.596884966 CET	33914	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:19.716389894 CET	777	33914	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:20.761748075 CET	777	33914	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:20.761806965 CET	33914	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:20.761833906 CET	33914	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:20.897845984 CET	33916	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:21.017394066 CET	777	33916	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:21.017462015 CET	33916	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:21.017509937 CET	33916	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:21.137187958 CET	777	33916	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:21.137239933 CET	33916	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:21.256810904 CET	777	33916	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:22.261589050 CET	777	33916	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:22.261643887 CET	33916	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:22.261682987 CET	33916	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:22.384251118 CET	33918	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:22.503885031 CET	777	33918	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:22.503947020 CET	33918	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:22.503978014 CET	33918	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:22.623511076 CET	777	33918	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:22.623557091 CET	33918	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:22.743072033 CET	777	33918	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:23.134450912 CET	42516	80	192.168.2.23	109.202.202.202
Dec 28, 2024 02:23:23.800738096 CET	777	33918	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:23.800798893 CET	33918	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:23.800842047 CET	33918	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:23.934654951 CET	33920	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:24.054158926 CET	777	33920	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:24.054225922 CET	33920	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:24.054305077 CET	33920	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:24.173731089 CET	777	33920	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:24.173779964 CET	33920	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:24.293318987 CET	777	33920	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:25.389981031 CET	777	33920	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:25.390045881 CET	33920	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:25.390079021 CET	33920	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:25.524283886 CET	33922	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:25.643831968 CET	777	33922	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:25.643892050 CET	33922	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:25.643940926 CET	33922	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:25.763402939 CET	777	33922	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:25.763449907 CET	33922	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:25.882919073 CET	777	33922	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:26.940462112 CET	777	33922	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:26.940516949 CET	33922	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:26.940551996 CET	33922	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:27.074834108 CET	33924	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:27.194355011 CET	777	33924	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:27.194406033 CET	33924	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:27.194473982 CET	33924	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:27.313927889 CET	777	33924	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:27.313971043 CET	33924	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:27.433582067 CET	777	33924	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:28.489782095 CET	777	33924	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:28.489836931 CET	33924	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:28.489877939 CET	33924	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:28.623852968 CET	33926	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:28.743504047 CET	777	33926	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:28.743556023 CET	33926	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:28.743587971 CET	33926	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:28.863178015 CET	777	33926	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:28.863241911 CET	33926	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:28.982942104 CET	777	33926	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:30.082974911 CET	777	33926	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:30.083040953 CET	33926	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:30.083087921 CET	33926	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:30.205583096 CET	33928	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:30.325222015 CET	777	33928	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:30.325278044 CET	33928	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:30.325295925 CET	33928	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:30.444830894 CET	777	33928	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:30.444884062 CET	33928	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:30.564371109 CET	777	33928	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:31.617321968 CET	777	33928	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:31.617386103 CET	33928	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:31.617424011 CET	33928	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:31.739856958 CET	33930	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:31.859349966 CET	777	33930	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:31.859400988 CET	33930	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:31.859436989 CET	33930	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:31.979079008 CET	777	33930	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:31.979120970 CET	33930	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:32.098612070 CET	777	33930	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:33.149144888 CET	777	33930	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:33.149195910 CET	33930	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:33.149233103 CET	33930	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:33.283029079 CET	33932	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:33.402591944 CET	777	33932	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:33.402664900 CET	33932	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:33.402664900 CET	33932	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:33.523509979 CET	777	33932	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:33.523565054 CET	33932	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:33.643022060 CET	777	33932	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:34.692440033 CET	777	33932	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:34.692511082 CET	33932	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:34.692589045 CET	33932	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:34.826390982 CET	33934	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:34.945890903 CET	777	33934	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:34.945962906 CET	33934	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:34.946010113 CET	33934	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:35.065530062 CET	777	33934	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:35.065608025 CET	33934	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:35.185312986 CET	777	33934	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:36.282313108 CET	777	33934	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:36.282396078 CET	33934	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:36.282397032 CET	33934	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:36.405014992 CET	33936	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:36.525477886 CET	777	33936	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:36.525548935 CET	33936	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:36.525583982 CET	33936	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:36.645175934 CET	777	33936	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:36.645237923 CET	33936	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:36.766151905 CET	777	33936	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:37.860527992 CET	777	33936	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:37.860593081 CET	33936	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:37.860630989 CET	33936	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:37.995136976 CET	33938	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:38.114869118 CET	777	33938	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:38.114940882 CET	33938	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:38.115003109 CET	33938	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:38.234595060 CET	777	33938	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:38.234647989 CET	33938	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:38.354176044 CET	777	33938	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:39.402038097 CET	777	33938	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:39.402098894 CET	33938	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:39.402136087 CET	33938	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:39.536484957 CET	33940	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:39.656008005 CET	777	33940	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:39.656069040 CET	33940	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:39.656112909 CET	33940	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:39.775760889 CET	777	33940	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:39.775841951 CET	33940	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:39.895443916 CET	777	33940	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:40.951756001 CET	777	33940	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:40.951816082 CET	33940	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:40.951852083 CET	33940	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:41.085824966 CET	33942	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:41.205518007 CET	777	33942	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:41.205569983 CET	33942	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:41.205600977 CET	33942	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:41.325401068 CET	777	33942	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:41.325448990 CET	33942	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:41.445034027 CET	777	33942	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:42.541815042 CET	777	33942	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:42.541877031 CET	33942	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:42.541924953 CET	33942	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:42.664381027 CET	33944	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:42.783993959 CET	777	33944	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:42.784073114 CET	33944	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:42.784145117 CET	33944	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:42.903620005 CET	777	33944	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:42.903671980 CET	33944	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:43.023180008 CET	777	33944	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:44.078355074 CET	777	33944	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:44.078449965 CET	33944	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:44.078449965 CET	33944	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:44.212908030 CET	33946	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:44.332442999 CET	777	33946	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:44.332504034 CET	33946	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:44.332540989 CET	33946	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:44.452035904 CET	777	33946	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:44.452096939 CET	33946	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:44.571789026 CET	777	33946	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:45.672346115 CET	777	33946	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:45.672449112 CET	33946	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:45.672449112 CET	33946	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:45.806376934 CET	33948	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:45.925980091 CET	777	33948	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:45.926028967 CET	33948	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:45.926057100 CET	33948	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:46.045547962 CET	777	33948	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:46.045608044 CET	33948	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:46.165323973 CET	777	33948	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:47.180442095 CET	777	33948	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:47.180514097 CET	33948	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:47.180565119 CET	33948	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:47.314714909 CET	33950	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:47.434353113 CET	777	33950	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:47.434420109 CET	33950	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:47.434485912 CET	33950	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:47.553982973 CET	777	33950	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:47.554039001 CET	33950	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:47.674365044 CET	777	33950	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:47.707053900 CET	43928	443	192.168.2.23	91.189.91.42
Dec 28, 2024 02:23:48.776048899 CET	777	33950	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:48.776114941 CET	33950	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:48.776149988 CET	33950	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:48.910011053 CET	33952	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:49.029530048 CET	777	33952	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:49.029603004 CET	33952	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:49.029634953 CET	33952	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:49.149302006 CET	777	33952	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:49.149373055 CET	33952	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:49.269123077 CET	777	33952	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:50.333978891 CET	777	33952	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:50.334041119 CET	33952	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:50.334076881 CET	33952	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:50.468003035 CET	33954	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:50.587605000 CET	777	33954	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:50.587666035 CET	33954	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:50.587704897 CET	33954	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:50.708467007 CET	777	33954	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:50.708513975 CET	33954	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:50.827956915 CET	777	33954	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:51.882755995 CET	777	33954	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:51.882826090 CET	33954	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:51.882855892 CET	33954	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:52.016674042 CET	33956	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:52.136233091 CET	777	33956	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:52.136301994 CET	33956	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:52.136343956 CET	33956	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:52.255867004 CET	777	33956	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:52.255928993 CET	33956	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:52.375529051 CET	777	33956	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:53.418529987 CET	777	33956	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:53.418579102 CET	33956	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:53.418606043 CET	33956	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:53.552531958 CET	33958	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:53.671967983 CET	777	33958	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:53.672025919 CET	33958	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:53.672046900 CET	33958	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:53.791502953 CET	777	33958	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:53.791553020 CET	33958	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:53.911065102 CET	777	33958	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:55.098161936 CET	777	33958	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:55.098217964 CET	33958	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:55.217678070 CET	777	33958	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:56.232585907 CET	33960	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:56.352082968 CET	777	33960	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:56.352169037 CET	33960	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:56.352169037 CET	33960	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:56.471766949 CET	777	33960	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:56.471817017 CET	33960	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:56.591242075 CET	777	33960	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:57.610236883 CET	777	33960	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:57.610296965 CET	33960	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:57.610349894 CET	33960	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:57.744168997 CET	33962	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:57.863974094 CET	777	33962	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:57.864037037 CET	33962	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:57.864067078 CET	33962	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:57.983644962 CET	777	33962	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:57.983702898 CET	33962	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:58.103202105 CET	777	33962	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:59.490087032 CET	777	33962	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:59.490153074 CET	33962	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:59.490186930 CET	33962	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:59.492019892 CET	777	33962	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:59.492084980 CET	33962	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:59.562414885 CET	777	33962	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:59.562482119 CET	33962	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:59.624500990 CET	33964	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:59.744137049 CET	777	33964	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:59.744194984 CET	33964	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:59.744210005 CET	33964	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:59.863756895 CET	777	33964	154.213.190.254	192.168.2.23
Dec 28, 2024 02:23:59.863826036 CET	33964	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:23:59.983465910 CET	777	33964	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:01.025250912 CET	777	33964	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:01.025311947 CET	33964	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:01.025311947 CET	33964	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:01.147872925 CET	33966	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:01.267380953 CET	777	33966	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:01.267441988 CET	33966	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:01.267487049 CET	33966	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:01.387186050 CET	777	33966	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:01.387233019 CET	33966	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:01.506685972 CET	777	33966	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:02.554271936 CET	777	33966	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:02.554322004 CET	33966	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:02.554343939 CET	33966	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:02.688080072 CET	33968	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:02.807657957 CET	777	33968	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:02.807717085 CET	33968	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:02.807743073 CET	33968	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:02.927323103 CET	777	33968	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:02.927369118 CET	33968	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:03.046988964 CET	777	33968	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:04.117383003 CET	777	33968	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:04.117443085 CET	33968	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:04.117464066 CET	33968	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:04.251936913 CET	33970	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:04.371582985 CET	777	33970	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:04.371639967 CET	33970	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:04.371669054 CET	33970	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:04.491230965 CET	777	33970	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:04.491281033 CET	33970	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:04.610800982 CET	777	33970	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:05.804071903 CET	777	33970	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:05.804147005 CET	33970	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:05.923754930 CET	777	33970	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:06.938745975 CET	33972	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:07.058276892 CET	777	33972	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:07.058334112 CET	33972	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:07.058357954 CET	33972	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:07.177917004 CET	777	33972	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:07.177974939 CET	33972	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:07.297561884 CET	777	33972	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:08.188225985 CET	42836	443	192.168.2.23	91.189.91.43
Dec 28, 2024 02:24:08.352754116 CET	777	33972	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:08.352811098 CET	33972	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:08.352843046 CET	33972	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:08.486720085 CET	33974	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:08.606379032 CET	777	33974	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:08.606439114 CET	33974	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:08.606475115 CET	33974	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:08.726106882 CET	777	33974	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:08.726161003 CET	33974	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:08.845721006 CET	777	33974	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:10.138247967 CET	777	33974	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:10.138318062 CET	33974	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:10.257778883 CET	777	33974	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:11.261473894 CET	33976	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:11.381050110 CET	777	33976	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:11.381108046 CET	33976	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:11.381128073 CET	33976	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:11.500754118 CET	777	33976	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:11.500808001 CET	33976	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:11.620384932 CET	777	33976	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:12.680819035 CET	777	33976	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:12.680883884 CET	33976	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:12.680917978 CET	33976	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:12.814649105 CET	33978	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:12.934288025 CET	777	33978	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:12.934349060 CET	33978	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:12.934376001 CET	33978	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:13.053991079 CET	777	33978	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:13.054042101 CET	33978	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:13.173556089 CET	777	33978	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:14.348721981 CET	777	33978	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:14.348790884 CET	33978	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:14.348831892 CET	33978	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:14.482759953 CET	33980	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:14.602338076 CET	777	33980	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:14.602396965 CET	33980	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:14.602418900 CET	33980	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:14.721980095 CET	777	33980	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:14.722037077 CET	33980	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:14.841581106 CET	777	33980	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:15.903740883 CET	777	33980	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:15.903803110 CET	33980	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:15.903803110 CET	33980	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:16.038347006 CET	33982	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:16.157955885 CET	777	33982	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:16.158026934 CET	33982	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:16.158077002 CET	33982	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:16.277621984 CET	777	33982	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:16.277704000 CET	33982	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:16.397300005 CET	777	33982	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:17.454989910 CET	777	33982	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:17.455159903 CET	33982	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:17.455159903 CET	33982	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:18.031678915 CET	33984	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:18.151527882 CET	777	33984	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:18.151583910 CET	33984	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:18.151629925 CET	33984	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:18.271215916 CET	777	33984	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:18.271269083 CET	33984	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:18.391053915 CET	777	33984	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:19.504205942 CET	777	33984	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:19.504290104 CET	33984	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:19.504290104 CET	33984	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:19.638361931 CET	33986	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:19.757936954 CET	777	33986	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:19.757994890 CET	33986	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:19.758012056 CET	33986	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:19.877697945 CET	777	33986	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:19.877747059 CET	33986	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:19.997324944 CET	777	33986	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:21.048683882 CET	777	33986	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:21.048754930 CET	33986	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:21.048784018 CET	33986	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:21.182745934 CET	33988	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:21.302443981 CET	777	33988	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:21.302524090 CET	33988	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:21.302547932 CET	33988	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:21.422200918 CET	777	33988	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:21.422257900 CET	33988	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:21.541848898 CET	777	33988	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:22.630558014 CET	777	33988	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:22.630621910 CET	33988	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:22.630662918 CET	33988	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:22.764633894 CET	33990	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:22.884206057 CET	777	33990	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:22.884265900 CET	33990	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:22.884294033 CET	33990	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:23.003988981 CET	777	33990	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:23.004074097 CET	33990	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:23.123826981 CET	777	33990	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:24.144216061 CET	777	33990	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:24.144293070 CET	33990	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:24.144293070 CET	33990	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:24.278188944 CET	33992	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:24.397872925 CET	777	33992	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:24.397926092 CET	33992	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:24.397950888 CET	33992	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:24.517532110 CET	777	33992	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:24.517577887 CET	33992	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:24.637244940 CET	777	33992	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:25.647274017 CET	777	33992	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:25.647325993 CET	33992	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:25.647341013 CET	33992	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:25.781188965 CET	33994	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:25.900794029 CET	777	33994	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:25.900892019 CET	33994	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:25.900908947 CET	33994	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:26.020530939 CET	777	33994	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:26.020610094 CET	33994	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:26.140413046 CET	777	33994	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:27.187849998 CET	777	33994	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:27.187912941 CET	33994	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:27.187912941 CET	33994	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:27.310450077 CET	33996	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:27.430078030 CET	777	33996	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:27.430135965 CET	33996	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:27.430147886 CET	33996	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:27.549720049 CET	777	33996	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:27.549778938 CET	33996	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:27.669373035 CET	777	33996	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:28.771142960 CET	777	33996	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:28.771204948 CET	33996	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:28.771259069 CET	33996	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:28.905031919 CET	33998	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:29.024580002 CET	777	33998	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:29.024641991 CET	33998	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:29.024663925 CET	33998	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:29.144277096 CET	777	33998	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:29.144334078 CET	33998	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:29.263928890 CET	777	33998	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:30.278264046 CET	777	33998	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:30.278323889 CET	33998	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:30.278379917 CET	33998	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:30.400974989 CET	34000	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:30.520590067 CET	777	34000	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:30.520661116 CET	34000	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:30.520713091 CET	34000	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:30.640264988 CET	777	34000	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:30.640324116 CET	34000	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:30.759916067 CET	777	34000	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:31.771276951 CET	777	34000	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:31.771342993 CET	34000	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:31.771365881 CET	34000	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:31.905827999 CET	34002	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:32.025543928 CET	777	34002	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:32.025599957 CET	34002	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:32.025625944 CET	34002	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:32.145405054 CET	777	34002	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:32.145446062 CET	34002	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:32.265026093 CET	777	34002	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:33.269684076 CET	777	34002	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:33.269747972 CET	34002	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:33.269777060 CET	34002	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:33.403718948 CET	34004	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:33.523408890 CET	777	34004	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:33.523467064 CET	34004	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:33.523482084 CET	34004	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:33.643066883 CET	777	34004	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:33.643114090 CET	34004	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:33.762667894 CET	777	34004	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:34.812999010 CET	777	34004	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:34.813059092 CET	34004	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:34.813079119 CET	34004	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:34.947474957 CET	34006	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:35.067085981 CET	777	34006	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:35.067138910 CET	34006	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:35.067153931 CET	34006	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:35.186968088 CET	777	34006	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:35.187017918 CET	34006	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:35.306607008 CET	777	34006	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:36.349540949 CET	777	34006	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:36.349596024 CET	34006	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:36.349615097 CET	34006	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:36.472141027 CET	34008	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:36.591849089 CET	777	34008	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:36.591914892 CET	34008	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:36.591960907 CET	34008	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:36.711618900 CET	777	34008	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:36.711679935 CET	34008	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:36.831242085 CET	777	34008	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:37.908380985 CET	777	34008	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:37.908442974 CET	34008	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:37.908442974 CET	34008	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:38.042583942 CET	34010	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:38.162256956 CET	777	34010	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:38.162334919 CET	34010	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:38.162334919 CET	34010	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:38.282075882 CET	777	34010	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:38.282135010 CET	34010	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:38.401700974 CET	777	34010	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:39.446427107 CET	777	34010	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:39.446501970 CET	34010	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:39.446501970 CET	34010	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:39.580656052 CET	34012	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:39.700242996 CET	777	34012	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:39.700293064 CET	34012	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:39.700314045 CET	34012	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:39.819895983 CET	777	34012	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:39.819947958 CET	34012	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:39.939627886 CET	777	34012	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:41.041697025 CET	777	34012	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:41.041764021 CET	34012	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:41.041789055 CET	34012	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:41.175996065 CET	34014	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:41.295619965 CET	777	34014	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:41.295669079 CET	34014	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:41.295684099 CET	34014	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:41.415307045 CET	777	34014	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:41.415369987 CET	34014	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:41.535012007 CET	777	34014	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:42.579065084 CET	777	34014	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:42.579128981 CET	34014	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:42.579157114 CET	34014	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:42.713644981 CET	34016	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:42.833280087 CET	777	34016	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:42.833343983 CET	34016	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:42.833365917 CET	34016	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:42.953021049 CET	777	34016	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:42.953071117 CET	34016	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:43.072714090 CET	777	34016	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:44.141314983 CET	777	34016	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:44.141386032 CET	34016	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:44.141386032 CET	34016	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:44.263906956 CET	34018	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:44.383493900 CET	777	34018	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:44.383565903 CET	34018	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:44.383565903 CET	34018	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:44.503170967 CET	777	34018	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:44.503276110 CET	34018	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:44.622843981 CET	777	34018	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:45.687012911 CET	777	34018	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:45.687067986 CET	34018	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:45.687093019 CET	34018	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:45.821146965 CET	34020	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:45.940721035 CET	777	34020	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:45.940782070 CET	34020	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:45.940798044 CET	34020	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:46.060336113 CET	777	34020	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:46.060381889 CET	34020	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:46.180119038 CET	777	34020	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:47.297322989 CET	777	34020	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:47.297378063 CET	34020	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:47.297400951 CET	34020	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:47.419869900 CET	34022	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:47.539397955 CET	777	34022	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:47.539499998 CET	34022	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:47.539516926 CET	34022	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:47.659157038 CET	777	34022	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:47.659204960 CET	34022	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:47.778754950 CET	777	34022	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:48.794974089 CET	777	34022	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:48.795032024 CET	34022	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:48.795056105 CET	34022	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:48.917599916 CET	34024	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:49.037401915 CET	777	34024	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:49.037491083 CET	34024	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:49.037491083 CET	34024	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:49.157136917 CET	777	34024	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:49.157212973 CET	34024	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:49.276776075 CET	777	34024	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:50.319195986 CET	777	34024	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:50.319287062 CET	34024	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:50.319287062 CET	34024	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:50.454118967 CET	34026	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:50.573700905 CET	777	34026	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:50.573776960 CET	34026	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:50.573776960 CET	34026	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:50.693366051 CET	777	34026	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:50.693429947 CET	34026	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:50.813061953 CET	777	34026	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:51.890372038 CET	777	34026	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:51.890444994 CET	34026	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:51.890444994 CET	34026	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:52.013195992 CET	34028	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:52.133218050 CET	777	34028	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:52.133281946 CET	34028	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:52.133308887 CET	34028	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:52.252971888 CET	777	34028	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:52.253024101 CET	34028	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:52.372965097 CET	777	34028	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:53.471343994 CET	777	34028	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:53.471404076 CET	34028	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:53.471441031 CET	34028	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:53.605201006 CET	34030	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:53.724859953 CET	777	34030	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:53.724920034 CET	34030	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:53.724941015 CET	34030	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:53.844489098 CET	777	34030	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:53.844552994 CET	34030	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:53.964216948 CET	777	34030	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:54.986310005 CET	777	34030	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:54.986368895 CET	34030	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:54.986391068 CET	34030	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:55.120980024 CET	34032	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:55.240639925 CET	777	34032	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:55.240705013 CET	34032	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:55.240736008 CET	34032	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:55.360299110 CET	777	34032	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:55.360359907 CET	34032	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:55.479959965 CET	777	34032	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:56.581748009 CET	777	34032	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:56.581811905 CET	34032	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:56.581851959 CET	34032	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:56.715612888 CET	34034	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:56.835272074 CET	777	34034	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:56.835331917 CET	34034	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:56.835354090 CET	34034	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:56.954938889 CET	777	34034	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:56.954988956 CET	34034	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:57.074533939 CET	777	34034	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:58.084647894 CET	777	34034	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:58.084722996 CET	34034	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:58.084788084 CET	34034	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:58.218888998 CET	34036	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:58.338584900 CET	777	34036	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:58.338649035 CET	34036	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:58.338649035 CET	34036	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:58.458350897 CET	777	34036	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:58.458406925 CET	34036	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:58.578058958 CET	777	34036	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:59.695839882 CET	777	34036	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:59.695913076 CET	34036	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:59.695913076 CET	34036	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:59.829695940 CET	34038	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:59.949713945 CET	777	34038	154.213.190.254	192.168.2.23
Dec 28, 2024 02:24:59.949779987 CET	34038	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:24:59.949779987 CET	34038	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:00.069832087 CET	777	34038	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:00.069885969 CET	34038	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:00.189644098 CET	777	34038	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:01.234020948 CET	777	34038	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:01.234093904 CET	34038	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:01.234093904 CET	34038	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:01.357215881 CET	34040	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:01.476965904 CET	777	34040	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:01.477035046 CET	34040	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:01.477102041 CET	34040	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:01.596707106 CET	777	34040	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:01.596771955 CET	34040	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:01.716357946 CET	777	34040	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:02.764117002 CET	777	34040	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:02.764174938 CET	34040	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:02.764203072 CET	34040	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:02.886743069 CET	34042	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:03.006391048 CET	777	34042	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:03.006447077 CET	34042	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:03.006458044 CET	34042	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:03.126386881 CET	777	34042	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:03.126434088 CET	34042	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:03.246401072 CET	777	34042	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:04.345330000 CET	777	34042	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:04.345386028 CET	34042	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:04.345412970 CET	34042	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:04.467984915 CET	34044	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:04.587594032 CET	777	34044	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:04.587646008 CET	34044	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:04.587663889 CET	34044	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:04.707257986 CET	777	34044	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:04.707317114 CET	34044	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:04.826919079 CET	777	34044	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:05.926743984 CET	777	34044	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:05.926810980 CET	34044	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:05.926851034 CET	34044	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:06.050385952 CET	34046	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:06.170911074 CET	777	34046	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:06.170969963 CET	34046	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:06.171001911 CET	34046	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:06.293617010 CET	777	34046	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:06.293683052 CET	34046	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:06.413300991 CET	777	34046	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:07.508388042 CET	777	34046	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:07.508452892 CET	34046	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:07.508517027 CET	34046	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:07.644125938 CET	34048	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:07.763700008 CET	777	34048	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:07.763761997 CET	34048	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:07.763781071 CET	34048	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:07.883388042 CET	777	34048	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:07.883435011 CET	34048	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:08.002981901 CET	777	34048	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:09.055058956 CET	777	34048	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:09.055119991 CET	34048	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:09.055135965 CET	34048	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:09.188813925 CET	34050	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:09.308517933 CET	777	34050	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:09.308578968 CET	34050	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:09.308597088 CET	34050	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:09.428251028 CET	777	34050	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:09.428297997 CET	34050	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:09.547835112 CET	777	34050	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:10.601378918 CET	777	34050	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:10.601430893 CET	34050	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:10.601454020 CET	34050	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:10.723961115 CET	34052	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:10.843565941 CET	777	34052	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:10.843626022 CET	34052	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:10.843672991 CET	34052	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:10.963598013 CET	777	34052	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:10.963653088 CET	34052	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:11.083270073 CET	777	34052	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:12.125925064 CET	777	34052	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:12.125987053 CET	34052	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:12.126080990 CET	34052	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:12.259860992 CET	34054	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:12.379390001 CET	777	34054	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:12.379456997 CET	34054	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:12.379456997 CET	34054	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:12.499598026 CET	777	34054	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:12.499660015 CET	34054	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:12.619879961 CET	777	34054	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:13.665676117 CET	777	34054	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:13.665744066 CET	34054	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:13.665844917 CET	34054	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:13.788275957 CET	34056	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:13.907843113 CET	777	34056	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:13.907896996 CET	34056	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:13.907921076 CET	34056	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:14.027553082 CET	777	34056	154.213.190.254	192.168.2.23
Dec 28, 2024 02:25:14.027601957 CET	34056	777	192.168.2.23	154.213.190.254
Dec 28, 2024 02:25:14.147111893 CET	777	34056	154.213.190.254	192.168.2.23

UDP Packets

Timestamp	Source Port	Dest Port	Source IP	Dest IP
Dec 28, 2024 02:22:43.259040117 CET	48498	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:22:44.213366985 CET	53	48498	8.8.8.8	192.168.2.23
Dec 28, 2024 02:22:45.669375896 CET	42303	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:22:46.240456104 CET	53	42303	8.8.8.8	192.168.2.23
Dec 28, 2024 02:22:48.755412102 CET	37294	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:22:48.889157057 CET	53	37294	8.8.8.8	192.168.2.23
Dec 28, 2024 02:22:48.967389107 CET	42238	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:22:48.967458963 CET	51166	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:22:49.089827061 CET	53	42238	8.8.8.8	192.168.2.23
Dec 28, 2024 02:22:49.089842081 CET	53	51166	8.8.8.8	192.168.2.23
Dec 28, 2024 02:22:50.293448925 CET	49472	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:22:50.427109957 CET	53	49472	8.8.8.8	192.168.2.23
Dec 28, 2024 02:22:51.837018967 CET	58288	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:22:52.726313114 CET	53	58288	8.8.8.8	192.168.2.23
Dec 28, 2024 02:22:52.921602964 CET	38610	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:22:53.043998957 CET	53	38610	8.8.8.8	192.168.2.23
Dec 28, 2024 02:22:54.146301985 CET	58578	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:22:54.279946089 CET	53	58578	8.8.8.8	192.168.2.23
Dec 28, 2024 02:22:55.688661098 CET	50150	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:22:56.626091003 CET	53	50150	8.8.8.8	192.168.2.23
Dec 28, 2024 02:22:58.044182062 CET	40771	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:22:58.178045034 CET	53	40771	8.8.8.8	192.168.2.23
Dec 28, 2024 02:22:59.372461081 CET	40975	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:22:59.495034933 CET	53	40975	8.8.8.8	192.168.2.23
Dec 28, 2024 02:22:59.592353106 CET	60028	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:22:59.726639032 CET	53	60028	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:01.090912104 CET	59340	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:01.225059032 CET	53	59340	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:02.588208914 CET	45669	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:02.723105907 CET	53	45669	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:04.144108057 CET	56109	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:04.278922081 CET	53	56109	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:05.735181093 CET	47636	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:05.868963003 CET	53	47636	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:07.318440914 CET	49184	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:07.452857971 CET	53	49184	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:08.886288881 CET	43608	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:09.020179033 CET	53	43608	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:10.476458073 CET	58441	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:11.055998087 CET	53	58441	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:12.512789965 CET	50134	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:12.646657944 CET	53	50134	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:14.070043087 CET	48662	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:14.192626953 CET	53	48662	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:15.618952990 CET	42146	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:15.752779961 CET	53	42146	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:17.116285086 CET	33087	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:17.250221968 CET	53	33087	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:18.782557964 CET	42748	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:19.357558966 CET	53	42748	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:20.761920929 CET	37709	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:20.897711039 CET	53	37709	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:22.261778116 CET	38857	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:22.384166956 CET	53	38857	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:23.800925970 CET	38821	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:23.934566021 CET	53	38821	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:25.390172958 CET	37476	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:25.524174929 CET	53	37476	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:26.940656900 CET	60289	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:27.074740887 CET	53	60289	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:28.489950895 CET	39621	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:28.623745918 CET	53	39621	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:30.083122969 CET	42944	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:30.205502033 CET	53	42944	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:31.617484093 CET	41329	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:31.739785910 CET	53	41329	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:33.149292946 CET	42988	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:33.282933950 CET	53	42988	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:34.692635059 CET	49707	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:34.826287031 CET	53	49707	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:36.282476902 CET	53662	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:36.404913902 CET	53	53662	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:37.860702991 CET	46905	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:37.994998932 CET	53	46905	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:39.402185917 CET	50934	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:39.536413908 CET	53	50934	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:40.951924086 CET	49449	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:41.085727930 CET	53	49449	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:42.541991949 CET	42802	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:42.664278984 CET	53	42802	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:44.078540087 CET	53573	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:44.212781906 CET	53	53573	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:45.672538996 CET	51555	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:45.806272030 CET	53	51555	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:47.180603027 CET	52081	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:47.314620018 CET	53	52081	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:48.776222944 CET	53720	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:48.909908056 CET	53	53720	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:50.334120989 CET	55271	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:50.467926025 CET	53	55271	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:51.882924080 CET	44811	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:52.016557932 CET	53	44811	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:53.418667078 CET	43284	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:53.552459955 CET	53	43284	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:56.098882914 CET	57560	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:56.232507944 CET	53	57560	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:57.610363007 CET	45985	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:57.744086027 CET	53	45985	8.8.8.8	192.168.2.23
Dec 28, 2024 02:23:59.490207911 CET	37750	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:23:59.624430895 CET	53	37750	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:01.025357962 CET	48737	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:01.147773027 CET	53	48737	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:02.554403067 CET	54701	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:02.687999010 CET	53	54701	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:04.117532969 CET	36282	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:04.251862049 CET	53	36282	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:06.804687023 CET	34202	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:06.938657045 CET	53	34202	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:08.352863073 CET	59213	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:08.486635923 CET	53	59213	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:11.138799906 CET	47603	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:11.261379957 CET	53	47603	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:12.680933952 CET	49632	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:12.814570904 CET	53	49632	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:14.348845959 CET	34869	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:14.482686043 CET	53	34869	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:15.903851032 CET	45308	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:16.038263083 CET	53	45308	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:17.455182076 CET	60544	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:18.031590939 CET	53	60544	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:19.504317999 CET	39943	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:19.638298035 CET	53	39943	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:21.048818111 CET	34549	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:21.182641983 CET	53	34549	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:22.630676985 CET	53427	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:22.764555931 CET	53	53427	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:24.144328117 CET	41639	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:24.278114080 CET	53	41639	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:25.647365093 CET	54335	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:25.781115055 CET	53	54335	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:27.187982082 CET	43328	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:27.310375929 CET	53	43328	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:28.771259069 CET	36019	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:28.904956102 CET	53	36019	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:30.278379917 CET	46764	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:30.400883913 CET	53	46764	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:31.771404028 CET	47277	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:31.905751944 CET	53	47277	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:33.269798040 CET	51344	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:33.403655052 CET	53	51344	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:34.813126087 CET	58620	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:34.947410107 CET	53	58620	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:36.349641085 CET	57826	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:36.472045898 CET	53	57826	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:37.908482075 CET	38235	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:38.042505980 CET	53	38235	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:39.446533918 CET	50591	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:39.580585957 CET	53	50591	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:41.041811943 CET	46798	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:41.175931931 CET	53	46798	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:42.579186916 CET	40577	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:42.713576078 CET	53	40577	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:44.141421080 CET	33269	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:44.263833046 CET	53	33269	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:45.687105894 CET	55930	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:45.821069002 CET	53	55930	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:47.297447920 CET	43891	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:47.419805050 CET	53	43891	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:48.795103073 CET	41470	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:48.917490959 CET	53	41470	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:50.319328070 CET	34927	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:50.454039097 CET	53	34927	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:51.890485048 CET	37039	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:52.013112068 CET	53	37039	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:53.471489906 CET	57018	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:53.605114937 CET	53	57018	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:54.986424923 CET	37111	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:55.120904922 CET	53	37111	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:56.581897974 CET	47590	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:56.715540886 CET	53	47590	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:58.084881067 CET	50851	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:58.218800068 CET	53	50851	8.8.8.8	192.168.2.23
Dec 28, 2024 02:24:59.695939064 CET	43763	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:24:59.829617977 CET	53	43763	8.8.8.8	192.168.2.23
Dec 28, 2024 02:25:01.234127998 CET	45669	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:25:01.357147932 CET	53	45669	8.8.8.8	192.168.2.23
Dec 28, 2024 02:25:02.764219999 CET	51087	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:25:02.886667013 CET	53	51087	8.8.8.8	192.168.2.23
Dec 28, 2024 02:25:04.345433950 CET	58081	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:25:04.467873096 CET	53	58081	8.8.8.8	192.168.2.23
Dec 28, 2024 02:25:05.926862955 CET	47310	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:25:06.050297976 CET	53	47310	8.8.8.8	192.168.2.23
Dec 28, 2024 02:25:07.508517027 CET	38870	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:25:07.644058943 CET	53	38870	8.8.8.8	192.168.2.23
Dec 28, 2024 02:25:09.055191040 CET	59104	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:25:09.188754082 CET	53	59104	8.8.8.8	192.168.2.23
Dec 28, 2024 02:25:10.601490021 CET	43256	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:25:10.723871946 CET	53	43256	8.8.8.8	192.168.2.23
Dec 28, 2024 02:25:12.126033068 CET	33586	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:25:12.259789944 CET	53	33586	8.8.8.8	192.168.2.23
Dec 28, 2024 02:25:13.665786028 CET	43242	53	192.168.2.23	8.8.8.8
Dec 28, 2024 02:25:13.788212061 CET	53	43242	8.8.8.8	192.168.2.23

ICMP Packets

Timestamp	Source IP	Dest IP	Checksum	Code	Type
Dec 28, 2024 02:22:53.654797077 CET	192.168.2.23	192.168.2.1	8283	(Port unreachable)	Destination Unreachable
Dec 28, 2024 02:24:13.670875072 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 28, 2024 02:22:43.259040117 CET	192.168.2.23	8.8.8.8	0xb9d8	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:22:45.669375896 CET	192.168.2.23	8.8.8.8	0xe636	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:22:48.755412102 CET	192.168.2.23	8.8.8.8	0xc1	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:22:48.967389107 CET	192.168.2.23	8.8.8.8	0xc325	Standard query (0)	daisy.ubuntu.com	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:22:48.967458963 CET	192.168.2.23	8.8.8.8	0xcc45	Standard query (0)	daisy.ubuntu.com	28	IN (0x0001)	false
Dec 28, 2024 02:22:50.293448925 CET	192.168.2.23	8.8.8.8	0xe196	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:22:51.837018967 CET	192.168.2.23	8.8.8.8	0xaf88	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:22:52.921602964 CET	192.168.2.23	8.8.8.8	0x5d8	Standard query (0)	daisy.ubuntu.com	28	IN (0x0001)	false
Dec 28, 2024 02:22:54.146301985 CET	192.168.2.23	8.8.8.8	0x8150	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:22:55.688661098 CET	192.168.2.23	8.8.8.8	0x44b1	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:22:58.044182062 CET	192.168.2.23	8.8.8.8	0x6c0c	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:22:59.372461081 CET	192.168.2.23	8.8.8.8	0xe87	Standard query (0)	daisy.ubuntu.com	28	IN (0x0001)	false
Dec 28, 2024 02:22:59.592353106 CET	192.168.2.23	8.8.8.8	0xcc12	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:01.090912104 CET	192.168.2.23	8.8.8.8	0x8b1	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:02.588208914 CET	192.168.2.23	8.8.8.8	0x302a	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:04.144108057 CET	192.168.2.23	8.8.8.8	0x17cb	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:05.735181093 CET	192.168.2.23	8.8.8.8	0xadba	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:07.318440914 CET	192.168.2.23	8.8.8.8	0x5ca6	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:08.886288881 CET	192.168.2.23	8.8.8.8	0x4076	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:10.476458073 CET	192.168.2.23	8.8.8.8	0xb323	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:12.512789965 CET	192.168.2.23	8.8.8.8	0xb092	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:14.070043087 CET	192.168.2.23	8.8.8.8	0xf248	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:15.618952990 CET	192.168.2.23	8.8.8.8	0xc082	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:17.116285086 CET	192.168.2.23	8.8.8.8	0xe996	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:18.782557964 CET	192.168.2.23	8.8.8.8	0xfc66	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:20.761920929 CET	192.168.2.23	8.8.8.8	0x6f1b	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:22.261778116 CET	192.168.2.23	8.8.8.8	0x1c52	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:23.800925970 CET	192.168.2.23	8.8.8.8	0xd0d7	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:25.390172958 CET	192.168.2.23	8.8.8.8	0xf945	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:26.940656900 CET	192.168.2.23	8.8.8.8	0x6133	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:28.489950895 CET	192.168.2.23	8.8.8.8	0xd54c	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:30.083122969 CET	192.168.2.23	8.8.8.8	0x9d0a	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:31.617484093 CET	192.168.2.23	8.8.8.8	0x4c48	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:33.149292946 CET	192.168.2.23	8.8.8.8	0xbc0c	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:34.692635059 CET	192.168.2.23	8.8.8.8	0x255f	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:36.282476902 CET	192.168.2.23	8.8.8.8	0xb852	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:37.860702991 CET	192.168.2.23	8.8.8.8	0xd4ca	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:39.402185917 CET	192.168.2.23	8.8.8.8	0x6879	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:40.951924086 CET	192.168.2.23	8.8.8.8	0x2c18	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:42.541991949 CET	192.168.2.23	8.8.8.8	0x858e	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:44.078540087 CET	192.168.2.23	8.8.8.8	0x5bf5	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:45.672538996 CET	192.168.2.23	8.8.8.8	0x885a	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:47.180603027 CET	192.168.2.23	8.8.8.8	0x11bf	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:48.776222944 CET	192.168.2.23	8.8.8.8	0xf2c1	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:50.334120989 CET	192.168.2.23	8.8.8.8	0xc519	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:51.882924080 CET	192.168.2.23	8.8.8.8	0x372c	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:53.418667078 CET	192.168.2.23	8.8.8.8	0x8e0a	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:56.098882914 CET	192.168.2.23	8.8.8.8	0x5391	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:57.610363007 CET	192.168.2.23	8.8.8.8	0x210e	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:59.490207911 CET	192.168.2.23	8.8.8.8	0xaae0	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:01.025357962 CET	192.168.2.23	8.8.8.8	0xb35e	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:02.554403067 CET	192.168.2.23	8.8.8.8	0xfe1	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:04.117532969 CET	192.168.2.23	8.8.8.8	0xa5d2	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:06.804687023 CET	192.168.2.23	8.8.8.8	0xdf2a	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:08.352863073 CET	192.168.2.23	8.8.8.8	0x76db	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:11.138799906 CET	192.168.2.23	8.8.8.8	0x1e35	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:12.680933952 CET	192.168.2.23	8.8.8.8	0x9383	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:14.348845959 CET	192.168.2.23	8.8.8.8	0xaddf	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:15.903851032 CET	192.168.2.23	8.8.8.8	0xc329	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:17.455182076 CET	192.168.2.23	8.8.8.8	0xe296	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:19.504317999 CET	192.168.2.23	8.8.8.8	0x1c54	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:21.048818111 CET	192.168.2.23	8.8.8.8	0x26c3	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:22.630676985 CET	192.168.2.23	8.8.8.8	0x4525	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:24.144328117 CET	192.168.2.23	8.8.8.8	0xa393	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:25.647365093 CET	192.168.2.23	8.8.8.8	0x5f47	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:27.187982082 CET	192.168.2.23	8.8.8.8	0x10e1	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:28.771259069 CET	192.168.2.23	8.8.8.8	0xde6b	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:30.278379917 CET	192.168.2.23	8.8.8.8	0xa492	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:31.771404028 CET	192.168.2.23	8.8.8.8	0x49c4	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:33.269798040 CET	192.168.2.23	8.8.8.8	0xfd6d	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:34.813126087 CET	192.168.2.23	8.8.8.8	0x45f3	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:36.349641085 CET	192.168.2.23	8.8.8.8	0x8d09	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:37.908482075 CET	192.168.2.23	8.8.8.8	0xf3ab	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:39.446533918 CET	192.168.2.23	8.8.8.8	0xde04	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:41.041811943 CET	192.168.2.23	8.8.8.8	0xea15	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:42.579186916 CET	192.168.2.23	8.8.8.8	0x342	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:44.141421080 CET	192.168.2.23	8.8.8.8	0x7961	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:45.687105894 CET	192.168.2.23	8.8.8.8	0x3788	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:47.297447920 CET	192.168.2.23	8.8.8.8	0xd674	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:48.795103073 CET	192.168.2.23	8.8.8.8	0x9a03	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:50.319328070 CET	192.168.2.23	8.8.8.8	0x3ea8	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:51.890485048 CET	192.168.2.23	8.8.8.8	0x231b	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:53.471489906 CET	192.168.2.23	8.8.8.8	0x2225	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:54.986424923 CET	192.168.2.23	8.8.8.8	0x11a3	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:56.581897974 CET	192.168.2.23	8.8.8.8	0x5ae3	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:58.084881067 CET	192.168.2.23	8.8.8.8	0x2cc3	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:59.695939064 CET	192.168.2.23	8.8.8.8	0xeabd	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:25:01.234127998 CET	192.168.2.23	8.8.8.8	0x2d1f	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:25:02.764219999 CET	192.168.2.23	8.8.8.8	0x8a3a	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:25:04.345433950 CET	192.168.2.23	8.8.8.8	0xb692	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:25:05.926862955 CET	192.168.2.23	8.8.8.8	0xbcc5	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:25:07.508517027 CET	192.168.2.23	8.8.8.8	0xc31d	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:25:09.055191040 CET	192.168.2.23	8.8.8.8	0xf6a	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:25:10.601490021 CET	192.168.2.23	8.8.8.8	0x5889	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:25:12.126033068 CET	192.168.2.23	8.8.8.8	0xc0a6	Standard query (0)	vbtgsze.r-e.kr	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:25:13.665786028 CET	192.168.2.23	8.8.8.8	0x4c45	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 28, 2024 02:22:44.213366985 CET	8.8.8.8	192.168.2.23	0xb9d8	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:22:46.240456104 CET	8.8.8.8	192.168.2.23	0xe636	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:22:48.889157057 CET	8.8.8.8	192.168.2.23	0xc1	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:22:49.089827061 CET	8.8.8.8	192.168.2.23	0xc325	No error (0)	daisy.ubuntu.com	162.213.35.25	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:22:49.089827061 CET	8.8.8.8	192.168.2.23	0xc325	No error (0)	daisy.ubuntu.com	162.213.35.24	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:22:50.427109957 CET	8.8.8.8	192.168.2.23	0xe196	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:22:52.726313114 CET	8.8.8.8	192.168.2.23	0xaf88	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:22:54.279946089 CET	8.8.8.8	192.168.2.23	0x8150	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:22:56.626091003 CET	8.8.8.8	192.168.2.23	0x44b1	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:22:58.178045034 CET	8.8.8.8	192.168.2.23	0x6c0c	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:22:59.726639032 CET	8.8.8.8	192.168.2.23	0xcc12	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:01.225059032 CET	8.8.8.8	192.168.2.23	0x8b1	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:02.723105907 CET	8.8.8.8	192.168.2.23	0x302a	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:04.278922081 CET	8.8.8.8	192.168.2.23	0x17cb	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:05.868963003 CET	8.8.8.8	192.168.2.23	0xadba	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:07.452857971 CET	8.8.8.8	192.168.2.23	0x5ca6	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:09.020179033 CET	8.8.8.8	192.168.2.23	0x4076	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:11.055998087 CET	8.8.8.8	192.168.2.23	0xb323	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:12.646657944 CET	8.8.8.8	192.168.2.23	0xb092	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:14.192626953 CET	8.8.8.8	192.168.2.23	0xf248	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:15.752779961 CET	8.8.8.8	192.168.2.23	0xc082	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:17.250221968 CET	8.8.8.8	192.168.2.23	0xe996	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:19.357558966 CET	8.8.8.8	192.168.2.23	0xfc66	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:20.897711039 CET	8.8.8.8	192.168.2.23	0x6f1b	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:22.384166956 CET	8.8.8.8	192.168.2.23	0x1c52	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:23.934566021 CET	8.8.8.8	192.168.2.23	0xd0d7	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:25.524174929 CET	8.8.8.8	192.168.2.23	0xf945	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:27.074740887 CET	8.8.8.8	192.168.2.23	0x6133	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:28.623745918 CET	8.8.8.8	192.168.2.23	0xd54c	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:30.205502033 CET	8.8.8.8	192.168.2.23	0x9d0a	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:31.739785910 CET	8.8.8.8	192.168.2.23	0x4c48	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:33.282933950 CET	8.8.8.8	192.168.2.23	0xbc0c	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:34.826287031 CET	8.8.8.8	192.168.2.23	0x255f	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:36.404913902 CET	8.8.8.8	192.168.2.23	0xb852	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:37.994998932 CET	8.8.8.8	192.168.2.23	0xd4ca	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:39.536413908 CET	8.8.8.8	192.168.2.23	0x6879	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:41.085727930 CET	8.8.8.8	192.168.2.23	0x2c18	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:42.664278984 CET	8.8.8.8	192.168.2.23	0x858e	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:44.212781906 CET	8.8.8.8	192.168.2.23	0x5bf5	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:45.806272030 CET	8.8.8.8	192.168.2.23	0x885a	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:47.314620018 CET	8.8.8.8	192.168.2.23	0x11bf	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:48.909908056 CET	8.8.8.8	192.168.2.23	0xf2c1	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:50.467926025 CET	8.8.8.8	192.168.2.23	0xc519	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:52.016557932 CET	8.8.8.8	192.168.2.23	0x372c	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:53.552459955 CET	8.8.8.8	192.168.2.23	0x8e0a	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:56.232507944 CET	8.8.8.8	192.168.2.23	0x5391	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:57.744086027 CET	8.8.8.8	192.168.2.23	0x210e	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:23:59.624430895 CET	8.8.8.8	192.168.2.23	0xaae0	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:01.147773027 CET	8.8.8.8	192.168.2.23	0xb35e	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:02.687999010 CET	8.8.8.8	192.168.2.23	0xfe1	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:04.251862049 CET	8.8.8.8	192.168.2.23	0xa5d2	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:06.938657045 CET	8.8.8.8	192.168.2.23	0xdf2a	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:08.486635923 CET	8.8.8.8	192.168.2.23	0x76db	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:11.261379957 CET	8.8.8.8	192.168.2.23	0x1e35	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:12.814570904 CET	8.8.8.8	192.168.2.23	0x9383	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:14.482686043 CET	8.8.8.8	192.168.2.23	0xaddf	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:16.038263083 CET	8.8.8.8	192.168.2.23	0xc329	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:18.031590939 CET	8.8.8.8	192.168.2.23	0xe296	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:19.638298035 CET	8.8.8.8	192.168.2.23	0x1c54	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:21.182641983 CET	8.8.8.8	192.168.2.23	0x26c3	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:22.764555931 CET	8.8.8.8	192.168.2.23	0x4525	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:24.278114080 CET	8.8.8.8	192.168.2.23	0xa393	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:25.781115055 CET	8.8.8.8	192.168.2.23	0x5f47	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:27.310375929 CET	8.8.8.8	192.168.2.23	0x10e1	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:28.904956102 CET	8.8.8.8	192.168.2.23	0xde6b	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:30.400883913 CET	8.8.8.8	192.168.2.23	0xa492	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:31.905751944 CET	8.8.8.8	192.168.2.23	0x49c4	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:33.403655052 CET	8.8.8.8	192.168.2.23	0xfd6d	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:34.947410107 CET	8.8.8.8	192.168.2.23	0x45f3	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:36.472045898 CET	8.8.8.8	192.168.2.23	0x8d09	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:38.042505980 CET	8.8.8.8	192.168.2.23	0xf3ab	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:39.580585957 CET	8.8.8.8	192.168.2.23	0xde04	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:41.175931931 CET	8.8.8.8	192.168.2.23	0xea15	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:42.713576078 CET	8.8.8.8	192.168.2.23	0x342	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:44.263833046 CET	8.8.8.8	192.168.2.23	0x7961	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:45.821069002 CET	8.8.8.8	192.168.2.23	0x3788	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:47.419805050 CET	8.8.8.8	192.168.2.23	0xd674	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:48.917490959 CET	8.8.8.8	192.168.2.23	0x9a03	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:50.454039097 CET	8.8.8.8	192.168.2.23	0x3ea8	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:52.013112068 CET	8.8.8.8	192.168.2.23	0x231b	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:53.605114937 CET	8.8.8.8	192.168.2.23	0x2225	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:55.120904922 CET	8.8.8.8	192.168.2.23	0x11a3	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:56.715540886 CET	8.8.8.8	192.168.2.23	0x5ae3	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:58.218800068 CET	8.8.8.8	192.168.2.23	0x2cc3	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:24:59.829617977 CET	8.8.8.8	192.168.2.23	0xeabd	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:25:01.357147932 CET	8.8.8.8	192.168.2.23	0x2d1f	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:25:02.886667013 CET	8.8.8.8	192.168.2.23	0x8a3a	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:25:04.467873096 CET	8.8.8.8	192.168.2.23	0xb692	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:25:06.050297976 CET	8.8.8.8	192.168.2.23	0xbcc5	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:25:07.644058943 CET	8.8.8.8	192.168.2.23	0xc31d	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:25:09.188754082 CET	8.8.8.8	192.168.2.23	0xf6a	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:25:10.723871946 CET	8.8.8.8	192.168.2.23	0x5889	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:25:12.259789944 CET	8.8.8.8	192.168.2.23	0xc0a6	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false
Dec 28, 2024 02:25:13.788212061 CET	8.8.8.8	192.168.2.23	0x4c45	No error (0)	vbtgsze.r-e.kr	154.213.190.254	A (IP address)	IN (0x0001)	false

System Behavior

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

General

Start time (UTC):	01:22:42
Start date (UTC):	28/12/2024
Path:	/tmp/byte.x86.elf
Arguments:	/tmp/byte.x86.elf
File size:	75088 bytes
MD5 hash:	f7eef7a952b17ab75b3bb24d03fbcdf2

Start time (UTC):	01:22:42
Start date (UTC):	28/12/2024
Path:	/tmp/byte.x86.elf
Arguments:	-
File size:	75088 bytes
MD5 hash:	f7eef7a952b17ab75b3bb24d03fbcdf2

Start time (UTC):	01:22:42
Start date (UTC):	28/12/2024
Path:	/tmp/byte.x86.elf
Arguments:	-
File size:	75088 bytes
MD5 hash:	f7eef7a952b17ab75b3bb24d03fbcdf2

Start time (UTC):	01:22:42
Start date (UTC):	28/12/2024
Path:	/tmp/byte.x86.elf
Arguments:	-
File size:	75088 bytes
MD5 hash:	f7eef7a952b17ab75b3bb24d03fbcdf2

Start time (UTC):	01:22:42
Start date (UTC):	28/12/2024
Path:	/tmp/byte.x86.elf
Arguments:	-
File size:	75088 bytes
MD5 hash:	f7eef7a952b17ab75b3bb24d03fbcdf2

Start time (UTC):	01:22:42
Start date (UTC):	28/12/2024
Path:	/tmp/byte.x86.elf
Arguments:	-
File size:	75088 bytes
MD5 hash:	f7eef7a952b17ab75b3bb24d03fbcdf2

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

Start time (UTC):	01:22:43
Start date (UTC):	28/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

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

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

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

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

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

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

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

Start time (UTC):	01:22:44
Start date (UTC):	28/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

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

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

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

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

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

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

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

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

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

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

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

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

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

Start time (UTC):	01:22:48
Start date (UTC):	28/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

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

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

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

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

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

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

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

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

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

Start time (UTC):	01:22:49
Start date (UTC):	28/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

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

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

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

Start time (UTC):	01:22:50
Start date (UTC):	28/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

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

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

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

Start time (UTC):	01:22:50
Start date (UTC):	28/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

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

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

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

Start time (UTC):	01:22:51
Start date (UTC):	28/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

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

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

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

Start time (UTC):	01:22:51
Start date (UTC):	28/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

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

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

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

Start time (UTC):	01:22:52
Start date (UTC):	28/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

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

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

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

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

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

Start time (UTC):	01:22:52
Start date (UTC):	28/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

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

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

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

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

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

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

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

Start time (UTC):	01:22:52
Start date (UTC):	28/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

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

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

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

Start time (UTC):	01:22:55
Start date (UTC):	28/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

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

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

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

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

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

Start time (UTC):	01:22:56
Start date (UTC):	28/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

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

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

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

Start time (UTC):	01:22:57
Start date (UTC):	28/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

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

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

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

Start time (UTC):	01:22:57
Start date (UTC):	28/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

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

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

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

Start time (UTC):	01:22:58
Start date (UTC):	28/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

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

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

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

Start time (UTC):	01:22:58
Start date (UTC):	28/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

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

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

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

Start time (UTC):	01:22:59
Start date (UTC):	28/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

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

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

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

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

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

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

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

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

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

Start time (UTC):	01:23:02
Start date (UTC):	28/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

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

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

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

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

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

Start time (UTC):	01:23:03
Start date (UTC):	28/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

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

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

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

Start time (UTC):	01:23:03
Start date (UTC):	28/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

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

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

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

Start time (UTC):	01:23:04
Start date (UTC):	28/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

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

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

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

Start time (UTC):	01:23:04
Start date (UTC):	28/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

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

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

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

Start time (UTC):	01:23:04
Start date (UTC):	28/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

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

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

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

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

General

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

Start time (UTC):	01:23:04
Start date (UTC):	28/12/2024
Path:	/usr/libexec/rtkit-daemon
Arguments:	/usr/libexec/rtkit-daemon
File size:	68096 bytes
MD5 hash:	df0cacf1db4ec95ac70f5b6e06b8ffd7

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

Start time (UTC):	01:23:05
Start date (UTC):	28/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

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

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

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

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

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

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

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

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

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

Start time (UTC):	01:23:07
Start date (UTC):	28/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

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

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

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

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

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

Start time (UTC):	01:23:08
Start date (UTC):	28/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

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

Start time (UTC):	01:23:09
Start date (UTC):	28/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

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

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

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

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

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

Start time (UTC):	01:23:09
Start date (UTC):	28/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

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

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

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

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

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

Start time (UTC):	01:23:10
Start date (UTC):	28/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

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

Start time (UTC):	01:23:10
Start date (UTC):	28/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

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

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

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

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

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

Start time (UTC):	01:23:10
Start date (UTC):	28/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

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

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

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

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

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

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

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

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

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

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

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

Start time (UTC):	01:23:12
Start date (UTC):	28/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

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

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

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

Start time (UTC):	01:23:13
Start date (UTC):	28/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

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

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

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

Start time (UTC):	01:23:14
Start date (UTC):	28/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

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

Start time (UTC):	01:23:14
Start date (UTC):	28/12/2024
Path:	/bin/plymouth
Arguments:	/bin/plymouth quit
File size:	51352 bytes
MD5 hash:	87003efd8dad470042f5e75360a8f49f

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

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

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

Start time (UTC):	01:24:17
Start date (UTC):	28/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: 6642, Parent PID: 1

General

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

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

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

Start time (UTC):	01:24:17
Start date (UTC):	28/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

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

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 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

Initial Sample

Memory Dumps

Suricata Signatures

Joe Sandbox Signatures

AV Detection

Bitcoin Miner

Spreading

Networking

System Summary

Persistence and Installation Behavior

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/.#seat0baEeJC

/run/systemd/seats/.#seat0r15kqI

/var/log/auth.log

/var/log/kern.log

/var/log/syslog

Static File Info

General

Static ELF Info

ELF header

Sections

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: 6247, Parent PID: 6163

General

Chronological Activities

Analysis Process: byte.x86.elf PID: 6249, Parent PID: 6247

General

Chronological Activities

Analysis Process: byte.x86.elf PID: 6250, Parent PID: 6247

General

Chronological Activities

Analysis Process: byte.x86.elf PID: 6251, Parent PID: 6247

Linux Analysis Report
byte.x86.elf