Linux Analysis Report Rpl2Twyrts

Overview

General Information

Sample Name: Rpl2Twyrts
Analysis ID: 507421
MD5: 4635e3761f10a21d01fec0df9fa36e2f
SHA1: a33d4b91fc25603b0ed98b17381f6a6e017f6c32
SHA256: 91ccea41a26fce7feab89f9b17c889b9f7c37f29b5b5a9390a7d3f2990f43cfa
Tags: 32elfmipsmirai
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
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
Sample listens on a socket
Sample tries to kill a process (SIGKILL)

Classification

AV Detection:

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

Networking:

barindex
Snort IDS alert for network traffic (e.g. based on Emerging Threat rules)
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 85.105.51.241:23 -> 192.168.2.23:33338
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 85.105.51.241:23 -> 192.168.2.23:33338
Source: Traffic Snort IDS: 492 INFO TELNET login failed 115.218.14.34:23 -> 192.168.2.23:41338
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 121.137.0.70:23 -> 192.168.2.23:34618
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 121.137.0.70:23 -> 192.168.2.23:34618
Source: Traffic Snort IDS: 492 INFO TELNET login failed 115.218.14.34:23 -> 192.168.2.23:41376
Source: Traffic Snort IDS: 404 ICMP Destination Unreachable Protocol Unreachable 92.34.49.134: -> 192.168.2.23:
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 121.137.0.70:23 -> 192.168.2.23:34686
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 121.137.0.70:23 -> 192.168.2.23:34686
Source: Traffic Snort IDS: 716 INFO TELNET access 178.207.232.219:23 -> 192.168.2.23:43666
Source: Traffic Snort IDS: 716 INFO TELNET access 178.207.232.219:23 -> 192.168.2.23:43694
Source: Traffic Snort IDS: 716 INFO TELNET access 178.207.232.219:23 -> 192.168.2.23:43696
Source: Traffic Snort IDS: 716 INFO TELNET access 178.207.232.219:23 -> 192.168.2.23:43730
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 121.137.0.70:23 -> 192.168.2.23:34742
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 121.137.0.70:23 -> 192.168.2.23:34742
Source: Traffic Snort IDS: 716 INFO TELNET access 178.207.232.219:23 -> 192.168.2.23:43736
Source: Traffic Snort IDS: 716 INFO TELNET access 178.207.232.219:23 -> 192.168.2.23:43746
Source: Traffic Snort IDS: 716 INFO TELNET access 178.207.232.219:23 -> 192.168.2.23:43752
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 85.105.51.241:23 -> 192.168.2.23:33544
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 85.105.51.241:23 -> 192.168.2.23:33544
Source: Traffic Snort IDS: 716 INFO TELNET access 178.207.232.219:23 -> 192.168.2.23:43762
Source: Traffic Snort IDS: 492 INFO TELNET login failed 117.141.39.60:23 -> 192.168.2.23:34908
Source: Traffic Snort IDS: 716 INFO TELNET access 178.207.232.219:23 -> 192.168.2.23:43772
Source: Traffic Snort IDS: 716 INFO TELNET access 178.207.232.219:23 -> 192.168.2.23:43782
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 121.137.0.70:23 -> 192.168.2.23:34832
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 121.137.0.70:23 -> 192.168.2.23:34832
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 219.85.186.111:23 -> 192.168.2.23:41952
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 219.85.186.111:23 -> 192.168.2.23:41952
Source: Traffic Snort IDS: 492 INFO TELNET login failed 117.141.39.60:23 -> 192.168.2.23:34954
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 121.137.0.70:23 -> 192.168.2.23:34874
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 121.137.0.70:23 -> 192.168.2.23:34874
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 219.85.186.111:23 -> 192.168.2.23:42000
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 219.85.186.111:23 -> 192.168.2.23:42000
Source: Traffic Snort IDS: 492 INFO TELNET login failed 117.141.39.60:23 -> 192.168.2.23:35004
Source: Traffic Snort IDS: 492 INFO TELNET login failed 117.141.39.60:23 -> 192.168.2.23:35022
Source: Traffic Snort IDS: 716 INFO TELNET access 61.155.111.226:23 -> 192.168.2.23:43856
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 121.137.0.70:23 -> 192.168.2.23:34940
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 121.137.0.70:23 -> 192.168.2.23:34940
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 85.105.51.241:23 -> 192.168.2.23:33688
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 85.105.51.241:23 -> 192.168.2.23:33688
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 219.85.186.111:23 -> 192.168.2.23:42056
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 219.85.186.111:23 -> 192.168.2.23:42056
Source: Traffic Snort IDS: 492 INFO TELNET login failed 61.155.111.226:23 -> 192.168.2.23:43856
Source: Traffic Snort IDS: 492 INFO TELNET login failed 117.141.39.60:23 -> 192.168.2.23:35044
Source: Traffic Snort IDS: 716 INFO TELNET access 61.155.111.226:23 -> 192.168.2.23:43872
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 79.134.5.70:23 -> 192.168.2.23:51930
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 79.134.5.70:23 -> 192.168.2.23:51930
Source: Traffic Snort IDS: 716 INFO TELNET access 111.118.117.166:23 -> 192.168.2.23:59234
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 121.137.0.70:23 -> 192.168.2.23:34968
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 121.137.0.70:23 -> 192.168.2.23:34968
Source: Traffic Snort IDS: 492 INFO TELNET login failed 117.141.39.60:23 -> 192.168.2.23:35074
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 111.118.117.166:23 -> 192.168.2.23:59234
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 111.118.117.166:23 -> 192.168.2.23:59234
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 219.85.186.111:23 -> 192.168.2.23:42094
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 219.85.186.111:23 -> 192.168.2.23:42094
Source: Traffic Snort IDS: 492 INFO TELNET login failed 61.155.111.226:23 -> 192.168.2.23:43872
Source: Traffic Snort IDS: 716 INFO TELNET access 61.155.111.226:23 -> 192.168.2.23:43920
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 79.134.5.70:23 -> 192.168.2.23:51964
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 79.134.5.70:23 -> 192.168.2.23:51964
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 121.137.0.70:23 -> 192.168.2.23:35000
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 121.137.0.70:23 -> 192.168.2.23:35000
Source: Traffic Snort IDS: 716 INFO TELNET access 111.118.117.166:23 -> 192.168.2.23:59358
Source: Traffic Snort IDS: 492 INFO TELNET login failed 117.141.39.60:23 -> 192.168.2.23:35152
Source: Traffic Snort IDS: 492 INFO TELNET login failed 61.155.111.226:23 -> 192.168.2.23:43920
Source: Traffic Snort IDS: 716 INFO TELNET access 121.190.249.90:23 -> 192.168.2.23:53378
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 219.85.186.111:23 -> 192.168.2.23:42210
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 219.85.186.111:23 -> 192.168.2.23:42210
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 111.118.117.166:23 -> 192.168.2.23:59358
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 111.118.117.166:23 -> 192.168.2.23:59358
Source: Traffic Snort IDS: 492 INFO TELNET login failed 121.190.249.90:23 -> 192.168.2.23:53378
Source: Traffic Snort IDS: 716 INFO TELNET access 61.155.111.226:23 -> 192.168.2.23:44042
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 79.134.5.70:23 -> 192.168.2.23:52076
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 79.134.5.70:23 -> 192.168.2.23:52076
Source: Traffic Snort IDS: 716 INFO TELNET access 121.190.249.90:23 -> 192.168.2.23:53420
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 121.137.0.70:23 -> 192.168.2.23:35136
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 121.137.0.70:23 -> 192.168.2.23:35136
Source: Traffic Snort IDS: 492 INFO TELNET login failed 121.190.249.90:23 -> 192.168.2.23:53420
Source: Traffic Snort IDS: 492 INFO TELNET login failed 61.155.111.226:23 -> 192.168.2.23:44042
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 85.105.51.241:23 -> 192.168.2.23:33888
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 85.105.51.241:23 -> 192.168.2.23:33888
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 181.114.224.143:23 -> 192.168.2.23:60320
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 181.114.224.143:23 -> 192.168.2.23:60320
Source: Traffic Snort IDS: 492 INFO TELNET login failed 117.141.39.60:23 -> 192.168.2.23:35240
Source: Traffic Snort IDS: 716 INFO TELNET access 121.190.249.90:23 -> 192.168.2.23:53434
Source: Traffic Snort IDS: 716 INFO TELNET access 111.118.117.166:23 -> 192.168.2.23:59424
Source: Traffic Snort IDS: 492 INFO TELNET login failed 121.190.249.90:23 -> 192.168.2.23:53434
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 219.85.186.111:23 -> 192.168.2.23:42274
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 219.85.186.111:23 -> 192.168.2.23:42274
Source: Traffic Snort IDS: 716 INFO TELNET access 121.190.249.90:23 -> 192.168.2.23:53446
Source: Traffic Snort IDS: 1251 INFO TELNET Bad Login 79.134.5.70:23 -> 192.168.2.23:52138
Source: Traffic Snort IDS: 718 INFO TELNET login incorrect 79.134.5.70:23 -> 192.168.2.23:52138
Uses known network protocols on non-standard ports
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 47728
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 47732
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 47736
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 47744
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 47750
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 47754
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 47760
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 47764
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 47770
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 47778
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/Rpl2Twyrts (PID: 5248) Socket: 0.0.0.0::0 Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5248) Socket: 0.0.0.0::23 Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5248) Socket: 0.0.0.0::53413 Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5248) Socket: 0.0.0.0::80 Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5248) Socket: 0.0.0.0::52869 Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5248) Socket: 0.0.0.0::37215 Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) Socket: 0.0.0.0::0 Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) Socket: 0.0.0.0::23 Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) Socket: 0.0.0.0::53413 Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) Socket: 0.0.0.0::80 Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) Socket: 0.0.0.0::52869 Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) Socket: 0.0.0.0::37215 Jump to behavior
Source: /usr/sbin/sshd (PID: 5290) Socket: 0.0.0.0::22 Jump to behavior
Source: /usr/sbin/sshd (PID: 5290) 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: 99.22.166.11
Source: unknown TCP traffic detected without corresponding DNS query: 63.165.84.11
Source: unknown TCP traffic detected without corresponding DNS query: 223.195.0.116
Source: unknown TCP traffic detected without corresponding DNS query: 35.118.13.8
Source: unknown TCP traffic detected without corresponding DNS query: 149.182.9.19
Source: unknown TCP traffic detected without corresponding DNS query: 24.8.223.69
Source: unknown TCP traffic detected without corresponding DNS query: 182.145.206.142
Source: unknown TCP traffic detected without corresponding DNS query: 9.67.65.67
Source: unknown TCP traffic detected without corresponding DNS query: 240.16.115.86
Source: unknown TCP traffic detected without corresponding DNS query: 12.43.212.21
Source: unknown TCP traffic detected without corresponding DNS query: 108.55.127.139
Source: unknown TCP traffic detected without corresponding DNS query: 201.247.47.135
Source: unknown TCP traffic detected without corresponding DNS query: 9.169.231.174
Source: unknown TCP traffic detected without corresponding DNS query: 223.11.182.21
Source: unknown TCP traffic detected without corresponding DNS query: 175.215.68.114
Source: unknown TCP traffic detected without corresponding DNS query: 76.131.185.195
Source: unknown TCP traffic detected without corresponding DNS query: 204.186.55.14
Source: unknown TCP traffic detected without corresponding DNS query: 104.42.93.127
Source: unknown TCP traffic detected without corresponding DNS query: 91.185.36.65
Source: unknown TCP traffic detected without corresponding DNS query: 73.185.144.44
Source: unknown TCP traffic detected without corresponding DNS query: 46.44.202.14
Source: unknown TCP traffic detected without corresponding DNS query: 146.90.157.91
Source: unknown TCP traffic detected without corresponding DNS query: 207.19.164.238
Source: unknown TCP traffic detected without corresponding DNS query: 2.5.107.224
Source: unknown TCP traffic detected without corresponding DNS query: 65.109.217.140
Source: unknown TCP traffic detected without corresponding DNS query: 193.187.14.64
Source: unknown TCP traffic detected without corresponding DNS query: 72.239.120.156
Source: unknown TCP traffic detected without corresponding DNS query: 164.30.143.68
Source: unknown TCP traffic detected without corresponding DNS query: 155.206.205.161
Source: unknown TCP traffic detected without corresponding DNS query: 19.156.56.61
Source: unknown TCP traffic detected without corresponding DNS query: 51.5.236.88
Source: unknown TCP traffic detected without corresponding DNS query: 206.22.155.20
Source: unknown TCP traffic detected without corresponding DNS query: 170.182.30.23
Source: unknown TCP traffic detected without corresponding DNS query: 66.95.128.129
Source: unknown TCP traffic detected without corresponding DNS query: 67.85.248.138
Source: unknown TCP traffic detected without corresponding DNS query: 209.218.75.6
Source: unknown TCP traffic detected without corresponding DNS query: 104.187.122.215
Source: unknown TCP traffic detected without corresponding DNS query: 218.248.90.54
Source: unknown TCP traffic detected without corresponding DNS query: 218.93.181.123
Source: unknown TCP traffic detected without corresponding DNS query: 76.42.25.135
Source: unknown TCP traffic detected without corresponding DNS query: 211.104.2.117
Source: unknown TCP traffic detected without corresponding DNS query: 203.176.253.233
Source: unknown TCP traffic detected without corresponding DNS query: 149.176.173.143
Source: unknown TCP traffic detected without corresponding DNS query: 170.185.42.8
Source: unknown TCP traffic detected without corresponding DNS query: 187.248.51.123
Source: unknown TCP traffic detected without corresponding DNS query: 125.220.33.131
Source: unknown TCP traffic detected without corresponding DNS query: 147.187.68.56
Source: unknown TCP traffic detected without corresponding DNS query: 211.170.82.218
Source: unknown TCP traffic detected without corresponding DNS query: 117.189.183.121

