Linux Analysis Report MPnFvIsvJp

Overview

General Information

Sample Name: MPnFvIsvJp
Analysis ID: 507413
MD5: 2af6167aa24d06f1795c507272d02916
SHA1: 24092366777f504a441a27f3555ca64e00719528
SHA256: 4c6ea0ba603fe0b1d8a97485afcf756d6e2a2630dfe18ee33353a17588924741
Tags: 32elfmiraipowerpc
Infos:

Most interesting Screenshot:

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
Uses known network protocols on non-standard ports
Sample tries to kill many processes (SIGKILL)
Sample has stripped symbol table
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
Executes the "rm" command used to delete files or directories
Sample listens on a socket
Sample tries to kill a process (SIGKILL)

Classification

AV Detection:

barindex
Multi AV Scanner detection for submitted file
Source: MPnFvIsvJp Virustotal: Detection: 50% Perma Link
Source: MPnFvIsvJp ReversingLabs: Detection: 58%

Networking:

barindex
Snort IDS alert for network traffic (e.g. based on Emerging Threat rules)
Source: Traffic Snort IDS: 716 INFO TELNET access 66.118.196.129:23 -> 192.168.2.23:36798
Source: Traffic Snort IDS: 492 INFO TELNET login failed 1.70.80.93:23 -> 192.168.2.23:60370
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 179.56.172.132:23 -> 192.168.2.23:49592
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 179.56.172.132:23 -> 192.168.2.23:49592
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 121.150.34.138:23 -> 192.168.2.23:52212
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 121.150.34.138:23 -> 192.168.2.23:52212
Source: Traffic Snort IDS: 716 INFO TELNET access 66.118.196.129:23 -> 192.168.2.23:36930
Source: Traffic Snort IDS: 716 INFO TELNET access 220.189.69.158:23 -> 192.168.2.23:40952
Source: Traffic Snort IDS: 716 INFO TELNET access 220.189.69.158:23 -> 192.168.2.23:41016
Source: Traffic Snort IDS: 716 INFO TELNET access 220.189.69.158:23 -> 192.168.2.23:41030
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 121.150.34.138:23 -> 192.168.2.23:52276
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 121.150.34.138:23 -> 192.168.2.23:52276
Source: Traffic Snort IDS: 716 INFO TELNET access 220.189.69.158:23 -> 192.168.2.23:41038
Source: Traffic Snort IDS: 716 INFO TELNET access 220.189.69.158:23 -> 192.168.2.23:41042
Source: Traffic Snort IDS: 716 INFO TELNET access 220.189.69.158:23 -> 192.168.2.23:41062
Source: Traffic Snort IDS: 716 INFO TELNET access 220.189.69.158:23 -> 192.168.2.23:41082
Source: Traffic Snort IDS: 716 INFO TELNET access 220.189.69.158:23 -> 192.168.2.23:41094
Source: Traffic Snort IDS: 716 INFO TELNET access 220.189.69.158:23 -> 192.168.2.23:41112
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 121.150.34.138:23 -> 192.168.2.23:52378
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 121.150.34.138:23 -> 192.168.2.23:52378
Source: Traffic Snort IDS: 716 INFO TELNET access 220.189.69.158:23 -> 192.168.2.23:41132
Source: Traffic Snort IDS: 2023448 ET TROJAN Possible Linux.Mirai Login Attempt (ubnt) 192.168.2.23:41132 -> 220.189.69.158:23
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 179.56.172.132:23 -> 192.168.2.23:49808
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 179.56.172.132:23 -> 192.168.2.23:49808
Source: Traffic Snort IDS: 716 INFO TELNET access 211.115.228.149:23 -> 192.168.2.23:50968
Source: Traffic Snort IDS: 716 INFO TELNET access 66.118.196.129:23 -> 192.168.2.23:37140
Source: Traffic Snort IDS: 716 INFO TELNET access 89.135.36.164:23 -> 192.168.2.23:55640
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 121.150.34.138:23 -> 192.168.2.23:52440
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 121.150.34.138:23 -> 192.168.2.23:52440
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 89.135.36.164:23 -> 192.168.2.23:55640
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 89.135.36.164:23 -> 192.168.2.23:55640
Source: Traffic Snort IDS: 492 INFO TELNET login failed 113.26.230.147:23 -> 192.168.2.23:39150
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 70.35.225.138:23 -> 192.168.2.23:57216
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 70.35.225.138:23 -> 192.168.2.23:57216
Source: Traffic Snort IDS: 716 INFO TELNET access 89.135.36.164:23 -> 192.168.2.23:55702
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 121.150.34.138:23 -> 192.168.2.23:52512
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 121.150.34.138:23 -> 192.168.2.23:52512
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 89.135.36.164:23 -> 192.168.2.23:55702
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 89.135.36.164:23 -> 192.168.2.23:55702
Source: Traffic Snort IDS: 716 INFO TELNET access 89.135.36.164:23 -> 192.168.2.23:55736
Source: Traffic Snort IDS: 716 INFO TELNET access 211.115.228.149:23 -> 192.168.2.23:51104
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 89.135.36.164:23 -> 192.168.2.23:55736
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 89.135.36.164:23 -> 192.168.2.23:55736
Source: Traffic Snort IDS: 716 INFO TELNET access 66.118.196.129:23 -> 192.168.2.23:37274
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 121.150.34.138:23 -> 192.168.2.23:52560
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 121.150.34.138:23 -> 192.168.2.23:52560
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 179.56.172.132:23 -> 192.168.2.23:49962
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 179.56.172.132:23 -> 192.168.2.23:49962
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 216.123.69.13:23 -> 192.168.2.23:39930
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 216.123.69.13:23 -> 192.168.2.23:39930
Source: Traffic Snort IDS: 716 INFO TELNET access 89.135.36.164:23 -> 192.168.2.23:55782
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 89.135.36.164:23 -> 192.168.2.23:55782
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 89.135.36.164:23 -> 192.168.2.23:55782
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 121.150.34.138:23 -> 192.168.2.23:52616
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 121.150.34.138:23 -> 192.168.2.23:52616
Uses known network protocols on non-standard ports
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37764
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37768
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37770
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37772
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37774
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37776
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37780
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37782
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37794
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37796
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37784
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37798
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37804
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37806
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37808
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39468
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37816
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39474
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37814
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39476
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37822
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39480
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39486
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37828
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39488
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37834
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39492
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39496
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39498
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39502
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 54454
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 54458
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 54468
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 54470
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 54476
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 54478
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 54488
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 54494
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 54496
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 54500
Tries to connect to HTTP servers, but all servers are down (expired dropper behavior)
Source: global traffic TCP traffic: 192.168.2.23:43928 -> 91.189.91.42:443
Source: global traffic TCP traffic: 192.168.2.23:42836 -> 91.189.91.43:443
Source: global traffic TCP traffic: 192.168.2.23:42516 -> 109.202.202.202:80
Detected TCP or UDP traffic on non-standard ports
Source: global traffic TCP traffic: 192.168.2.23:44200 -> 176.126.175.188:1312
Sample listens on a socket
Source: /tmp/MPnFvIsvJp (PID: 5270) Socket: 0.0.0.0::22 Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5270) Socket: 0.0.0.0::23 Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5270) Socket: 0.0.0.0::53413 Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5270) Socket: 0.0.0.0::80 Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5270) Socket: 0.0.0.0::52869 Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5270) Socket: 0.0.0.0::37215 Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) Socket: 0.0.0.0::0 Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) Socket: 0.0.0.0::23 Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) Socket: 0.0.0.0::53413 Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) Socket: 0.0.0.0::80 Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) Socket: 0.0.0.0::52869 Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) Socket: 0.0.0.0::37215 Jump to behavior
Source: /usr/sbin/sshd (PID: 5308) 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: 176.126.175.188
Source: unknown TCP traffic detected without corresponding DNS query: 141.236.143.83
Source: unknown TCP traffic detected without corresponding DNS query: 92.42.25.252
Source: unknown TCP traffic detected without corresponding DNS query: 254.81.82.214
Source: unknown TCP traffic detected without corresponding DNS query: 114.119.111.231
Source: unknown TCP traffic detected without corresponding DNS query: 80.122.42.242
Source: unknown TCP traffic detected without corresponding DNS query: 101.82.42.191
Source: unknown TCP traffic detected without corresponding DNS query: 2.85.105.98
Source: unknown TCP traffic detected without corresponding DNS query: 53.225.130.44
Source: unknown TCP traffic detected without corresponding DNS query: 35.216.80.163
Source: unknown TCP traffic detected without corresponding DNS query: 250.204.96.3
Source: unknown TCP traffic detected without corresponding DNS query: 178.155.158.132
Source: unknown TCP traffic detected without corresponding DNS query: 37.226.184.57
Source: unknown TCP traffic detected without corresponding DNS query: 4.101.100.125
Source: unknown TCP traffic detected without corresponding DNS query: 59.2.58.91
Source: unknown TCP traffic detected without corresponding DNS query: 111.68.240.159
Source: unknown TCP traffic detected without corresponding DNS query: 145.127.203.168
Source: unknown TCP traffic detected without corresponding DNS query: 93.111.178.142
Source: unknown TCP traffic detected without corresponding DNS query: 109.227.12.105
Source: unknown TCP traffic detected without corresponding DNS query: 166.155.133.136
Source: unknown TCP traffic detected without corresponding DNS query: 45.253.45.196
Source: unknown TCP traffic detected without corresponding DNS query: 114.127.150.38
Source: unknown TCP traffic detected without corresponding DNS query: 142.134.60.96
Source: unknown TCP traffic detected without corresponding DNS query: 90.183.57.44
Source: unknown TCP traffic detected without corresponding DNS query: 254.63.233.189
Source: unknown TCP traffic detected without corresponding DNS query: 125.45.23.97
Source: unknown TCP traffic detected without corresponding DNS query: 252.237.198.223
Source: unknown TCP traffic detected without corresponding DNS query: 61.95.222.35
Source: unknown TCP traffic detected without corresponding DNS query: 120.14.42.228
Source: unknown TCP traffic detected without corresponding DNS query: 84.58.140.225
Source: unknown TCP traffic detected without corresponding DNS query: 81.108.193.140
Source: unknown TCP traffic detected without corresponding DNS query: 9.127.16.250
Source: unknown TCP traffic detected without corresponding DNS query: 246.101.183.47
Source: unknown TCP traffic detected without corresponding DNS query: 165.115.26.237
Source: unknown TCP traffic detected without corresponding DNS query: 152.146.155.12
Source: unknown TCP traffic detected without corresponding DNS query: 145.117.154.94
Source: unknown TCP traffic detected without corresponding DNS query: 48.5.50.187
Source: unknown TCP traffic detected without corresponding DNS query: 243.134.35.78
Source: unknown TCP traffic detected without corresponding DNS query: 27.154.165.37
Source: unknown TCP traffic detected without corresponding DNS query: 23.226.106.55
Source: unknown TCP traffic detected without corresponding DNS query: 166.27.220.118
Source: unknown TCP traffic detected without corresponding DNS query: 182.169.48.199
Source: unknown TCP traffic detected without corresponding DNS query: 207.126.60.86
Source: unknown TCP traffic detected without corresponding DNS query: 84.168.179.71
Source: unknown TCP traffic detected without corresponding DNS query: 53.149.80.83
Source: unknown TCP traffic detected without corresponding DNS query: 20.182.141.7
Source: unknown TCP traffic detected without corresponding DNS query: 87.233.107.0
Source: unknown TCP traffic detected without corresponding DNS query: 95.130.139.211
Source: unknown TCP traffic detected without corresponding DNS query: 161.154.243.114
Source: unknown TCP traffic detected without corresponding DNS query: 74.133.199.57
Source: motd-news.18.dr String found in binary or memory: https://ubuntu.com/blog/microk8s-memory-optimisation

