IP Address: 168.138.164.132Previously Malicious
IP Address: 168.138.164.132Previously 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 |
Successful SSH Login Port 8080 Scan 5 Shell Commands Listening SSH System File Modification Download and Execute Superuser Operation Port 80 Scan Outgoing Connection Port 1234 Scan |
Associated Attack Servers |
bsnl.in escom.bg iforte.net.id mycingular.net nwgsm.ru 8.213.128.90 8.242.232.86 18.205.117.37 35.236.57.157 41.207.248.204 45.168.133.250 58.221.57.214 63.245.46.10 69.74.68.50 85.26.129.164 93.183.167.152 94.26.139.111 96.126.124.197 103.165.122.93 117.247.172.37 120.224.34.31 122.70.156.12 124.70.55.29 147.182.233.56 149.129.232.50 166.193.42.177 172.64.200.11 172.64.201.11 185.227.171.232 191.96.34.2 194.146.234.43 219.140.162.82 222.117.95.174 223.171.91.144 |
IP Address |
168.138.164.132 |
|
Domain |
- |
|
ISP |
Oracle Public Cloud |
|
Country |
United States |
|
WHOIS |
Created Date |
- |
Updated Date |
- |
|
Organization |
- |
First seen in Akamai Guardicore Segmentation |
2022-07-03 |
Last seen in Akamai Guardicore Segmentation |
2022-10-29 |
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 |
System file /etc/ifconfig was modified 4 times |
System File Modification |
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 |
System file /etc/apache2 was modified 4 times |
System File Modification |
The file /etc/ifconfig was downloaded and executed 2 times |
Download and Execute |
Process /etc/apache2 scanned port 1234 on 27 IP Addresses |
Port 1234 Scan Port 80 Scan Port 8080 Scan |
Process /etc/apache2 scanned port 80 on 27 IP Addresses |
Port 1234 Scan Port 80 Scan Port 8080 Scan |
Process /etc/apache2 scanned port 8080 on 27 IP Addresses |
Port 1234 Scan Port 80 Scan Port 8080 Scan |
Process /etc/apache2 scanned port 1234 on 32 IP Addresses |
Port 1234 Scan Port 80 Scan Port 8080 Scan |
Process /etc/apache2 scanned port 1234 on 29 IP Addresses |
Port 1234 Scan Port 80 Scan Port 8080 Scan |
Process /bin/bash scanned port 1234 on 27 IP Addresses 2 times |
Port 1234 Scan |
Process /etc/apache2 generated outgoing network traffic to: 1.13.133.100:80, 1.13.133.100:8080, 101.42.90.177:1234, 103.152.118.20:1234, 104.21.25.86:443, 116.90.173.18:80, 116.90.173.18:8080, 117.80.212.33:1234, 118.41.204.72:1234, 12.232.41.98:80, 12.232.41.98:8080, 120.224.34.31:1234, 120.68.55.160:80, 120.68.55.160:8080, 122.171.149.78:80, 122.171.149.78:8080, 123.132.238.210:1234, 124.155.247.12:80, 124.155.247.12:8080, 124.200.94.14:80, 124.200.94.14:8080, 124.223.14.100:1234, 132.63.136.222:80, 132.63.136.222:8080, 134.50.154.98:80, 134.50.154.98:8080, 138.159.59.115:80, 138.159.59.115:8080, 140.18.60.23:80, 140.18.60.23:8080, 141.198.116.107:80, 141.198.116.107:8080, 142.251.32.4:443, 149.97.53.101:80, 150.107.95.20:1234, 161.35.79.199:1234, 161.81.90.201:80, 161.81.90.201:8080, 163.95.168.155:80, 163.95.168.155:8080, 166.227.252.248:80, 166.227.252.248:8080, 172.67.133.228:443, 173.18.35.41:1234, 175.9.13.212:80, 175.9.13.212:8080, 176.135.250.29:80, 176.135.250.29:8080, 183.179.26.242:80, 183.179.26.242:8080, 19.248.82.164:80, 190.238.218.8:80, 190.238.218.8:8080, 20.141.185.205:1234, 201.79.15.56:80, 201.79.15.56:8080, 202.61.203.229:1234, 209.216.177.158:1234, 209.216.177.238:1234, 218.146.15.97:1234, 22.156.109.158:80, 22.156.109.158:8080, 222.103.98.58:1234, 222.121.63.87:1234, 223.171.91.149:1234, 223.99.166.104:1234, 240.217.104.87:80, 240.217.104.87:8080, 244.240.78.54:80, 244.240.78.54:8080, 31.19.237.170:1234, 34.62.253.83:80, 34.62.253.83:8080, 55.33.153.129:80, 55.33.153.129:8080, 58.229.125.66:1234, 65.24.18.134:80, 65.24.18.134:8080, 69.2.46.210:80, 69.2.46.210:8080, 82.149.112.170:1234, 84.204.148.99:1234, 85.155.196.169:80, 85.155.196.169:8080, 92.194.249.67:80, 92.194.249.67:8080, 93.176.229.145:1234, 94.153.165.43:1234 and 97.6.65.214:80 |
Outgoing Connection |
Process /etc/apache2 started listening on ports: 1234, 8088 and 8182 |
Listening |
The file /etc/apache2 was downloaded and executed 102 times |
Download and Execute |
Process /etc/apache2 scanned port 80 on 32 IP Addresses |
Port 1234 Scan Port 80 Scan Port 8080 Scan |
Process /etc/apache2 scanned port 8080 on 32 IP Addresses |
Port 1234 Scan Port 80 Scan Port 8080 Scan |
Process /etc/apache2 scanned port 80 on 29 IP Addresses |
Port 1234 Scan Port 80 Scan Port 8080 Scan |
Process /etc/apache2 scanned port 8080 on 29 IP Addresses |
Port 1234 Scan Port 80 Scan Port 8080 Scan |
Process /usr/local/mysql/bin/mysqld started listening on ports: 3306 2 times |
Listening |
Process /usr/local/apache2/bin/httpd started listening on ports: 80 2 times |
Listening |
Connection was closed due to user inactivity |
|