System Summary:

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

Persistence and Installation Behavior:

barindex
Enumerates processes within the "proc" file system
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/5268/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2033/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2033/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2033/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1582/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1582/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1582/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2275/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2275/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1612/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1612/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1612/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1579/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1579/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1579/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1699/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1699/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1699/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1335/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1335/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1335/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1698/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1698/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1698/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2028/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2028/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2028/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1334/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1334/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1334/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1576/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1576/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1576/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2302/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2302/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/3236/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/3236/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2025/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2025/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2025/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2146/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2146/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2146/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/910/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/912/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/912/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/912/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/759/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/759/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/759/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/517/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2307/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2307/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/918/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/918/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/918/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/5272/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/5273/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/5274/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/5275/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/5276/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/5277/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/5278/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/5279/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1594/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1594/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1594/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2285/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2285/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2281/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2281/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/5270/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/5271/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1349/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1349/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1349/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1623/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1623/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1623/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/761/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/761/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/761/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1622/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1622/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1622/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/884/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/884/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/884/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1983/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1983/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1983/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2038/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2038/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/2038/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1586/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1586/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1586/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1465/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1465/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1465/exe Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1344/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1344/fd Jump to behavior
Source: /tmp/Rpl2Twyrts (PID: 5254) File opened: /proc/1344/exe 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 -> 47728
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 47732
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 47736
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 47744
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 47750
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 47754
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 47760
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 47764
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 47770
Source: unknown Network traffic detected: HTTP traffic on port 23 -> 47778

Malware Analysis System Evasion:

barindex
Uses the "uname" system call to query kernel version information (possible evasion)
Source: /tmp/Rpl2Twyrts (PID: 5246) Queries kernel information via 'uname': Jump to behavior
Source: Rpl2Twyrts, 5246.1.00000000e46a4f04.0000000018f5b09c.rw-.sdmp Binary or memory string: /etc/qemu-binfmt/mipsel
Source: Rpl2Twyrts, 5246.1.00000000e46a4f04.0000000018f5b09c.rw-.sdmp Binary or memory string: V!/etc/qemu-binfmt/mipsel
Source: Rpl2Twyrts, 5246.1.000000006915b6a7.0000000099a0e5b4.rw-.sdmp Binary or memory string: x86_64/usr/bin/qemu-mipsel/tmp/Rpl2TwyrtsSUDO_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/Rpl2Twyrts
Source: Rpl2Twyrts, 5246.1.000000006915b6a7.0000000099a0e5b4.rw-.sdmp Binary or memory string: /usr/bin/qemu-mipsel

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