Linux Analysis Report sora.arm7

Overview

General Information

Sample Name: sora.arm7
Analysis ID: 518886
MD5: c0530dfd3766a324673f37c1644de5bc
SHA1: a45fb3c938ed307ed0f4a550bc17e460a0e5b661
SHA256: 8a6e72fa60a5be3c99b64bdbbf23839949e051dfaf9b975c040fa00c8edde1c6
Tags: Mirai
Infos:

Detection

Mirai
Score: 72
Range: 0 - 100
Whitelisted: false

Signatures

Snort IDS alert for network traffic (e.g. based on Emerging Threat rules)
Yara detected Mirai
Multi AV Scanner detection for submitted file
Sample is packed with UPX
Uses known network protocols on non-standard ports
Sample contains only a LOAD segment without any section mappings
Yara signature match
Uses the "uname" system call to query kernel version information (possible evasion)
Enumerates processes within the "proc" file system
Tries to connect to HTTP servers, but all servers are down (expired dropper behavior)
Detected TCP or UDP traffic on non-standard ports
Sample listens on a socket
Sample tries to kill a process (SIGKILL)

Classification

AV Detection:

barindex
Multi AV Scanner detection for submitted file
Source: sora.arm7 Virustotal: Detection: 41% Perma Link
Source: sora.arm7 ReversingLabs: Detection: 42%

Networking:

barindex
Snort IDS alert for network traffic (e.g. based on Emerging Threat rules)
Source: Traffic Snort IDS: 716 INFO TELNET access 1.218.245.230:23 -> 192.168.2.23:44004
Source: Traffic Snort IDS: 716 INFO TELNET access 1.251.57.101:23 -> 192.168.2.23:35992
Source: Traffic Snort IDS: 716 INFO TELNET access 111.56.51.195:23 -> 192.168.2.23:35188
Source: Traffic Snort IDS: 492 INFO TELNET login failed 111.56.51.195:23 -> 192.168.2.23:35188
Source: Traffic Snort IDS: 716 INFO TELNET access 111.56.51.195:23 -> 192.168.2.23:35198
Source: Traffic Snort IDS: 492 INFO TELNET login failed 111.56.51.195:23 -> 192.168.2.23:35198
Source: Traffic Snort IDS: 716 INFO TELNET access 1.218.245.230:23 -> 192.168.2.23:44116
Source: Traffic Snort IDS: 716 INFO TELNET access 111.56.51.195:23 -> 192.168.2.23:35238
Source: Traffic Snort IDS: 492 INFO TELNET login failed 111.56.51.195:23 -> 192.168.2.23:35238
Source: Traffic Snort IDS: 716 INFO TELNET access 111.56.51.195:23 -> 192.168.2.23:35270
Source: Traffic Snort IDS: 492 INFO TELNET login failed 111.56.51.195:23 -> 192.168.2.23:35270
Source: Traffic Snort IDS: 716 INFO TELNET access 111.56.51.195:23 -> 192.168.2.23:35320
Source: Traffic Snort IDS: 716 INFO TELNET access 1.251.57.101:23 -> 192.168.2.23:36172
Source: Traffic Snort IDS: 492 INFO TELNET login failed 111.56.51.195:23 -> 192.168.2.23:35320
Source: Traffic Snort IDS: 716 INFO TELNET access 111.56.51.195:23 -> 192.168.2.23:35352
Source: Traffic Snort IDS: 492 INFO TELNET login failed 111.56.51.195:23 -> 192.168.2.23:35352
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 108.39.178.247:23 -> 192.168.2.23:47030
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 108.39.178.247:23 -> 192.168.2.23:47030
Source: Traffic Snort IDS: 2023434 ET TROJAN Possible Linux.Mirai Login Attempt (7ujMko0vizxv) 192.168.2.23:36114 -> 190.60.19.213:23
Source: Traffic Snort IDS: 716 INFO TELNET access 111.56.51.195:23 -> 192.168.2.23:35386
Source: Traffic Snort IDS: 716 INFO TELNET access 1.218.245.230:23 -> 192.168.2.23:44304
Source: Traffic Snort IDS: 492 INFO TELNET login failed 111.56.51.195:23 -> 192.168.2.23:35386
Source: Traffic Snort IDS: 716 INFO TELNET access 81.21.249.100:23 -> 192.168.2.23:56860
Source: Traffic Snort IDS: 716 INFO TELNET access 111.56.51.195:23 -> 192.168.2.23:35424
Source: Traffic Snort IDS: 492 INFO TELNET login failed 111.56.51.195:23 -> 192.168.2.23:35424
Source: Traffic Snort IDS: 716 INFO TELNET access 111.56.51.195:23 -> 192.168.2.23:35446
Source: Traffic Snort IDS: 492 INFO TELNET login failed 111.56.51.195:23 -> 192.168.2.23:35446
Source: Traffic Snort IDS: 716 INFO TELNET access 1.251.57.101:23 -> 192.168.2.23:36344
Source: Traffic Snort IDS: 716 INFO TELNET access 111.56.51.195:23 -> 192.168.2.23:35502
Source: Traffic Snort IDS: 492 INFO TELNET login failed 111.56.51.195:23 -> 192.168.2.23:35502
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 69.173.230.203:23 -> 192.168.2.23:36636
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 69.173.230.203:23 -> 192.168.2.23:36636
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 69.173.230.203:23 -> 192.168.2.23:36662
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 69.173.230.203:23 -> 192.168.2.23:36662
Source: Traffic Snort IDS: 716 INFO TELNET access 1.218.245.230:23 -> 192.168.2.23:44482
Source: Traffic Snort IDS: 492 INFO TELNET login failed 121.254.204.242:23 -> 192.168.2.23:45712
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 69.173.230.203:23 -> 192.168.2.23:36678
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 69.173.230.203:23 -> 192.168.2.23:36678
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 108.39.178.247:23 -> 192.168.2.23:47238
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 108.39.178.247:23 -> 192.168.2.23:47238
Source: Traffic Snort IDS: 716 INFO TELNET access 81.21.249.100:23 -> 192.168.2.23:57024
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 69.173.230.203:23 -> 192.168.2.23:36692
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 69.173.230.203:23 -> 192.168.2.23:36692
Source: Traffic Snort IDS: 2023433 ET TROJAN Possible Linux.Mirai Login Attempt (7ujMko0admin) 192.168.2.23:41002 -> 87.75.69.53:23
Source: Traffic Snort IDS: 2023433 ET TROJAN Possible Linux.Mirai Login Attempt (7ujMko0admin) 192.168.2.23:41004 -> 87.75.69.53:23
Source: Traffic Snort IDS: 2023434 ET TROJAN Possible Linux.Mirai Login Attempt (7ujMko0vizxv) 192.168.2.23:41034 -> 87.75.69.53:23
Source: Traffic Snort IDS: 492 INFO TELNET login failed 121.254.204.242:23 -> 192.168.2.23:45806
Source: Traffic Snort IDS: 716 INFO TELNET access 1.251.57.101:23 -> 192.168.2.23:36536
Source: Traffic Snort IDS: 2023448 ET TROJAN Possible Linux.Mirai Login Attempt (ubnt) 192.168.2.23:40516 -> 31.199.225.231:23
Source: Traffic Snort IDS: 492 INFO TELNET login failed 123.175.50.138:23 -> 192.168.2.23:52042
Source: Traffic Snort IDS: 716 INFO TELNET access 178.206.214.19:23 -> 192.168.2.23:58340
Source: Traffic Snort IDS: 716 INFO TELNET access 60.213.32.54:23 -> 192.168.2.23:38002
Source: Traffic Snort IDS: 716 INFO TELNET access 178.206.214.19:23 -> 192.168.2.23:58356
Source: Traffic Snort IDS: 716 INFO TELNET access 178.206.214.19:23 -> 192.168.2.23:58362
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 59.127.75.126:23 -> 192.168.2.23:45312
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 59.127.75.126:23 -> 192.168.2.23:45312
Source: Traffic Snort IDS: 716 INFO TELNET access 178.206.214.19:23 -> 192.168.2.23:58372
Source: Traffic Snort IDS: 492 INFO TELNET login failed 121.254.204.242:23 -> 192.168.2.23:45924
Source: Traffic Snort IDS: 716 INFO TELNET access 1.218.245.230:23 -> 192.168.2.23:44690
Source: Traffic Snort IDS: 716 INFO TELNET access 81.21.249.100:23 -> 192.168.2.23:57234
Source: Traffic Snort IDS: 716 INFO TELNET access 178.206.214.19:23 -> 192.168.2.23:58388
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 109.186.36.253:23 -> 192.168.2.23:34818
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 109.186.36.253:23 -> 192.168.2.23:34818
Source: Traffic Snort IDS: 716 INFO TELNET access 178.206.214.19:23 -> 192.168.2.23:58396
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 108.39.178.247:23 -> 192.168.2.23:47468
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 108.39.178.247:23 -> 192.168.2.23:47468
Source: Traffic Snort IDS: 716 INFO TELNET access 178.206.214.19:23 -> 192.168.2.23:58406
Source: Traffic Snort IDS: 716 INFO TELNET access 178.206.214.19:23 -> 192.168.2.23:58426
Source: Traffic Snort IDS: 2023448 ET TROJAN Possible Linux.Mirai Login Attempt (ubnt) 192.168.2.23:36568 -> 190.60.19.213:23
Source: Traffic Snort IDS: 716 INFO TELNET access 178.206.214.19:23 -> 192.168.2.23:58456
Source: Traffic Snort IDS: 492 INFO TELNET login failed 121.254.204.242:23 -> 192.168.2.23:45996
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 59.127.75.126:23 -> 192.168.2.23:45374
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 59.127.75.126:23 -> 192.168.2.23:45374
Source: Traffic Snort IDS: 716 INFO TELNET access 178.206.214.19:23 -> 192.168.2.23:58478
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 109.186.36.253:23 -> 192.168.2.23:34886
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 109.186.36.253:23 -> 192.168.2.23:34886
Source: Traffic Snort IDS: 716 INFO TELNET access 1.251.57.101:23 -> 192.168.2.23:36772
Source: Traffic Snort IDS: 492 INFO TELNET login failed 121.254.204.242:23 -> 192.168.2.23:46076
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 109.186.36.253:23 -> 192.168.2.23:34966
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 109.186.36.253:23 -> 192.168.2.23:34966
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 59.127.75.126:23 -> 192.168.2.23:45486
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 59.127.75.126:23 -> 192.168.2.23:45486
Source: Traffic Snort IDS: 716 INFO TELNET access 60.213.32.54:23 -> 192.168.2.23:38210
Source: Traffic Snort IDS: 492 INFO TELNET login failed 121.254.204.242:23 -> 192.168.2.23:46126
Source: Traffic Snort IDS: 716 INFO TELNET access 1.218.245.230:23 -> 192.168.2.23:44910
Source: Traffic Snort IDS: 716 INFO TELNET access 81.21.249.100:23 -> 192.168.2.23:57444
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 109.186.36.253:23 -> 192.168.2.23:35036
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 109.186.36.253:23 -> 192.168.2.23:35036
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 59.127.75.126:23 -> 192.168.2.23:45564
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 59.127.75.126:23 -> 192.168.2.23:45564
Source: Traffic Snort IDS: 492 INFO TELNET login failed 121.254.204.242:23 -> 192.168.2.23:46168
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 108.39.178.247:23 -> 192.168.2.23:47722
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 108.39.178.247:23 -> 192.168.2.23:47722
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 109.186.36.253:23 -> 192.168.2.23:35094
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 109.186.36.253:23 -> 192.168.2.23:35094
Source: Traffic Snort IDS: 492 INFO TELNET login failed 121.254.204.242:23 -> 192.168.2.23:46222
Source: Traffic Snort IDS: 716 INFO TELNET access 1.251.57.101:23 -> 192.168.2.23:36944
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 59.127.75.126:23 -> 192.168.2.23:45640
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 59.127.75.126:23 -> 192.168.2.23:45640
Source: Traffic Snort IDS: 716 INFO TELNET access 187.8.88.19:23 -> 192.168.2.23:53706
Source: Traffic Snort IDS: 492 INFO TELNET login failed 120.210.132.132:23 -> 192.168.2.23:39756
Source: Traffic Snort IDS: 492 INFO TELNET login failed 121.254.204.242:23 -> 192.168.2.23:46288
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 109.186.36.253:23 -> 192.168.2.23:35168
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 109.186.36.253:23 -> 192.168.2.23:35168
Source: Traffic Snort IDS: 2023448 ET TROJAN Possible Linux.Mirai Login Attempt (ubnt) 192.168.2.23:44362 -> 63.78.213.106:23
Source: Traffic Snort IDS: 716 INFO TELNET access 60.213.32.54:23 -> 192.168.2.23:38488
Source: Traffic Snort IDS: 492 INFO TELNET login failed 120.210.132.132:23 -> 192.168.2.23:39910
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 186.190.238.29:23 -> 192.168.2.23:52178
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 186.190.238.29:23 -> 192.168.2.23:52178
Source: Traffic Snort IDS: 492 INFO TELNET login failed 121.254.204.242:23 -> 192.168.2.23:46442
Source: Traffic Snort IDS: 716 INFO TELNET access 1.218.245.230:23 -> 192.168.2.23:45226
Source: Traffic Snort IDS: 716 INFO TELNET access 81.21.249.100:23 -> 192.168.2.23:57786
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 59.127.75.126:23 -> 192.168.2.23:45824
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 59.127.75.126:23 -> 192.168.2.23:45824
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 5.134.192.143:23 -> 192.168.2.23:46000
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 5.134.192.143:23 -> 192.168.2.23:46000
Source: Traffic Snort IDS: 716 INFO TELNET access 122.228.187.182:23 -> 192.168.2.23:59192
Source: Traffic Snort IDS: 2023448 ET TROJAN Possible Linux.Mirai Login Attempt (ubnt) 192.168.2.23:44526 -> 63.78.213.106:23
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 109.186.36.253:23 -> 192.168.2.23:35352
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 109.186.36.253:23 -> 192.168.2.23:35352
Source: Traffic Snort IDS: 716 INFO TELNET access 91.155.104.45:23 -> 192.168.2.23:44134
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 113.174.140.208:23 -> 192.168.2.23:56482
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 113.174.140.208:23 -> 192.168.2.23:56482
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 186.190.238.29:23 -> 192.168.2.23:52270
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 186.190.238.29:23 -> 192.168.2.23:52270
Source: Traffic Snort IDS: 404 ICMP Destination Unreachable Protocol Unreachable 87.60.19.234: -> 192.168.2.23:
Source: Traffic Snort IDS: 2023433 ET TROJAN Possible Linux.Mirai Login Attempt (7ujMko0admin) 192.168.2.23:37136 -> 190.60.19.213:23
Source: Traffic Snort IDS: 492 INFO TELNET login failed 103.192.76.26:23 -> 192.168.2.23:52556
Source: Traffic Snort IDS: 492 INFO TELNET login failed 122.228.187.182:23 -> 192.168.2.23:59192
Source: Traffic Snort IDS: 492 INFO TELNET login failed 61.136.141.5:23 -> 192.168.2.23:49242
Source: Traffic Snort IDS: 716 INFO TELNET access 122.228.187.182:23 -> 192.168.2.23:59276
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 186.190.238.29:23 -> 192.168.2.23:52328
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 186.190.238.29:23 -> 192.168.2.23:52328
Source: Traffic Snort IDS: 492 INFO TELNET login failed 120.210.132.132:23 -> 192.168.2.23:40072
Source: Traffic Snort IDS: 716 INFO TELNET access 59.124.8.47:23 -> 192.168.2.23:56656
Source: Traffic Snort IDS: 492 INFO TELNET login failed 122.228.187.182:23 -> 192.168.2.23:59276
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 109.186.36.253:23 -> 192.168.2.23:35484
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 109.186.36.253:23 -> 192.168.2.23:35484
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 59.127.75.126:23 -> 192.168.2.23:45998
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 59.127.75.126:23 -> 192.168.2.23:45998
Source: Traffic Snort IDS: 492 INFO TELNET login failed 61.136.141.5:23 -> 192.168.2.23:49386
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 186.190.238.29:23 -> 192.168.2.23:52422
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 186.190.238.29:23 -> 192.168.2.23:52422
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 188.119.49.10:23 -> 192.168.2.23:52888
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 188.119.49.10:23 -> 192.168.2.23:52888
Source: Traffic Snort IDS: 716 INFO TELNET access 122.228.187.182:23 -> 192.168.2.23:59428
Uses known network protocols on non-standard ports
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 34110
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 34112
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 34116
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 34118
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 34122
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 34124
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 34126
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 34128
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 34136
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 34140
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 58262
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 58264
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 58270
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 58274
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 58276
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45940
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 58282
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45946
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 58286
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45950
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 58290
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45954
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 58294
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45960
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 58300
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45964
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45966
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45970
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45976
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45982
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45168
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45170
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45172
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45174
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45184
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45186
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45190
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39914
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45196
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39922
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45208
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39928
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45216
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39936
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39946
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39956
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39962
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39970
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39982
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39990
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 46936
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 46942
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 46950
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 46952
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 46958
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 46964
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 46970
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 46978
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 46986
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 46994
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
Detected TCP or UDP traffic on non-standard ports
Source: global traffic TCP traffic: 192.168.2.23:33146 -> 128.199.243.41:1312
Sample listens on a socket
Source: /tmp/sora.arm7 (PID: 5242) Socket: 0.0.0.0::0 Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) Socket: 0.0.0.0::0 Jump to behavior
Source: /usr/sbin/sshd (PID: 5274) Socket: 0.0.0.0::22 Jump to behavior
Source: /usr/sbin/sshd (PID: 5274) Socket: [::]::22 Jump to behavior
Source: unknown Network traffic detected: HTTP traffic on port 43928 -> 443
Source: unknown Network traffic detected: HTTP traffic on port 42836 -> 443
Source: unknown TCP traffic detected without corresponding DNS query: 128.199.243.41
Source: unknown TCP traffic detected without corresponding DNS query: 222.140.219.5
Source: unknown TCP traffic detected without corresponding DNS query: 252.214.35.97
Source: unknown TCP traffic detected without corresponding DNS query: 169.8.20.4
Source: unknown TCP traffic detected without corresponding DNS query: 155.223.51.109
Source: unknown TCP traffic detected without corresponding DNS query: 42.131.237.138
Source: unknown TCP traffic detected without corresponding DNS query: 191.127.186.244
Source: unknown TCP traffic detected without corresponding DNS query: 122.80.228.224
Source: unknown TCP traffic detected without corresponding DNS query: 222.33.193.194
Source: unknown TCP traffic detected without corresponding DNS query: 5.57.145.87
Source: unknown TCP traffic detected without corresponding DNS query: 157.79.58.251
Source: unknown TCP traffic detected without corresponding DNS query: 74.143.129.21
Source: unknown TCP traffic detected without corresponding DNS query: 183.24.19.102
Source: unknown TCP traffic detected without corresponding DNS query: 14.44.21.76
Source: unknown TCP traffic detected without corresponding DNS query: 159.149.104.79
Source: unknown TCP traffic detected without corresponding DNS query: 122.140.92.0
Source: unknown TCP traffic detected without corresponding DNS query: 62.185.215.67
Source: unknown TCP traffic detected without corresponding DNS query: 62.41.93.155
Source: unknown TCP traffic detected without corresponding DNS query: 14.252.253.48
Source: unknown TCP traffic detected without corresponding DNS query: 154.3.132.22
Source: unknown TCP traffic detected without corresponding DNS query: 195.90.3.2
Source: unknown TCP traffic detected without corresponding DNS query: 136.28.48.183
Source: unknown TCP traffic detected without corresponding DNS query: 251.59.130.41
Source: unknown TCP traffic detected without corresponding DNS query: 242.94.57.124
Source: unknown TCP traffic detected without corresponding DNS query: 121.174.8.56
Source: unknown TCP traffic detected without corresponding DNS query: 37.248.219.83
Source: unknown TCP traffic detected without corresponding DNS query: 8.117.57.95
Source: unknown TCP traffic detected without corresponding DNS query: 90.174.206.18
Source: unknown TCP traffic detected without corresponding DNS query: 74.227.140.102
Source: unknown TCP traffic detected without corresponding DNS query: 154.129.38.115
Source: unknown TCP traffic detected without corresponding DNS query: 171.136.251.77
Source: unknown TCP traffic detected without corresponding DNS query: 157.46.4.171
Source: unknown TCP traffic detected without corresponding DNS query: 18.62.67.52
Source: unknown TCP traffic detected without corresponding DNS query: 34.142.97.118
Source: unknown TCP traffic detected without corresponding DNS query: 38.126.149.110
Source: unknown TCP traffic detected without corresponding DNS query: 90.180.218.209
Source: unknown TCP traffic detected without corresponding DNS query: 135.153.100.11
Source: unknown TCP traffic detected without corresponding DNS query: 27.248.76.68
Source: unknown TCP traffic detected without corresponding DNS query: 90.243.31.211
Source: unknown TCP traffic detected without corresponding DNS query: 164.149.118.95
Source: unknown TCP traffic detected without corresponding DNS query: 75.83.232.229
Source: unknown TCP traffic detected without corresponding DNS query: 166.19.96.132
Source: unknown TCP traffic detected without corresponding DNS query: 73.40.54.218
Source: unknown TCP traffic detected without corresponding DNS query: 42.161.172.203
Source: unknown TCP traffic detected without corresponding DNS query: 142.161.113.178
Source: unknown TCP traffic detected without corresponding DNS query: 196.79.170.181
Source: unknown TCP traffic detected without corresponding DNS query: 27.123.29.201
Source: unknown TCP traffic detected without corresponding DNS query: 81.249.133.35
Source: unknown TCP traffic detected without corresponding DNS query: 5.72.70.26
Source: unknown TCP traffic detected without corresponding DNS query: 69.239.28.185
Source: sora.arm7 String found in binary or memory: http://upx.sf.net

