Linux Analysis Report
byte.sh4.elf

Overview

General Information

Sample name: byte.sh4.elf
Analysis ID: 1592445
MD5: 0ff51ad5f99061d5a3e0e5615c151e7f
SHA1: 0441409ce720fd05351e92953b6500bd145f0fe5
SHA256: 93be9d5dda433a702be271a68be68745ef1820b42487dcbc1bb5055d1d5f3529
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
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

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 https://malpedia.caad.fkie.fraunhofer.de/details/elf.mirai

AV Detection
barindex
Antivirus / Scanner detection for submitted sample
Source: byte.sh4.elf Avira: detected
Multi AV Scanner detection for submitted file
Source: byte.sh4.elf Virustotal: Detection: 61% Perma Link
Source: byte.sh4.elf ReversingLabs: Detection: 52%
Reads CPU information from /sys indicative of miner or evasive malware
Source: /usr/bin/pkill (PID: 6371) Reads CPU info from /sys: /sys/devices/system/cpu/online Jump to behavior
Source: /usr/bin/pkill (PID: 6481) Reads CPU info from /sys: /sys/devices/system/cpu/online Jump to behavior
Source: /usr/bin/pkill (PID: 6579) Reads CPU info from /sys: /sys/devices/system/cpu/online Jump to behavior
Source: /usr/bin/pkill (PID: 6598) Reads CPU info from /sys: /sys/devices/system/cpu/online Jump to behavior
Found strings indicative of a multi-platform dropper
Source: byte.sh4.elf String: ;httpurl=POST'=byte/proc//proc/%s/exe/proc/self/exe/proc/proc/%d/cmdlinenetstatwgettftpftpcurlbusyboxreboot/bin/busyboxvar/Challengeapp/hi3511gmDVRiboxusr/dvr_main _8182T_1108mnt/mtd/app/guivar/Kylinl0 c/udevdanko-app/ankosample _8182T_1104var/tmp/soniahicorestm_hi3511_dvr/usr/lib/systemd/systemd/usr/libexec/openssh/sftp-serverusr/shellmnt/sys/bin/boot/media/srv/var/run/sbin/lib/etc/dev/home/Davincitelnetsshwatchdog/var/spool/var/Sofiasshd/usr/compress/bin//compress/bin/compress/usr/bashhttpdtelnetddropbearropbearencodersystem/root/dvr_gui//root/dvr_app//anko-app//opt/soraJoshohajime902i13BzSxLxBxeYHOHO-LUGO7HOHO-U79OLJuYfouyf87NiGGeR69xdSO190Ij1XLOLKIKEEEDDEekjheory98escansh4MDMAfdevalvexscanspcMELTEDNINJAREALZflexsonskidsscanx86MISAKI-U79OLfoAxi102kxeswodjwodjwojMmKiy7f87lfreecookiex86sysgpufrgegesysupdater0DnAzepdNiGGeRD0nks69frgreu0x766f6964NiGGeRd0nks1337gafturasgbsigboa120i3UI49OaF3geaevaiolmao123123aOfurain0n4H34DggTrexewwasads1293194hjXDOthLaLosnggtwget-log1337SoraLOADERSAIAKINAggtq1378bfp919GRB1Q2SAIAKUSOggtr14FaSEXSLAVE1337ggtt1902a3u912u3u4haetrghbr19ju3dSORAojkf120hehahejeje922U2JDJA901F91SlaVLav12helpmedaddthhhhh2wgg9qphbqSlav3Th3seD3viceshzSmYZjYMQ5GbfSoRAxD123LOLiaGv5aA3SoRAxD420LOLinsomni640277SoraBeReppin1337ipcamCache66tlGg9QjUYfouyf876ke3TOKYO3lyEeaXul2dULCVxh93OfjHZ2zTY2gD6MZvKc7KU6rmMkiy6f87lA023UU4U24UIUTheWeekndmioribitchesA5p9TheWeekndsmnblkjpoiAbAdTokyosnebAkiruU8inTznetstatsAlexW9RCAKM20TnewnetwordAyo215WordnloadsBAdAsVWordmanenotyakuzaaBelchWordnetsobpBigN0gg0r420X0102I34fofhasfhiafhoiX19I239124UIUoismXSHJEHHEIIHWOolsVNwo12DeportedDeportedXkTer0GbA1onry0v03FortniteDownLOLZY0urM0mGaypussyfartlmaojkGrAcEnIgGeRaNnYvdGkqndCOqGeoRBe6BEGuiltyCrownZEuS69s4beBsEQhdHOHO-KSNDOZEuz69sat1234aj93hJ23scanHAalie293z0k2LscanJoshoARMHellInSideayyyGangShitscanJoshoARM5HighFryb1glscanJoshoARM6IWhPyucDbJboatnetzscanJoshoARM7IuYgujeIqnbtbatrtahzexsexscanJoshoM68KJJDUHEWBBBIBscanJoshoMIPSJSDGIEVIVAVIGcKbVkzGOPascanJoshoMPSLccADscanJoshoPPCKAZEN-OIU97chickenxingsscanJoshoSH4yakuskzm8KAZEN-PO78HcleanerscanJoshoSPCKAZEN-U79OLdbeefscanJoshoX86yakuz4c24KETASHI32ddrwelperscanarm5zPnr6HpQj2Kaishi-Iz90Ydeexecscanarm6zdrtfxcgyKatrina32doCP3fVjscanarm7zxcfhuioKsif91je39scanm68kKuasadvrhelperl33t_feetl33tl33tfeetscanmipsKuasaBinsMateeQnOhRk85rscanmpslLOLHHHOHOHBUIeXK20CL12ZnyamezyQBotBladeSPOOKYhikariwasherep4029x91xx32uhj4gbejhwizardzhra.outboatnetdbgcondiheroshimaskid.dbglzrdPownedSecurity69.aresfxlyazsxhyUNSTABLEunstable_is_the_story_of_the_universemoobotjnsd9sdoilayourmomgaeissdfjiougsiojOasisSEGRJIJHFVNHSNHEIHFOSapep999KOWAI-BAdAsVKOWAI-SADjHKipU7Ylairdropmalwareyour_verry_fucking_gayBig-Bro-Brightsefaexecshirololieagle.For-Gai-Mezy0x6axNLcloqkisvspookymythSwergjmioGKILLEJW(IU(JIWERGFJGJWJRGHetrhwewrtheIuFdKssCxzjSDFJIjioOnrYoXd666ewrtkjokethajbdf89wu823AAaasrdgsWsGA4@F6FGhostWuzHere666BOGOMIPSbeastmodedvrHelperbestmodesfc6aJfIuYDemon.xeno-is-godICY-P-0ODIJgSHUIHIfhwrgLhu87VhvQPzlunadakuexecbinTacoBellGodYololigangExecutionorbitclientAmnesiaOwariU
Detected TCP or UDP traffic on non-standard ports
Source: global traffic TCP traffic: 192.168.2.23:39074 -> 193.143.1.66:2222
Reads the 'hosts' file potentially containing internal network hosts
Source: /usr/sbin/rsyslogd (PID: 6249) Reads hosts file: /etc/hosts Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6262) Reads hosts file: /etc/hosts Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6272) Reads hosts file: /etc/hosts Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6344) Reads hosts file: /etc/hosts Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6372) Reads hosts file: /etc/hosts Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6450) Reads hosts file: /etc/hosts Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6477) Reads hosts file: /etc/hosts Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6557) Reads hosts file: /etc/hosts Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6580) Reads hosts file: /etc/hosts Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6589) Reads hosts file: /etc/hosts Jump to behavior
Tries to connect to HTTP servers, but all servers are down (expired dropper behavior)
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: global traffic TCP traffic: 192.168.2.23:43928 -> 91.189.91.42:443
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 UDP traffic detected without corresponding DNS query: 1.1.1.1
Source: unknown UDP traffic detected without corresponding DNS query: 1.1.1.1
Source: unknown UDP traffic detected without corresponding DNS query: 1.1.1.1
Source: global traffic DNS traffic detected: DNS query: krkrdoskslansldkalsd.o-r.kr
Source: global traffic DNS traffic detected: DNS query: daisy.ubuntu.com
Source: syslog.155.dr, syslog.31.dr, syslog.107.dr, syslog.199.dr, syslog.57.dr, syslog.191.dr, syslog.23.dr, syslog.40.dr, syslog.141.dr, syslog.91.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
barindex
Malicious sample detected (through community Yara rule)
Source: byte.sh4.elf, type: SAMPLE Matched rule: Detects Mirai Botnet Malware Author: Florian Roth
Source: byte.sh4.elf, type: SAMPLE Matched rule: Detects ELF malware Mirai related Author: Florian Roth
Source: 6207.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY Matched rule: Detects Mirai Botnet Malware Author: Florian Roth
Source: 6207.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY Matched rule: Detects ELF malware Mirai related Author: Florian Roth
Source: 6203.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY Matched rule: Detects Mirai Botnet Malware Author: Florian Roth
Source: 6203.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY Matched rule: Detects ELF malware Mirai related Author: Florian Roth
Source: 6204.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY Matched rule: Detects Mirai Botnet Malware Author: Florian Roth
Source: 6204.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY Matched rule: Detects ELF malware Mirai related Author: Florian Roth
Source: 6201.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY Matched rule: Detects Mirai Botnet Malware Author: Florian Roth
Source: 6201.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY Matched rule: Detects ELF malware Mirai related Author: Florian Roth
Source: 6210.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY Matched rule: Detects Mirai Botnet Malware Author: Florian Roth
Source: 6210.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY Matched rule: Detects ELF malware Mirai related Author: Florian Roth
Sample tries to kill a massive number of system processes
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 1 (init), result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 2, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 3, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 4, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 6, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 9, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 10, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 11, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 12, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 13, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 14, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 15, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 16, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 17, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 18, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 20, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 21, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 22, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 23, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 24, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 25, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 26, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 27, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 28, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 29, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 30, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 35, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 77, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 78, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 79, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 80, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 81, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 82, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 83, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 84, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 85, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 88, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 89, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 91, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 92, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 93, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 94, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 95, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 96, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 97, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 98, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 99, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 100, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 101, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 102, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 103, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 104, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 105, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 106, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 107, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 108, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 109, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 110, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 111, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 112, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 113, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 114, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 115, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 116, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 117, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 118, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 119, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 120, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 121, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 122, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 123, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 124, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 125, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 126, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 127, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 128, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 130, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 132, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 141, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 144, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 157, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 201, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 202, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 203, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 204, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 205, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 206, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 207, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 208, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 209, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 210, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 211, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 212, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 213, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 214, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 215, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 216, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 217, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 218, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 219, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 220, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 221, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 222, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 223, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 224, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 225, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 226, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 227, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 228, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 229, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 230, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 231, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 232, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 233, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 234, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 235, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 236, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 237, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 243, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 248, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 249, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 250, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 251, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 252, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 253, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 254, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 255, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 256, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 257, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 258, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 259, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 260, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 261, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 262, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 263, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 264, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 265, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 266, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 267, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 269, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 270, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 272, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 274, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 278, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 281, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 286, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 322, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 324, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 326, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 327, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 328, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 333, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 346, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 379, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 419, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 420, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 658, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 667, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 670, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 674, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 675, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 676, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 677, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 720, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 721, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 772, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 777, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 785, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 793, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent to PID below 1000: pid: 936, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 1 (init), result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 2, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 3, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 4, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 6, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 9, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 10, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 11, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 12, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 13, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 14, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 15, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 16, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 17, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 18, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 20, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 21, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 22, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 23, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 24, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 25, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 26, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 27, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 28, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 29, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 30, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 35, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 77, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 78, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 79, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 80, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 81, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 82, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 83, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 84, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 85, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 88, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 89, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 91, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 92, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 93, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 94, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 95, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 96, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 97, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 98, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 99, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 100, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 101, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 102, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 103, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 104, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 105, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 106, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 107, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 108, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 109, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 110, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 111, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 112, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 113, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 114, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 115, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 116, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 117, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 118, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 119, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 120, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 121, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 122, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 123, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 124, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 125, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 126, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 127, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 128, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 130, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 132, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 141, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 144, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 157, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 201, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 202, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 203, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 204, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 205, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 206, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 207, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 208, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 209, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 210, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 211, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 212, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 213, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 214, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 215, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 216, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 217, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 218, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 219, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 220, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 221, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 222, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 223, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 224, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 225, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 226, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 227, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 228, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 229, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 230, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 231, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 232, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 233, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 234, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 235, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 236, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 237, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 243, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 248, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 249, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 250, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 251, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 252, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 253, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 254, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 255, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 256, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 257, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 258, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 259, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 260, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 261, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 262, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 263, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 264, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 265, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 266, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 267, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 269, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 270, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 272, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 274, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 278, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 281, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 286, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 322, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 324, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 326, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 327, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 328, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 333, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 346, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 379, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 419, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 420, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 658, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 667, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 670, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 674, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 675, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 676, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 677, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 720, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 772, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 936, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 840, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 896, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent to PID below 1000: pid: 910, result: successful Jump to behavior
Sample tries to kill multiple processes (SIGKILL)
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 1 (init), result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 2, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 3, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 4, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 6, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 9, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 10, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 11, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 12, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 13, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 14, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 15, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 16, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 17, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 18, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 20, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 21, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 22, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 23, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 24, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 25, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 26, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 27, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 28, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 29, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 30, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 35, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 77, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 78, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 79, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 80, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 81, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 82, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 83, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 84, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 85, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 88, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 89, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 91, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 92, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 93, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 94, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 95, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 96, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 97, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 98, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 99, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 100, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 101, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 102, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 103, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 104, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 105, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 106, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 107, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 108, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 109, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 110, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 111, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 112, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 113, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 114, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 115, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 116, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 117, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 118, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 119, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 120, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 121, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 122, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 123, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 124, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 125, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 126, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 127, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 128, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 130, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 132, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 141, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 144, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 157, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 201, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 202, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 203, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 204, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 205, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 206, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 207, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 208, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 209, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 210, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 211, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 212, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 213, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 214, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 215, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 216, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 217, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 218, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 219, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 220, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 221, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 222, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 223, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 224, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 225, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 226, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 227, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 228, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 229, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 230, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 231, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 232, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 233, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 234, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 235, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 236, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 237, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 243, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 248, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 249, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 250, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 251, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 252, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 253, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 254, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 255, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 256, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 257, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 258, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 259, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 260, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 261, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 262, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 263, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 264, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 265, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 266, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 267, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 269, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 270, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 272, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 274, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 278, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 281, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 286, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 322, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 324, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 326, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 327, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 328, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 333, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 346, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 379, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 419, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 420, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 658, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 667, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 670, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 674, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 675, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 676, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 677, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 720, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 721, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 772, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 777, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 785, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 793, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 936, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 1207, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 1320, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 1344, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 1601, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 1983, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 2048, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 2746, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 2749, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 2761, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 2882, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 3021, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 3088, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 4456, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 4457, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 4458, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 4459, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 4481, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 4486, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 4489, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 1 (init), result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 2, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 3, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 4, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 9, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 10, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 11, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 12, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 13, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 14, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 15, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 16, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 17, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 18, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 20, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 21, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 22, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 23, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 24, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 25, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 26, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 27, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 28, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 29, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 30, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 35, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 77, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 78, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 79, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 80, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 81, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 82, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 83, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 84, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 85, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 88, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 89, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 91, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 92, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 93, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 94, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 95, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 96, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 97, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 98, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 99, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 100, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 101, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 102, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 103, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 104, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 105, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 106, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 107, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 108, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 109, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 110, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 111, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 112, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 113, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 114, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 115, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 116, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 117, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 118, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 119, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 120, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 121, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 122, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 123, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 124, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 125, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 126, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 127, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 128, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 130, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 132, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 141, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 144, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 157, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 201, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 202, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 203, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 204, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 205, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 206, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 207, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 208, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 209, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 210, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 211, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 212, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 213, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 214, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 215, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 216, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 217, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 218, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 219, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 220, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 221, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 222, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 223, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 224, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 225, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 226, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 227, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 228, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 229, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 230, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 231, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 232, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 233, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 234, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 235, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 236, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 237, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 243, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 248, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 249, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 250, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 251, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 252, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 253, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 254, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 255, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 256, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 257, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 258, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 259, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 260, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 261, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 262, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 263, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 264, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 265, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 266, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 267, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 269, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 270, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 272, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 274, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 278, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 281, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 286, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 322, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 324, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 326, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 327, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 328, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 333, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 346, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 379, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 419, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 420, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 658, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 667, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 670, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 674, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 675, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 676, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 677, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 720, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 772, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 936, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 1207, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 1320, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 1601, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 1886, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 1983, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 2048, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 2746, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 2749, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 2761, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 2882, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 3021, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 3088, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 4456, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 4457, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 4458, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 4459, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 4481, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 4486, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 4489, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6183, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6203, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6207, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6247, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6248, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6249, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6250, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6260, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6261, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6262, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6263, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6270, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6271, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6272, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6273, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 840, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 896, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 910, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6283, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6343, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6344, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6345, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6346, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6366, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6369, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6370, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6372, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6373, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6374, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6449, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6450, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6451, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6452, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6453, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6476, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6477, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6478, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6479, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6480, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6554, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6557, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6558, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6559, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6560, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6577, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6578, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6580, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6581, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6582, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6588, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6589, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6590, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6591, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6595, result: successful Jump to behavior
Sample contains strings indicative of BusyBox which embeds multiple Unix commands in a single executable
Source: Initial sample String containing 'busybox' found: busybox
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: ;httpurl=POST'=byte/proc//proc/%s/exe/proc/self/exe/proc/proc/%d/cmdlinenetstatwgettftpftpcurlbusyboxreboot/bin/busyboxvar/Challengeapp/hi3511gmDVRiboxusr/dvr_main _8182T_1108mnt/mtd/app/guivar/Kylinl0 c/udevdanko-app/ankosample _8182T_1104var/tmp/soniahicorestm_hi3511_dvr/usr/lib/systemd/systemd/usr/libexec/openssh/sftp-serverusr/shellmnt/sys/bin/boot/media/srv/var/run/sbin/lib/etc/dev/home/Davincitelnetsshwatchdog/var/spool/var/Sofiasshd/usr/compress/bin//compress/bin/compress/usr/bashhttpdtelnetddropbearropbearencodersystem/root/dvr_gui//root/dvr_app//anko-app//opt/soraJoshohajime902i13BzSxLxBxeYHOHO-LUGO7HOHO-U79OLJuYfouyf87NiGGeR69xdSO190Ij1XLOLKIKEEEDDEekjheory98escansh4MDMAfdevalvexscanspcMELTEDNINJAREALZflexsonskidsscanx86MISAKI-U79OLfoAxi102kxeswodjwodjwojMmKiy7f87lfreecookiex86sysgpufrgegesysupdater0DnAzepdNiGGeRD0nks69frgreu0x766f6964NiGGeRd0nks1337gafturasgbsigboa120i3UI49OaF3geaevaiolmao123123aOfurain0n4H34DggTrexewwasads1293194hjXDOthLaLosnggtwget-log1337SoraLOADERSAIAKINAggtq1378bfp919GRB1Q2SAI
Sample has stripped symbol table
Source: ELF static info symbol of initial sample .symtab present: no
Sample tries to kill a process (SIGKILL)
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 1 (init), result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 2, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 3, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 4, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 6, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 9, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 10, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 11, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 12, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 13, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 14, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 15, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 16, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 17, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 18, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 20, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 21, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 22, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 23, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 24, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 25, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 26, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 27, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 28, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 29, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 30, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 35, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 77, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 78, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 79, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 80, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 81, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 82, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 83, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 84, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 85, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 88, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 89, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 91, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 92, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 93, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 94, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 95, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 96, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 97, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 98, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 99, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 100, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 101, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 102, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 103, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 104, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 105, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 106, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 107, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 108, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 109, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 110, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 111, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 112, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 113, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 114, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 115, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 116, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 117, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 118, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 119, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 120, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 121, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 122, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 123, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 124, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 125, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 126, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 127, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 128, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 130, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 132, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 141, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 144, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 157, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 201, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 202, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 203, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 204, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 205, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 206, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 207, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 208, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 209, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 210, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 211, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 212, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 213, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 214, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 215, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 216, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 217, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 218, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 219, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 220, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 221, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 222, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 223, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 224, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 225, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 226, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 227, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 228, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 229, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 230, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 231, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 232, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 233, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 234, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 235, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 236, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 237, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 243, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 248, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 249, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 250, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 251, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 252, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 253, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 254, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 255, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 256, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 257, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 258, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 259, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 260, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 261, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 262, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 263, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 264, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 265, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 266, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 267, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 269, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 270, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 272, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 274, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 278, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 281, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 286, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 322, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 324, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 326, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 327, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 328, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 333, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 346, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 379, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 419, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 420, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 658, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 667, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 670, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 674, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 675, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 676, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 677, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 720, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 721, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 772, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 777, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 785, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 793, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 936, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 1207, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 1320, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 1344, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 1601, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 1983, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 2048, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 2746, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 2749, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 2761, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 2882, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 3021, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 3088, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 4456, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 4457, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 4458, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 4459, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 4481, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 4486, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) SIGKILL sent: pid: 4489, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 1 (init), result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 2, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 3, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 4, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 9, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 10, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 11, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 12, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 13, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 14, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 15, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 16, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 17, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 18, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 20, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 21, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 22, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 23, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 24, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 25, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 26, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 27, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 28, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 29, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 30, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 35, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 77, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 78, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 79, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 80, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 81, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 82, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 83, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 84, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 85, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 88, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 89, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 91, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 92, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 93, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 94, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 95, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 96, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 97, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 98, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 99, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 100, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 101, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 102, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 103, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 104, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 105, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 106, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 107, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 108, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 109, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 110, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 111, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 112, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 113, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 114, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 115, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 116, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 117, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 118, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 119, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 120, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 121, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 122, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 123, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 124, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 125, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 126, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 127, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 128, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 130, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 132, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 141, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 144, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 157, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 201, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 202, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 203, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 204, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 205, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 206, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 207, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 208, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 209, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 210, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 211, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 212, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 213, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 214, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 215, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 216, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 217, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 218, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 219, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 220, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 221, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 222, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 223, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 224, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 225, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 226, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 227, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 228, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 229, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 230, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 231, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 232, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 233, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 234, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 235, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 236, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 237, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 243, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 248, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 249, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 250, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 251, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 252, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 253, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 254, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 255, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 256, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 257, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 258, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 259, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 260, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 261, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 262, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 263, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 264, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 265, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 266, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 267, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 269, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 270, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 272, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 274, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 278, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 281, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 286, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 322, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 324, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 326, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 327, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 328, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 333, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 346, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 379, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 419, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 420, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 658, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 667, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 670, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 674, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 675, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 676, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 677, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 720, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 772, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 936, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 1207, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 1320, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 1601, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 1886, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 1983, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 2048, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 2746, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 2749, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 2761, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 2882, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 3021, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 3088, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 4456, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 4457, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 4458, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 4459, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 4481, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 4486, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 4489, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6183, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6203, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6207, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6247, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6248, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6249, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6250, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6260, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6261, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6262, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6263, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6270, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6271, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6272, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6273, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 840, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 896, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 910, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6283, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6343, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6344, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6345, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6346, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6366, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6369, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6370, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6372, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6373, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6374, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6449, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6450, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6451, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6452, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6453, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6476, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6477, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6478, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6479, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6480, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6554, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6557, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6558, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6559, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6560, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6577, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6578, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6580, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6581, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6582, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6588, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6589, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6590, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6591, result: successful Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6209) SIGKILL sent: pid: 6595, result: successful Jump to behavior
Yara signature match
Source: byte.sh4.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: byte.sh4.elf, type: SAMPLE Matched rule: MAL_ELF_LNX_Mirai_Oct10_2 date = 2018-10-27, hash1 = fa0018e75f503f9748a5de0d14d4358db234f65e28c31c8d5878cc58807081c9, author = Florian Roth, description = Detects ELF malware Mirai related, reference = Internal Research
Source: 6207.1.00007f14e8400000.00007f14e8412000.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: 6207.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY Matched rule: MAL_ELF_LNX_Mirai_Oct10_2 date = 2018-10-27, hash1 = fa0018e75f503f9748a5de0d14d4358db234f65e28c31c8d5878cc58807081c9, author = Florian Roth, description = Detects ELF malware Mirai related, reference = Internal Research
Source: 6203.1.00007f14e8400000.00007f14e8412000.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: 6203.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY Matched rule: MAL_ELF_LNX_Mirai_Oct10_2 date = 2018-10-27, hash1 = fa0018e75f503f9748a5de0d14d4358db234f65e28c31c8d5878cc58807081c9, author = Florian Roth, description = Detects ELF malware Mirai related, reference = Internal Research
Source: 6204.1.00007f14e8400000.00007f14e8412000.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: 6204.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY Matched rule: MAL_ELF_LNX_Mirai_Oct10_2 date = 2018-10-27, hash1 = fa0018e75f503f9748a5de0d14d4358db234f65e28c31c8d5878cc58807081c9, author = Florian Roth, description = Detects ELF malware Mirai related, reference = Internal Research
Source: 6201.1.00007f14e8400000.00007f14e8412000.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: 6201.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY Matched rule: MAL_ELF_LNX_Mirai_Oct10_2 date = 2018-10-27, hash1 = fa0018e75f503f9748a5de0d14d4358db234f65e28c31c8d5878cc58807081c9, author = Florian Roth, description = Detects ELF malware Mirai related, reference = Internal Research
Source: 6210.1.00007f14e8400000.00007f14e8412000.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: 6210.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY Matched rule: MAL_ELF_LNX_Mirai_Oct10_2 date = 2018-10-27, hash1 = fa0018e75f503f9748a5de0d14d4358db234f65e28c31c8d5878cc58807081c9, author = Florian Roth, description = Detects ELF malware Mirai related, reference = Internal Research
Source: classification engine Classification label: mal100.spre.troj.linELF@0/1054@7/0

