IP Address: 82.173.4.191Previously Malicious
IP Address: 82.173.4.191Previously Malicious
This IP address attempted an attack on a machine in our threat sensors network
Role |
Attacker, Connect-Back, Scanner |
Services Targeted |
SCP SSH |
Tags |
Port 22 Scan Access Suspicious Domain Port 8080 Scan 2 Shell Commands Download File SSH Superuser Operation Port 80 Scan Successful SSH Login Download and Execute SCP Outgoing Connection Listening Download and Allow Execution |
Associated Attack Servers |
146.in-addr.arpa ae2am1.shop aeza.network airtel.in cable.net.co ertelecom.ru fetnet.net gvt.net.br innovatelekom.com ip-51-222-212.net jiketoys.com.cn Majordomo.ru metrotel.net.co ntust.edu.tw prserv.net rhythmguitarplayer.com sileman.net.pl versatel.nl 1.15.13.216 2.87.72.160 9.28.6.32 9.218.20.229 13.3.120.195 13.124.116.69 13.235.111.215 16.40.237.73 16.194.115.17 19.136.196.8 24.32.65.138 25.25.118.78 26.24.136.174 27.195.153.110 31.19.237.170 32.4.166.28 32.106.97.38 35.53.189.115 35.76.8.5 36.75.66.175 37.126.197.221 38.26.232.21 38.114.245.74 40.112.221.159 41.228.22.107 42.193.137.44 45.107.170.183 45.142.122.215 45.153.186.205 46.13.164.29 |
IP Address |
82.173.4.191 |
|
Domain |
- |
|
ISP |
Tele2 Nederland |
|
Country |
Netherlands |
|
WHOIS |
Created Date |
- |
Updated Date |
- |
|
Organization |
- |
First seen in Akamai Guardicore Segmentation |
2022-03-08 |
Last seen in Akamai Guardicore Segmentation |
2022-04-08 |
What is Akamai Guardicore SegmentationAkamai Guardicore Segmentation is a data center and cloud security solution that protects the organization's core assets, using flexible, quickly deployed and easy to understand micro-segmentation controls. Akamai Guardicore Segmentation generates in-context security incidents, with details on attacker tools and techniques, that help IR teams prioritize incident investigation and reduce dwell time. Learn More
A user logged in using SSH with the following credentials: root / ****** - Authentication policy: White List |
Successful SSH Login |
A user logged in using SSH with the following credentials: root / ****** - Authentication policy: Correct Password |
Successful SSH Login |
A possibly malicious Superuser Operation was detected 2 times |
Superuser Operation |
The file /tmp/ifconfig was downloaded and executed 5 times |
Download and Execute |
Process /tmp/apache2 scanned port 22 on 12 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /tmp/apache2 scanned port 80 on 12 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /tmp/apache2 scanned port 8080 on 12 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /tmp/apache2 scanned port 22 on 32 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /tmp/apache2 scanned port 22 on 32 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
The file /tmp/apache2 was downloaded and executed 21 times |
Download and Execute |
Process /tmp/apache2 generated outgoing network traffic to: 103.59.14.125:80, 103.59.14.125:8080, 103.96.41.245:1234, 104.21.25.86:443, 107.244.124.158:80, 107.244.124.158:8080, 11.244.236.238:80, 11.244.236.238:8080, 113.78.105.203:80, 113.78.105.203:8080, 116.31.107.208:1234, 120.136.134.153:1234, 123.115.229.78:2222, 123.70.203.36:2222, 129.101.71.92:80, 129.101.71.92:8080, 132.17.224.108:22, 137.202.196.80:80, 137.202.196.80:8080, 139.28.231.174:1234, 143.33.214.164:80, 143.33.214.164:8080, 146.199.151.245:80, 146.199.151.245:8080, 157.217.99.150:22, 159.133.245.95:80, 159.133.245.95:8080, 16.112.6.159:80, 16.112.6.159:8080, 16.51.97.85:80, 16.51.97.85:8080, 172.58.58.161:22, 172.67.133.228:443, 173.21.188.113:22, 176.27.223.143:80, 176.27.223.143:8080, 176.70.133.155:22, 177.142.191.156:80, 177.142.191.156:8080, 191.249.236.85:1234, 195.108.59.253:22, 198.114.168.250:2222, 199.102.16.47:22, 202.182.136.160:80, 202.182.136.160:8080, 208.167.253.43:80, 208.167.253.43:8080, 21.16.147.130:80, 21.16.147.130:8080, 210.235.128.209:80, 210.235.128.209:8080, 212.204.182.60:22, 23.213.30.161:22, 241.97.94.137:80, 241.97.94.137:8080, 246.58.204.79:80, 246.58.204.79:8080, 250.51.101.43:80, 250.51.101.43:8080, 3.162.250.4:80, 3.162.250.4:8080, 30.232.87.199:80, 30.232.87.199:8080, 35.252.207.46:80, 35.252.207.46:8080, 35.29.223.245:80, 35.29.223.245:8080, 41.34.43.117:80, 41.34.43.117:8080, 49.166.59.202:1234, 51.75.146.174:443, 53.124.48.87:80, 53.124.48.87:8080, 53.221.160.123:22, 55.114.251.76:80, 55.114.251.76:8080, 56.247.210.166:80, 56.247.210.166:8080, 72.140.217.4:80, 72.140.217.4:8080, 73.97.15.126:80, 73.97.15.126:8080, 8.203.70.77:80, 8.203.70.77:8080, 80.198.32.98:22, 82.173.4.191:1234, 83.174.115.193:2222, 90.225.24.136:80 and 90.225.24.136:8080 |
Outgoing Connection |
Process /tmp/apache2 started listening on ports: 1234, 8086 and 8183 |
Listening |
Process /tmp/apache2 attempted to access suspicious domains: dsnet, gvt.net.br, innovatelekom.com, limerick.co.in and versatel.nl |
Access Suspicious Domain Outgoing Connection |
Process /tmp/apache2 scanned port 80 on 32 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /tmp/apache2 scanned port 8080 on 32 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /tmp/apache2 scanned port 80 on 32 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /tmp/apache2 scanned port 8080 on 32 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Connection was closed due to user inactivity |
|