System Summary:

barindex
Sample contains only a LOAD segment without any section mappings
Source: LOAD without section mappings Program segment: 0x8000
Yara signature match
Source: sora.arm7, type: SAMPLE Matched rule: SUSP_ELF_LNX_UPX_Compressed_File date = 2018-12-12, author = Florian Roth, description = Detects a suspicious ELF binary with UPX compression, reference = Internal Research, score = 038ff8b2fef16f8ee9d70e6c219c5f380afe1a21761791e8cbda21fa4d09fdb4
Sample tries to kill a process (SIGKILL)
Source: /tmp/sora.arm7 (PID: 5242) SIGKILL sent: pid: 936, result: successful Jump to behavior
Source: classification engine Classification label: mal72.troj.evad.linARM7@0/2@0/0
Source: sora.arm7 Joe Sandbox Cloud Basic: Detection: clean Score: 0 Perma Link

Data Obfuscation:

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

Persistence and Installation Behavior:

barindex
Enumerates processes within the "proc" file system
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/491/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/793/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/772/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/796/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/774/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/797/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/777/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/799/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/658/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/912/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/759/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/936/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/918/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/1/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/761/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/785/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/884/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/720/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/721/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/788/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/789/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/800/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/801/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/847/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5242) File opened: /proc/904/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/5261/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/5262/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/5263/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/5264/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/5265/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/5266/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/5267/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/5268/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/2033/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1582/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/2275/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/5260/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1612/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1579/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1699/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1335/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1698/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/2028/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1334/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1576/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/2302/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/3236/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/2025/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/2146/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/912/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/759/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/2307/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/918/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/5272/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/5273/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1594/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/2285/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/2281/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/5270/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/5271/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1349/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1623/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/761/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1622/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/884/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1983/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/2038/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1586/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1465/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1344/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1860/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1463/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/2156/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/800/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/5269/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/801/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1629/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1627/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1900/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/491/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/2294/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/2050/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/5040/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1877/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/772/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1633/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1599/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1632/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1477/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/774/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1476/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1872/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/2048/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1475/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/2289/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/777/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/658/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1639/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1638/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/2208/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/2180/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1809/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1494/fd Jump to behavior
Source: /tmp/sora.arm7 (PID: 5248) File opened: /proc/1890/fd Jump to behavior