Persistence and Installation Behavior
barindex
Sample reads /proc/mounts (often used for finding a writable filesystem)
Source: /usr/bin/dbus-daemon (PID: 6247) File: /proc/6247/mounts Jump to behavior
Source: /bin/fusermount (PID: 6251) File: /proc/6251/mounts Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6260) File: /proc/6260/mounts Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6270) File: /proc/6270/mounts Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6283) File: /proc/6283/mounts Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6366) File: /proc/6366/mounts Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6449) File: /proc/6449/mounts Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6476) File: /proc/6476/mounts Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6554) File: /proc/6554/mounts Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6577) File: /proc/6577/mounts Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6588) File: /proc/6588/mounts Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6596) File: /proc/6596/mounts Jump to behavior
Creates hidden files and/or directories
Source: /lib/systemd/systemd-logind (PID: 6286) Directory: <invalid fd (18)>/.. Jump to behavior
Source: /lib/systemd/systemd-logind (PID: 6286) Directory: <invalid fd (17)>/.. Jump to behavior
Source: /lib/systemd/systemd-logind (PID: 6286) File: /run/systemd/seats/.#seat0v5tDHv Jump to behavior
Source: /lib/systemd/systemd-logind (PID: 6385) Directory: <invalid fd (18)>/.. Jump to behavior
Source: /lib/systemd/systemd-logind (PID: 6385) Directory: <invalid fd (17)>/.. Jump to behavior
Source: /lib/systemd/systemd-logind (PID: 6385) File: /run/systemd/seats/.#seat09hBT2X Jump to behavior
Source: /usr/lib/policykit-1/polkitd (PID: 6445) Directory: /root/.cache Jump to behavior
Source: /usr/lib/policykit-1/polkitd (PID: 6475) Directory: /root/.cache Jump to behavior
Source: /lib/systemd/systemd-logind (PID: 6492) Directory: <invalid fd (18)>/.. Jump to behavior
Source: /lib/systemd/systemd-logind (PID: 6492) Directory: <invalid fd (17)>/.. Jump to behavior
Source: /lib/systemd/systemd-logind (PID: 6492) File: /run/systemd/seats/.#seat0OB7Zu4 Jump to behavior
Source: /lib/systemd/systemd-logind (PID: 6652) Directory: <invalid fd (18)>/..
Source: /lib/systemd/systemd-logind (PID: 6652) Directory: <invalid fd (17)>/..
Source: /lib/systemd/systemd-logind (PID: 6652) File: /run/systemd/seats/.#seat0QqHmzc
Enumerates processes within the "proc" file system
Source: /usr/bin/dbus-daemon (PID: 6366) File opened: /proc/6373/cmdline Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6366) File opened: /proc/6373/cmdline Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6366) File opened: /proc/6374/cmdline Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6366) File opened: /proc/6366/status Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6366) File opened: /proc/6366/attr/current Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6366) File opened: /proc/6445/cmdline Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6366) File opened: /proc/6382/cmdline Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6366) File opened: /proc/1/cmdline Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6476) File opened: /proc/6476/status Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6476) File opened: /proc/6476/attr/current Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6476) File opened: /proc/6475/cmdline Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6476) File opened: /proc/6480/cmdline Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6476) File opened: /proc/1/cmdline Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6476) File opened: /proc/6479/cmdline Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6476) File opened: /proc/6479/cmdline Jump to behavior
Source: /usr/bin/dbus-daemon (PID: 6476) File opened: /proc/6549/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/1582/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/3088/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/230/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/110/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/231/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/111/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/232/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/1579/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/112/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/233/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/113/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/234/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/1335/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/114/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/235/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/1334/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/1576/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/115/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/236/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/116/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/237/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/117/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/118/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/910/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/119/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/912/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/10/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/11/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/918/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/12/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/13/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/14/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/15/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/16/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/17/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/18/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/1594/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/120/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/121/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/1349/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/1/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/122/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/243/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/123/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/2/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/124/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/3/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/4/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/125/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/126/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/1344/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/1465/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/1586/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/127/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/6/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/248/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/128/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/249/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/1463/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/800/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/9/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/801/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/20/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/21/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/22/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/23/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/24/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/25/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/26/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/27/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/28/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/29/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/491/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/250/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/130/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/251/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/252/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/132/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/253/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/254/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/255/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/256/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/1599/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/257/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/1477/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/379/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/258/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/1476/cmdline Jump to behavior
Source: /tmp/byte.sh4.elf (PID: 6203) File opened: /proc/259/cmdline Jump to behavior
Executes commands using a shell command-line interpreter
Source: /usr/bin/gpu-manager (PID: 6350) Shell command executed: sh -c "grep -G \"^blacklist.*nvidia[[:space:]]*$\" /etc/modprobe.d/*.conf" Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6355) Shell command executed: sh -c "grep -G \"^blacklist.*nvidia[[:space:]]*$\" /lib/modprobe.d/*.conf" Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6357) Shell command executed: sh -c "grep -G \"^blacklist.*radeon[[:space:]]*$\" /etc/modprobe.d/*.conf" Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6359) Shell command executed: sh -c "grep -G \"^blacklist.*radeon[[:space:]]*$\" /lib/modprobe.d/*.conf" Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6363) Shell command executed: sh -c "grep -G \"^blacklist.*amdgpu[[:space:]]*$\" /etc/modprobe.d/*.conf" Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6457) Shell command executed: sh -c "grep -G \"^blacklist.*nvidia[[:space:]]*$\" /etc/modprobe.d/*.conf" Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6460) Shell command executed: sh -c "grep -G \"^blacklist.*nvidia[[:space:]]*$\" /lib/modprobe.d/*.conf" Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6462) Shell command executed: sh -c "grep -G \"^blacklist.*radeon[[:space:]]*$\" /etc/modprobe.d/*.conf" Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6464) Shell command executed: sh -c "grep -G \"^blacklist.*radeon[[:space:]]*$\" /lib/modprobe.d/*.conf" Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6471) Shell command executed: sh -c "grep -G \"^blacklist.*amdgpu[[:space:]]*$\" /etc/modprobe.d/*.conf" Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6564) Shell command executed: sh -c "grep -G \"^blacklist.*nvidia[[:space:]]*$\" /etc/modprobe.d/*.conf" Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6567) Shell command executed: sh -c "grep -G \"^blacklist.*nvidia[[:space:]]*$\" /lib/modprobe.d/*.conf" Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6569) Shell command executed: sh -c "grep -G \"^blacklist.*radeon[[:space:]]*$\" /etc/modprobe.d/*.conf" Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6571) Shell command executed: sh -c "grep -G \"^blacklist.*radeon[[:space:]]*$\" /lib/modprobe.d/*.conf" Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6575) Shell command executed: sh -c "grep -G \"^blacklist.*amdgpu[[:space:]]*$\" /etc/modprobe.d/*.conf" Jump to behavior
Executes the "grep" command used to find patterns in files or piped streams
Source: /bin/sh (PID: 6351) 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: 6356) 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: 6358) 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: 6360) 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: 6364) 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: 6458) 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: 6461) 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: 6463) 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: 6465) 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: 6472) 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: 6565) 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: 6568) 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: 6570) 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: 6572) 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: 6576) 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
Executes the "kill" or "pkill" command typically used to terminate processes
Source: /usr/share/gdm/generate-config (PID: 6371) Pkill executable: /usr/bin/pkill -> pkill --signal HUP --uid gdm dconf-service Jump to behavior
Source: /usr/share/gdm/generate-config (PID: 6481) Pkill executable: /usr/bin/pkill -> pkill --signal HUP --uid gdm dconf-service Jump to behavior
Source: /usr/share/gdm/generate-config (PID: 6579) Pkill executable: /usr/bin/pkill -> pkill --signal HUP --uid gdm dconf-service Jump to behavior
Source: /usr/share/gdm/generate-config (PID: 6598) Pkill executable: /usr/bin/pkill -> pkill --signal HUP --uid gdm dconf-service Jump to behavior
Source: /usr/share/gdm/generate-config (PID: 6608) Pkill executable: /usr/bin/pkill -> pkill --signal HUP --uid gdm dconf-service
Source: /usr/share/gdm/generate-config (PID: 6611) Pkill executable: /usr/bin/pkill -> pkill --signal HUP --uid gdm dconf-service
Source: /usr/share/gdm/generate-config (PID: 6616) Pkill executable: /usr/bin/pkill -> pkill --signal HUP --uid gdm dconf-service
Source: /usr/sbin/rsyslogd (PID: 6249) Log file created: /var/log/auth.log
Source: /usr/sbin/rsyslogd (PID: 6249) Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6262) Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6272) Log file created: /var/log/auth.log
Source: /usr/sbin/rsyslogd (PID: 6272) Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6344) Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6344) Log file created: /var/log/auth.log
Source: /usr/sbin/rsyslogd (PID: 6372) Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6450) Log file created: /var/log/auth.log
Source: /usr/sbin/rsyslogd (PID: 6450) Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6477) Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6557) Log file created: /var/log/auth.log Jump to dropped file
Source: /usr/sbin/rsyslogd (PID: 6557) Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6580) Log file created: /var/log/kern.log
Source: /usr/sbin/rsyslogd (PID: 6589) Log file created: /var/log/kern.log Jump to dropped file
Deletes log files
Source: /usr/bin/gpu-manager (PID: 6346) Truncated file: /var/log/gpu-manager.log Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6453) Truncated file: /var/log/gpu-manager.log Jump to behavior
Source: /usr/bin/gpu-manager (PID: 6560) Truncated file: /var/log/gpu-manager.log Jump to behavior
Reads CPU information from /sys indicative of miner or evasive malware
Source: /usr/bin/pkill (PID: 6371) Reads CPU info from /sys: /sys/devices/system/cpu/online Jump to behavior
Source: /usr/bin/pkill (PID: 6481) Reads CPU info from /sys: /sys/devices/system/cpu/online Jump to behavior
Source: /usr/bin/pkill (PID: 6579) Reads CPU info from /sys: /sys/devices/system/cpu/online Jump to behavior
Source: /usr/bin/pkill (PID: 6598) Reads CPU info from /sys: /sys/devices/system/cpu/online Jump to behavior
Uses the "uname" system call to query kernel version information (possible evasion)
Source: /tmp/byte.sh4.elf (PID: 6201) Queries kernel information via 'uname': Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6249) Queries kernel information via 'uname': Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6262) Queries kernel information via 'uname': Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6272) Queries kernel information via 'uname': Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6344) Queries kernel information via 'uname': Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6372) Queries kernel information via 'uname': Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6450) Queries kernel information via 'uname': Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6477) Queries kernel information via 'uname': Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6557) Queries kernel information via 'uname': Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6580) Queries kernel information via 'uname': Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6589) Queries kernel information via 'uname': Jump to behavior
Source: /usr/sbin/rsyslogd (PID: 6599) Queries kernel information via 'uname': Jump to behavior
Source: byte.sh4.elf, 6201.1.00007fff00d33000.00007fff00d54000.rw-.sdmp, byte.sh4.elf, 6203.1.00007fff00d33000.00007fff00d54000.rw-.sdmp, byte.sh4.elf, 6204.1.00007fff00d33000.00007fff00d54000.rw-.sdmp, byte.sh4.elf, 6207.1.00007fff00d33000.00007fff00d54000.rw-.sdmp, byte.sh4.elf, 6210.1.00007fff00d33000.00007fff00d54000.rw-.sdmp Binary or memory string: ,5."x86_64/usr/bin/qemu-sh4/tmp/byte.sh4.elfSUDO_USER=saturninoPATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/binDISPLAY=:1.0XAUTHORITY=/run/user/1000/gdm/XauthoritySUDO_UID=1000TERM=xterm-256colorCOLORTERM=truecolorLOGNAME=rootUSER=rootLANG=en_US.UTF-8SUDO_COMMAND=/bin/bashHOME=/rootMAIL=/var/mail/rootSUDO_GID=1000SHELL=/bin/bash/tmp/byte.sh4.elf
Source: byte.sh4.elf, 6201.1.00007fff00d33000.00007fff00d54000.rw-.sdmp, byte.sh4.elf, 6203.1.00007fff00d33000.00007fff00d54000.rw-.sdmp, byte.sh4.elf, 6204.1.00007fff00d33000.00007fff00d54000.rw-.sdmp, byte.sh4.elf, 6207.1.00007fff00d33000.00007fff00d54000.rw-.sdmp, byte.sh4.elf, 6210.1.00007fff00d33000.00007fff00d54000.rw-.sdmp Binary or memory string: /usr/bin/qemu-sh4
Source: syslog.23.dr Binary or memory string: Jan 15 23:32:54 galassia kernel: [ 416.975192] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 12/12/2018
Source: byte.sh4.elf, 6201.1.000055f665bfc000.000055f665c5f000.rw-.sdmp, byte.sh4.elf, 6203.1.000055f665bfc000.000055f665c5f000.rw-.sdmp, byte.sh4.elf, 6204.1.000055f665bfc000.000055f665c5f000.rw-.sdmp, byte.sh4.elf, 6207.1.000055f665bfc000.000055f665c5f000.rw-.sdmp, byte.sh4.elf, 6210.1.000055f665bfc000.000055f665c5f000.rw-.sdmp Binary or memory string: U5!/etc/qemu-binfmt/sh4
Source: byte.sh4.elf, 6201.1.000055f665bfc000.000055f665c5f000.rw-.sdmp, byte.sh4.elf, 6203.1.000055f665bfc000.000055f665c5f000.rw-.sdmp, byte.sh4.elf, 6204.1.000055f665bfc000.000055f665c5f000.rw-.sdmp, byte.sh4.elf, 6207.1.000055f665bfc000.000055f665c5f000.rw-.sdmp, byte.sh4.elf, 6210.1.000055f665bfc000.000055f665c5f000.rw-.sdmp Binary or memory string: /etc/qemu-binfmt/sh4
Source: syslog.23.dr Binary or memory string: Jan 15 23:32:54 galassia kernel: [ 416.975166] Modules linked in: monitor(OE) md4 cmac cifs libarc4 fscache libdes vmw_vsock_vmci_transport vsock binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmw_balloon joydev input_leds serio_raw vmw_vmci sch_fq_codel drm parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper psmouse ahci mptspi vmxnet3 scsi_transport_spi mptscsih libahci mptbase