System Summary:

barindex
Sample tries to kill many processes (SIGKILL)
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 936, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 5270, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 720, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 759, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 788, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 800, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 847, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 884, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 1334, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 1335, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 1860, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 1872, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 2096, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 2097, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 2102, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 2180, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 2191, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 2208, result: successful Jump to behavior
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/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 936, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 5270, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 720, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 759, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 788, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 800, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 847, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 884, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 1334, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 1335, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 1860, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 1872, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 2096, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 2097, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 2102, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 2180, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 2191, result: successful Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) SIGKILL sent: pid: 2208, result: successful Jump to behavior
Source: classification engine Classification label: mal72.spre.troj.lin@0/3@0/0
Source: MPnFvIsvJp Joe Sandbox Cloud Basic: Detection: clean Score: 0 Perma Link

Persistence and Installation Behavior:

barindex
Enumerates processes within the "proc" file system
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/2033/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/2033/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1582/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1582/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/2275/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1612/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1612/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1579/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1579/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1699/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1699/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1335/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1335/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1698/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1698/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/2028/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/2028/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1334/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1334/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1576/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1576/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/2302/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/3236/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/2025/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/2025/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/2146/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/2146/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/910/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/912/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/912/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/912/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/759/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/759/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/759/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/517/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/2307/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/918/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/918/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/918/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1594/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1594/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/2285/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/2281/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/5270/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1349/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1349/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1623/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1623/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/761/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/761/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/761/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1622/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1622/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/884/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/884/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/884/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1983/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1983/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/2038/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/2038/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1586/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1586/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1465/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1465/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1344/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1344/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1860/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1860/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1463/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1463/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/2156/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/2156/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/800/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/800/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/800/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/801/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/801/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/801/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1629/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1629/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1627/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1627/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1900/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1900/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/491/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/491/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/491/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/2294/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/2050/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/2050/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1877/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1877/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/772/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/772/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/772/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1633/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1633/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1599/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1599/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1632/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1632/exe Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1477/fd Jump to behavior
Source: /tmp/MPnFvIsvJp (PID: 5276) File opened: /proc/1477/exe Jump to behavior
Executes the "rm" command used to delete files or directories
Source: /usr/bin/dash (PID: 5221) Rm executable: /usr/bin/rm -> rm -f /tmp/tmp.nd5wZIclrj /tmp/tmp.zShyQQ7qTu /tmp/tmp.3SdD1ZBLJc 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 -> 37764
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37768
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37770
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37772
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37774
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37776
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37780
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37782
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37794
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37796
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37784
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37798
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37804
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37806
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37808
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39468
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37816
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39474
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37814
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39476
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37822
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39480
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39486
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37828
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39488
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 37834
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39492
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39496
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39498
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 39502
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 54454
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 54458
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 54468
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 54470
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 54476
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 54478
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 54488
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 54494
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 54496
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 54500

Malware Analysis System Evasion:

barindex
Uses the "uname" system call to query kernel version information (possible evasion)
Source: /tmp/MPnFvIsvJp (PID: 5267) Queries kernel information via 'uname': Jump to behavior
Source: MPnFvIsvJp, 5267.1.000000000d0936a4.000000009ef99e4c.rw-.sdmp Binary or memory string: !/etc/qemu-binfmt/ppc11!hotpluggableq
Source: MPnFvIsvJp, 5270.1.000000000d0936a4.000000009ef99e4c.rw-.sdmp Binary or memory string: !/etc/qemu-binfmt/ppc1
Source: MPnFvIsvJp, 5267.1.000000000d0936a4.000000009ef99e4c.rw-.sdmp Binary or memory string: /etc/qemu-binfmt/ppc
Source: MPnFvIsvJp, 5267.1.00000000c3376e66.00000000dbbd983f.rw-.sdmp Binary or memory string: /usr/bin/qemu-ppc
Source: MPnFvIsvJp, 5267.1.00000000c3376e66.00000000dbbd983f.rw-.sdmp Binary or memory string: CJx86_64/usr/bin/qemu-ppc/tmp/MPnFvIsvJpSUDO_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/MPnFvIsvJp

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