Linux Analysis Report fVA3Q44QAK

Overview

General Information

Sample Name: fVA3Q44QAK
Analysis ID: 553483
MD5: cd6521521289846e8001d5f05cf0e10d
SHA1: ecb03ba794a579a02ad8e0ef94b29ebed527a155
SHA256: 00a6f460395d2f545eba81ead528fcf2883582412affb7b052e7fef3478361c0
Tags: 32elfintelmirai
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
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
Executes the "rm" command used to delete files or directories
Sample tries to kill a process (SIGKILL)

Classification

AV Detection:

barindex
Multi AV Scanner detection for submitted file
Source: fVA3Q44QAK Virustotal: Detection: 36% Perma Link
Source: fVA3Q44QAK ReversingLabs: Detection: 51%

Networking:

barindex
Snort IDS alert for network traffic (e.g. based on Emerging Threat rules)
Source: Traffic Snort IDS: 716 INFO TELNET access 41.57.43.2:23 -> 192.168.2.23:52626
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 41.57.43.2:23 -> 192.168.2.23:52626
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 41.57.43.2:23 -> 192.168.2.23:52626
Source: Traffic Snort IDS: 716 INFO TELNET access 41.57.43.2:23 -> 192.168.2.23:52648
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 41.57.43.2:23 -> 192.168.2.23:52648
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 41.57.43.2:23 -> 192.168.2.23:52648
Source: Traffic Snort IDS: 716 INFO TELNET access 177.7.221.41:23 -> 192.168.2.23:59270
Source: Traffic Snort IDS: 2023433 ET TROJAN Possible Linux.Mirai Login Attempt (7ujMko0admin) 192.168.2.23:59270 -> 177.7.221.41:23
Source: Traffic Snort IDS: 716 INFO TELNET access 41.57.43.2:23 -> 192.168.2.23:52658
Source: Traffic Snort IDS: 716 INFO TELNET access 177.7.221.41:23 -> 192.168.2.23:59276
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 41.57.43.2:23 -> 192.168.2.23:52658
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 41.57.43.2:23 -> 192.168.2.23:52658
Source: Traffic Snort IDS: 716 INFO TELNET access 177.7.221.41:23 -> 192.168.2.23:59280
Source: Traffic Snort IDS: 716 INFO TELNET access 177.7.221.41:23 -> 192.168.2.23:59292
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 178.219.113.60:23 -> 192.168.2.23:41272
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 178.219.113.60:23 -> 192.168.2.23:41272
Source: Traffic Snort IDS: 716 INFO TELNET access 41.57.43.2:23 -> 192.168.2.23:52684
Source: Traffic Snort IDS: 716 INFO TELNET access 177.7.221.41:23 -> 192.168.2.23:59346
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 41.57.43.2:23 -> 192.168.2.23:52684
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 41.57.43.2:23 -> 192.168.2.23:52684
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 178.219.113.60:23 -> 192.168.2.23:41390
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 178.219.113.60:23 -> 192.168.2.23:41390
Source: Traffic Snort IDS: 716 INFO TELNET access 41.57.43.2:23 -> 192.168.2.23:52836
Source: Traffic Snort IDS: 492 INFO TELNET login failed 223.8.49.214:23 -> 192.168.2.23:34430
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 41.57.43.2:23 -> 192.168.2.23:52836
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 41.57.43.2:23 -> 192.168.2.23:52836
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 178.219.113.60:23 -> 192.168.2.23:41482
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 178.219.113.60:23 -> 192.168.2.23:41482
Source: Traffic Snort IDS: 716 INFO TELNET access 41.57.43.2:23 -> 192.168.2.23:52978
Source: Traffic Snort IDS: 492 INFO TELNET login failed 218.75.91.70:23 -> 192.168.2.23:44108
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 41.57.43.2:23 -> 192.168.2.23:52978
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 41.57.43.2:23 -> 192.168.2.23:52978
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 178.219.113.60:23 -> 192.168.2.23:41600
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 178.219.113.60:23 -> 192.168.2.23:41600
Source: Traffic Snort IDS: 492 INFO TELNET login failed 218.75.91.70:23 -> 192.168.2.23:44198
Source: Traffic Snort IDS: 716 INFO TELNET access 41.57.43.2:23 -> 192.168.2.23:53088
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 178.219.113.60:23 -> 192.168.2.23:41692
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 178.219.113.60:23 -> 192.168.2.23:41692
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 41.57.43.2:23 -> 192.168.2.23:53088
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 41.57.43.2:23 -> 192.168.2.23:53088
Source: Traffic Snort IDS: 492 INFO TELNET login failed 218.75.91.70:23 -> 192.168.2.23:44220
Source: Traffic Snort IDS: 716 INFO TELNET access 41.57.43.2:23 -> 192.168.2.23:53138
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 178.219.113.60:23 -> 192.168.2.23:41734
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 178.219.113.60:23 -> 192.168.2.23:41734
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 41.57.43.2:23 -> 192.168.2.23:53138
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 41.57.43.2:23 -> 192.168.2.23:53138
Source: Traffic Snort IDS: 492 INFO TELNET login failed 218.75.91.70:23 -> 192.168.2.23:44296
Source: Traffic Snort IDS: 404 ICMP Destination Unreachable Protocol Unreachable 190.111.231.121: -> 192.168.2.23:
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 178.219.113.60:23 -> 192.168.2.23:41778
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 178.219.113.60:23 -> 192.168.2.23:41778
Source: Traffic Snort IDS: 716 INFO TELNET access 41.57.43.2:23 -> 192.168.2.23:53190
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 93.49.107.156:23 -> 192.168.2.23:43966
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 93.49.107.156:23 -> 192.168.2.23:43966
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 41.57.43.2:23 -> 192.168.2.23:53190
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 41.57.43.2:23 -> 192.168.2.23:53190
Source: Traffic Snort IDS: 492 INFO TELNET login failed 218.75.91.70:23 -> 192.168.2.23:44352
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 178.219.113.60:23 -> 192.168.2.23:41830
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 178.219.113.60:23 -> 192.168.2.23:41830
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 93.49.107.156:23 -> 192.168.2.23:44020
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 93.49.107.156:23 -> 192.168.2.23:44020
Source: Traffic Snort IDS: 716 INFO TELNET access 41.57.43.2:23 -> 192.168.2.23:53284
Source: Traffic Snort IDS: 2023448 ET TROJAN Possible Linux.Mirai Login Attempt (ubnt) 192.168.2.23:41898 -> 178.219.113.60:23
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 41.57.43.2:23 -> 192.168.2.23:53284
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 41.57.43.2:23 -> 192.168.2.23:53284
Source: Traffic Snort IDS: 492 INFO TELNET login failed 218.75.91.70:23 -> 192.168.2.23:44426
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 178.219.113.60:23 -> 192.168.2.23:41898
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 178.219.113.60:23 -> 192.168.2.23:41898
Source: Traffic Snort IDS: 492 INFO TELNET login failed 120.198.210.199:23 -> 192.168.2.23:50898
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 93.49.107.156:23 -> 192.168.2.23:44100
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 93.49.107.156:23 -> 192.168.2.23:44100
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 178.219.113.60:23 -> 192.168.2.23:41944
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 178.219.113.60:23 -> 192.168.2.23:41944
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 93.49.107.156:23 -> 192.168.2.23:44132
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 93.49.107.156:23 -> 192.168.2.23:44132
Source: Traffic Snort IDS: 492 INFO TELNET login failed 218.75.91.70:23 -> 192.168.2.23:44482
Source: Traffic Snort IDS: 716 INFO TELNET access 27.35.231.182:23 -> 192.168.2.23:34932
Source: Traffic Snort IDS: 492 INFO TELNET login failed 221.2.193.110:23 -> 192.168.2.23:54124
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 27.35.231.182:23 -> 192.168.2.23:34932
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 27.35.231.182:23 -> 192.168.2.23:34932
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 93.49.107.156:23 -> 192.168.2.23:44180
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 93.49.107.156:23 -> 192.168.2.23:44180
Source: Traffic Snort IDS: 492 INFO TELNET login failed 221.2.193.110:23 -> 192.168.2.23:54182
Source: Traffic Snort IDS: 716 INFO TELNET access 27.35.231.182:23 -> 192.168.2.23:35018
Source: Traffic Snort IDS: 492 INFO TELNET login failed 218.75.91.70:23 -> 192.168.2.23:44568
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 93.49.107.156:23 -> 192.168.2.23:44236
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 93.49.107.156:23 -> 192.168.2.23:44236
Source: Traffic Snort IDS: 716 INFO TELNET access 41.181.140.130:23 -> 192.168.2.23:57582
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 27.35.231.182:23 -> 192.168.2.23:35018
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 27.35.231.182:23 -> 192.168.2.23:35018
Source: Traffic Snort IDS: 492 INFO TELNET login failed 218.75.91.70:23 -> 192.168.2.23:44616
Source: Traffic Snort IDS: 492 INFO TELNET login failed 221.2.193.110:23 -> 192.168.2.23:54230
Source: Traffic Snort IDS: 716 INFO TELNET access 201.20.102.53:23 -> 192.168.2.23:46814
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 93.49.107.156:23 -> 192.168.2.23:44284
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 93.49.107.156:23 -> 192.168.2.23:44284
Source: Traffic Snort IDS: 492 INFO TELNET login failed 201.20.102.53:23 -> 192.168.2.23:46814
Source: Traffic Snort IDS: 716 INFO TELNET access 27.35.231.182:23 -> 192.168.2.23:35082
Source: Traffic Snort IDS: 492 INFO TELNET login failed 221.2.193.110:23 -> 192.168.2.23:54248
Source: Traffic Snort IDS: 492 INFO TELNET login failed 218.75.91.70:23 -> 192.168.2.23:44642
Source: Traffic Snort IDS: 716 INFO TELNET access 201.20.102.53:23 -> 192.168.2.23:46832
Source: Traffic Snort IDS: 492 INFO TELNET login failed 201.20.102.53:23 -> 192.168.2.23:46832
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 93.49.107.156:23 -> 192.168.2.23:44308
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 93.49.107.156:23 -> 192.168.2.23:44308
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 27.35.231.182:23 -> 192.168.2.23:35082
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 27.35.231.182:23 -> 192.168.2.23:35082
Source: Traffic Snort IDS: 716 INFO TELNET access 201.20.102.53:23 -> 192.168.2.23:46876
Source: Traffic Snort IDS: 492 INFO TELNET login failed 221.2.193.110:23 -> 192.168.2.23:54306
Source: Traffic Snort IDS: 492 INFO TELNET login failed 201.20.102.53:23 -> 192.168.2.23:46876
Source: Traffic Snort IDS: 716 INFO TELNET access 189.115.194.129:23 -> 192.168.2.23:57130
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 93.49.107.156:23 -> 192.168.2.23:44362
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 93.49.107.156:23 -> 192.168.2.23:44362
Source: Traffic Snort IDS: 716 INFO TELNET access 183.236.171.20:23 -> 192.168.2.23:55824
Source: Traffic Snort IDS: 716 INFO TELNET access 201.20.102.53:23 -> 192.168.2.23:46982
Source: Traffic Snort IDS: 492 INFO TELNET login failed 189.115.194.129:23 -> 192.168.2.23:57130
Source: Traffic Snort IDS: 492 INFO TELNET login failed 201.20.102.53:23 -> 192.168.2.23:46982
Source: Traffic Snort IDS: 716 INFO TELNET access 27.35.231.182:23 -> 192.168.2.23:35228
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 183.236.171.20:23 -> 192.168.2.23:55824
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 183.236.171.20:23 -> 192.168.2.23:55824
Source: Traffic Snort IDS: 716 INFO TELNET access 189.115.194.129:23 -> 192.168.2.23:57252
Source: Traffic Snort IDS: 492 INFO TELNET login failed 221.2.193.110:23 -> 192.168.2.23:54484
Source: Traffic Snort IDS: 716 INFO TELNET access 201.20.102.53:23 -> 192.168.2.23:47096
Source: Traffic Snort IDS: 716 INFO TELNET access 210.165.140.156:23 -> 192.168.2.23:42788
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 93.49.107.156:23 -> 192.168.2.23:44536
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 93.49.107.156:23 -> 192.168.2.23:44536
Source: Traffic Snort IDS: 492 INFO TELNET login failed 189.115.194.129:23 -> 192.168.2.23:57252
Source: Traffic Snort IDS: 492 INFO TELNET login failed 201.20.102.53:23 -> 192.168.2.23:47096
Source: Traffic Snort IDS: 716 INFO TELNET access 106.240.171.6:23 -> 192.168.2.23:56382
Source: Traffic Snort IDS: 492 INFO TELNET login failed 189.112.121.182:23 -> 192.168.2.23:44974
Source: Traffic Snort IDS: 716 INFO TELNET access 183.236.171.20:23 -> 192.168.2.23:56072
Source: Traffic Snort IDS: 716 INFO TELNET access 189.115.194.129:23 -> 192.168.2.23:57416
Source: Traffic Snort IDS: 716 INFO TELNET access 201.20.102.53:23 -> 192.168.2.23:47240
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 27.35.231.182:23 -> 192.168.2.23:35228
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 27.35.231.182:23 -> 192.168.2.23:35228
Source: Traffic Snort IDS: 492 INFO TELNET login failed 201.20.102.53:23 -> 192.168.2.23:47240
Source: Traffic Snort IDS: 492 INFO TELNET login failed 189.115.194.129:23 -> 192.168.2.23:57416
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 183.236.171.20:23 -> 192.168.2.23:56072
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 183.236.171.20:23 -> 192.168.2.23:56072
Source: Traffic Snort IDS: 716 INFO TELNET access 60.14.56.69:23 -> 192.168.2.23:57868
Source: Traffic Snort IDS: 492 INFO TELNET login failed 221.2.193.110:23 -> 192.168.2.23:54710
Source: Traffic Snort IDS: 716 INFO TELNET access 189.115.194.129:23 -> 192.168.2.23:57480
Source: Traffic Snort IDS: 716 INFO TELNET access 201.20.102.53:23 -> 192.168.2.23:47298
Source: Traffic Snort IDS: 716 INFO TELNET access 23.91.241.26:23 -> 192.168.2.23:38630
Source: Traffic Snort IDS: 716 INFO TELNET access 211.160.177.2:23 -> 192.168.2.23:44084
Source: Traffic Snort IDS: 716 INFO TELNET access 27.35.231.182:23 -> 192.168.2.23:35580
Source: Traffic Snort IDS: 716 INFO TELNET access 60.14.56.69:23 -> 192.168.2.23:57874
Source: Traffic Snort IDS: 492 INFO TELNET login failed 201.20.102.53:23 -> 192.168.2.23:47298
Source: Traffic Snort IDS: 492 INFO TELNET login failed 23.91.241.26:23 -> 192.168.2.23:38630
Source: Traffic Snort IDS: 492 INFO TELNET login failed 189.115.194.129:23 -> 192.168.2.23:57480
Source: Traffic Snort IDS: 716 INFO TELNET access 60.14.56.69:23 -> 192.168.2.23:57948
Source: Traffic Snort IDS: 492 INFO TELNET login failed 211.160.177.2:23 -> 192.168.2.23:44084
Source: Traffic Snort IDS: 716 INFO TELNET access 60.14.56.69:23 -> 192.168.2.23:57962
Source: Traffic Snort IDS: 716 INFO TELNET access 111.163.72.218:23 -> 192.168.2.23:34104
Source: Traffic Snort IDS: 716 INFO TELNET access 183.236.171.20:23 -> 192.168.2.23:56238
Source: Traffic Snort IDS: 716 INFO TELNET access 60.14.56.69:23 -> 192.168.2.23:58000
Source: Traffic Snort IDS: 716 INFO TELNET access 23.91.241.26:23 -> 192.168.2.23:38750
Source: Traffic Snort IDS: 716 INFO TELNET access 189.115.194.129:23 -> 192.168.2.23:57612
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 27.35.231.182:23 -> 192.168.2.23:35580
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 27.35.231.182:23 -> 192.168.2.23:35580
Source: Traffic Snort IDS: 716 INFO TELNET access 201.20.102.53:23 -> 192.168.2.23:47428
Source: Traffic Snort IDS: 716 INFO TELNET access 60.14.56.69:23 -> 192.168.2.23:58024
Source: Traffic Snort IDS: 716 INFO TELNET access 211.160.177.2:23 -> 192.168.2.23:44208
Source: Traffic Snort IDS: 492 INFO TELNET login failed 221.2.193.110:23 -> 192.168.2.23:54860
Source: Traffic Snort IDS: 492 INFO TELNET login failed 23.91.241.26:23 -> 192.168.2.23:38750
Source: Traffic Snort IDS: 716 INFO TELNET access 60.14.56.69:23 -> 192.168.2.23:58040
Source: Traffic Snort IDS: 716 INFO TELNET access 111.163.72.218:23 -> 192.168.2.23:34178
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 183.236.171.20:23 -> 192.168.2.23:56238
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 183.236.171.20:23 -> 192.168.2.23:56238
Source: Traffic Snort IDS: 492 INFO TELNET login failed 201.20.102.53:23 -> 192.168.2.23:47428
Source: Traffic Snort IDS: 716 INFO TELNET access 60.14.56.69:23 -> 192.168.2.23:58048
Source: Traffic Snort IDS: 492 INFO TELNET login failed 189.115.194.129:23 -> 192.168.2.23:57612
Source: Traffic Snort IDS: 492 INFO TELNET login failed 211.160.177.2:23 -> 192.168.2.23:44208
Source: Traffic Snort IDS: 716 INFO TELNET access 60.14.56.69:23 -> 192.168.2.23:58062
Source: Traffic Snort IDS: 716 INFO TELNET access 23.91.241.26:23 -> 192.168.2.23:38816
Source: Traffic Snort IDS: 716 INFO TELNET access 60.14.56.69:23 -> 192.168.2.23:58078
Source: Traffic Snort IDS: 716 INFO TELNET access 189.115.194.129:23 -> 192.168.2.23:57712
Source: Traffic Snort IDS: 716 INFO TELNET access 201.20.102.53:23 -> 192.168.2.23:47524
Source: Traffic Snort IDS: 716 INFO TELNET access 211.160.177.2:23 -> 192.168.2.23:44294
Source: Traffic Snort IDS: 492 INFO TELNET login failed 23.91.241.26:23 -> 192.168.2.23:38816
Uses known network protocols on non-standard ports
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 41240
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 41248
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 41258
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 41278
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 41288
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 41306
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 41330
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 41334
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 41338
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 41340
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: global traffic TCP traffic: 192.168.2.23:39274 -> 34.249.145.219:443
Detected TCP or UDP traffic on non-standard ports
Source: global traffic TCP traffic: 192.168.2.23:51422 -> 136.144.41.15:1312
Source: unknown Network traffic detected: HTTP traffic on port 43928 -> 443
Source: unknown Network traffic detected: HTTP traffic on port 42836 -> 443
Source: unknown Network traffic detected: HTTP traffic on port 39274 -> 443
Source: unknown TCP traffic detected without corresponding DNS query: 136.144.41.15
Source: unknown TCP traffic detected without corresponding DNS query: 86.114.208.209
Source: unknown TCP traffic detected without corresponding DNS query: 243.174.106.35
Source: unknown TCP traffic detected without corresponding DNS query: 67.49.248.210
Source: unknown TCP traffic detected without corresponding DNS query: 16.114.55.95
Source: unknown TCP traffic detected without corresponding DNS query: 197.22.95.112
Source: unknown TCP traffic detected without corresponding DNS query: 35.102.24.95
Source: unknown TCP traffic detected without corresponding DNS query: 126.36.123.32
Source: unknown TCP traffic detected without corresponding DNS query: 116.151.253.46
Source: unknown TCP traffic detected without corresponding DNS query: 194.173.176.105
Source: unknown TCP traffic detected without corresponding DNS query: 130.193.17.243
Source: unknown TCP traffic detected without corresponding DNS query: 103.222.112.39
Source: unknown TCP traffic detected without corresponding DNS query: 181.22.75.4
Source: unknown TCP traffic detected without corresponding DNS query: 124.97.161.209
Source: unknown TCP traffic detected without corresponding DNS query: 39.108.62.151
Source: unknown TCP traffic detected without corresponding DNS query: 168.109.209.2
Source: unknown TCP traffic detected without corresponding DNS query: 75.119.233.6
Source: unknown TCP traffic detected without corresponding DNS query: 82.61.135.125
Source: unknown TCP traffic detected without corresponding DNS query: 147.228.81.150
Source: unknown TCP traffic detected without corresponding DNS query: 193.130.162.15
Source: unknown TCP traffic detected without corresponding DNS query: 151.221.106.243
Source: unknown TCP traffic detected without corresponding DNS query: 13.95.76.153
Source: unknown TCP traffic detected without corresponding DNS query: 243.232.160.119
Source: unknown TCP traffic detected without corresponding DNS query: 202.25.239.217
Source: unknown TCP traffic detected without corresponding DNS query: 63.242.170.205
Source: unknown TCP traffic detected without corresponding DNS query: 58.17.227.90
Source: unknown TCP traffic detected without corresponding DNS query: 251.104.219.53
Source: unknown TCP traffic detected without corresponding DNS query: 255.21.84.13
Source: unknown TCP traffic detected without corresponding DNS query: 9.97.192.97
Source: unknown TCP traffic detected without corresponding DNS query: 63.127.95.221
Source: unknown TCP traffic detected without corresponding DNS query: 128.31.239.87
Source: unknown TCP traffic detected without corresponding DNS query: 194.50.7.65
Source: unknown TCP traffic detected without corresponding DNS query: 172.155.57.146
Source: unknown TCP traffic detected without corresponding DNS query: 92.232.14.56
Source: unknown TCP traffic detected without corresponding DNS query: 119.167.39.218
Source: unknown TCP traffic detected without corresponding DNS query: 200.237.13.70
Source: unknown TCP traffic detected without corresponding DNS query: 17.135.153.56
Source: unknown TCP traffic detected without corresponding DNS query: 155.245.80.45
Source: unknown TCP traffic detected without corresponding DNS query: 170.170.202.40
Source: unknown TCP traffic detected without corresponding DNS query: 133.95.172.234
Source: unknown TCP traffic detected without corresponding DNS query: 75.48.59.107
Source: unknown TCP traffic detected without corresponding DNS query: 73.39.38.124
Source: unknown TCP traffic detected without corresponding DNS query: 255.1.109.214
Source: unknown TCP traffic detected without corresponding DNS query: 123.46.224.16
Source: unknown TCP traffic detected without corresponding DNS query: 78.140.215.45
Source: unknown TCP traffic detected without corresponding DNS query: 4.77.72.12
Source: unknown TCP traffic detected without corresponding DNS query: 23.138.112.226
Source: unknown TCP traffic detected without corresponding DNS query: 41.66.188.103
Source: unknown TCP traffic detected without corresponding DNS query: 221.206.147.174
Source: unknown TCP traffic detected without corresponding DNS query: 61.141.254.232
Source: fVA3Q44QAK 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: 0xc01000
Sample tries to kill a process (SIGKILL)
Source: /tmp/fVA3Q44QAK (PID: 5219) SIGKILL sent: pid: 936, result: successful Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) SIGKILL sent: pid: 936, result: successful Jump to behavior
Source: classification engine Classification label: mal72.troj.evad.lin@0/0@0/0

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/fVA3Q44QAK (PID: 5222) File opened: /proc/5222/exe Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/491/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/793/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/772/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/796/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/774/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/797/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/777/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/799/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/658/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/912/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/759/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/936/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/918/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/1/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/761/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/785/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/884/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/720/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/721/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/788/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/789/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/800/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/801/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/847/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5222) File opened: /proc/904/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/491/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/793/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/772/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/796/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/774/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/797/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/777/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/799/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/658/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/912/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/759/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/936/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/5219/exe Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/918/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/1/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/761/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/785/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/884/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/720/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/721/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/788/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/789/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/800/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/801/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/847/fd Jump to behavior
Source: /tmp/fVA3Q44QAK (PID: 5219) File opened: /proc/904/fd Jump to behavior
Executes the "rm" command used to delete files or directories
Source: /usr/bin/dash (PID: 5264) Rm executable: /usr/bin/rm -> rm -f /tmp/tmp.FZJy5QRkED /tmp/tmp.Cx4p8ienxO /tmp/tmp.ayYQw5P6KC 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 -> 41240
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 41248
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 41258
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 41278
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 41288
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 41306
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 41330
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 41334
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 41338
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 41340

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