Stealing of Sensitive Information
barindex
Yara detected Mirai
Source: Yara match File source: byte.sh4.elf, type: SAMPLE
Source: Yara match File source: 6207.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY
Source: Yara match File source: 6203.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY
Source: Yara match File source: 6204.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY
Source: Yara match File source: 6201.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY
Source: Yara match File source: 6210.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY
Source: Yara match File source: Process Memory Space: byte.sh4.elf PID: 6201, type: MEMORYSTR
Source: Yara match File source: Process Memory Space: byte.sh4.elf PID: 6203, type: MEMORYSTR
Source: Yara match File source: Process Memory Space: byte.sh4.elf PID: 6204, type: MEMORYSTR
Source: Yara match File source: Process Memory Space: byte.sh4.elf PID: 6207, type: MEMORYSTR
Source: Yara match File source: Process Memory Space: byte.sh4.elf PID: 6210, type: MEMORYSTR
Yara detected Okiru
Source: Yara match File source: byte.sh4.elf, type: SAMPLE
Source: Yara match File source: 6207.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY
Source: Yara match File source: 6203.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY
Source: Yara match File source: 6204.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY
Source: Yara match File source: 6201.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY
Source: Yara match File source: 6210.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY
Source: Yara match File source: Process Memory Space: byte.sh4.elf PID: 6201, type: MEMORYSTR
Source: Yara match File source: Process Memory Space: byte.sh4.elf PID: 6203, type: MEMORYSTR
Source: Yara match File source: Process Memory Space: byte.sh4.elf PID: 6204, type: MEMORYSTR
Source: Yara match File source: Process Memory Space: byte.sh4.elf PID: 6207, type: MEMORYSTR
Source: Yara match File source: Process Memory Space: byte.sh4.elf PID: 6210, type: MEMORYSTR