Hooking and other Techniques for Hiding and Protection:

barindex
Uses known network protocols on non-standard ports
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 34110
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 34112
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 34116
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 34118
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 34122
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 34124
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 34126
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 34128
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 34136
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 34140
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 58262
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 58264
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 58270
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 58274
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 58276
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45940
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 58282
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45946
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 58286
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45950
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 58290
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45954
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 58294
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45960
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 58300
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45964
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45966
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45970
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45976
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45982
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45168
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45170
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45172
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45174
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45184
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45186
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45190
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39914
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45196
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39922
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45208
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39928
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 45216
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39936
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39946
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39956
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39962
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39970
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39982
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39990
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 46936
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 46942
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 46950
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 46952
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 46958
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 46964
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 46970
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 46978
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 46986
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 46994

Malware Analysis System Evasion:

barindex
Uses the "uname" system call to query kernel version information (possible evasion)
Source: /tmp/sora.arm7 (PID: 5240) Queries kernel information via 'uname': Jump to behavior
Source: sora.arm7, 5240.1.00000000ec5b085b.0000000030322648.rw-.sdmp Binary or memory string: U!/etc/qemu-binfmt/arm
Source: sora.arm7, 5240.1.00000000ec5b085b.0000000030322648.rw-.sdmp Binary or memory string: /etc/qemu-binfmt/arm
Source: sora.arm7, 5240.1.0000000057ff4a10.0000000007cc84c3.rw-.sdmp Binary or memory string: /usr/bin/qemu-arm
Source: sora.arm7, 5240.1.0000000057ff4a10.0000000007cc84c3.rw-.sdmp Binary or memory string: Vx86_64/usr/bin/qemu-arm/tmp/sora.arm7SUDO_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/sora.arm7

Stealing of Sensitive Information:

barindex
Yara detected Mirai
Source: Yara match File source: dump.pcap, type: PCAP

Remote Access Functionality:

barindex
Yara detected Mirai
Source: Yara match File source: dump.pcap, type: PCAP
  • No. of IPs < 25%
  • 25% < No. of IPs < 50%
  • 50% < No. of IPs < 75%
  • 75% < No. of IPs