Remote Access Functionality
barindex
Yara detected Mirai
Source: Yara match File source: byte.sh4.elf, type: SAMPLE
Source: Yara match File source: 6207.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY
Source: Yara match File source: 6203.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY
Source: Yara match File source: 6204.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY
Source: Yara match File source: 6201.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY
Source: Yara match File source: 6210.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY
Source: Yara match File source: Process Memory Space: byte.sh4.elf PID: 6201, type: MEMORYSTR
Source: Yara match File source: Process Memory Space: byte.sh4.elf PID: 6203, type: MEMORYSTR
Source: Yara match File source: Process Memory Space: byte.sh4.elf PID: 6204, type: MEMORYSTR
Source: Yara match File source: Process Memory Space: byte.sh4.elf PID: 6207, type: MEMORYSTR
Source: Yara match File source: Process Memory Space: byte.sh4.elf PID: 6210, type: MEMORYSTR
Yara detected Okiru
Source: Yara match File source: byte.sh4.elf, type: SAMPLE
Source: Yara match File source: 6207.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY
Source: Yara match File source: 6203.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY
Source: Yara match File source: 6204.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY
Source: Yara match File source: 6201.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY
Source: Yara match File source: 6210.1.00007f14e8400000.00007f14e8412000.r-x.sdmp, type: MEMORY
Source: Yara match File source: Process Memory Space: byte.sh4.elf PID: 6201, type: MEMORYSTR
Source: Yara match File source: Process Memory Space: byte.sh4.elf PID: 6203, type: MEMORYSTR
Source: Yara match File source: Process Memory Space: byte.sh4.elf PID: 6204, type: MEMORYSTR
Source: Yara match File source: Process Memory Space: byte.sh4.elf PID: 6207, type: MEMORYSTR
Source: Yara match File source: Process Memory Space: byte.sh4.elf PID: 6210, type: MEMORYSTR

No Screenshots

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

Contacted Public IPs

IP Domain Country Flag ASN ASN Name Malicious
193.143.1.66
 krkrdoskslansldkalsd.o-r.kr unknown
57271 BITWEB-ASRU 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

Contacted Domains

Name IP Active
daisy.ubuntu.com 162.213.35.25 true
krkrdoskslansldkalsd.o-r.kr 193.143.1.66 true