Cyber Threat Intelligence

Discover malicious IPs and domains with Akamai Guardicore Segmentation

IP Address: 106.75.72.63Previously Malicious

IP Address: 106.75.72.63Previously Malicious

This IP address attempted an attack on a machine in our threat sensors network

Threat Information

Role

Attacker, Connect-Back, Scanner

Services Targeted

SCP SSH

Tags

Port 22 Scan Port 8080 Scan 3 Shell Commands SSH Superuser Operation Port 80 Scan Successful SSH Login Outgoing Connection Access Suspicious Domain Listening

Associated Attack Servers

attdns.com az1am5.shop btcentralplus.com bt.net ccsnet.ne.jp centertel.pl cloudfront.net cultimording.org.uk enta.net innovatelekom.com mycingular.net nextgentel.com omantel.net.om onvol.net pocketinet.com saxion.nl scw.cloud serv-net.pl sileman.net.pl sparkbb.co.nz spd-mgts.ru swisscom.ch telecel.com.py telia.com timbrasil.com.br vsb.cz

1.13.18.11 1.116.42.111 2.144.99.105 4.122.195.88 5.185.58.136 5.220.223.40 6.152.105.197 8.33.112.133 8.154.125.74 9.204.49.91 10.33.0.9 11.19.14.20 13.33.178.99 13.190.233.43 14.212.178.106 15.103.92.114 17.167.179.41 19.161.72.122 20.58.184.140 20.141.185.205 20.195.231.146 20.211.135.135 20.247.51.204 21.116.122.76 23.104.140.88 23.238.226.87 24.32.65.138 25.70.209.245 26.169.29.250 26.190.150.175

Basic Information

IP Address

106.75.72.63

Domain

-

ISP

Shanghai UCloud Information Technology Company Lim

Country

China

WHOIS

Created Date

-

Updated Date

-

Organization

-

First seen in Akamai Guardicore Segmentation

2022-03-20

Last seen in Akamai Guardicore Segmentation

2022-04-11

What is Akamai Guardicore Segmentation
Akamai 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

Attack Flow

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

Process /dev/shm/apache2 scanned port 22 on 10 IP Addresses

Port 22 Scan Port 80 Scan Port 8080 Scan

Process /dev/shm/apache2 scanned port 80 on 10 IP Addresses

Port 22 Scan Port 80 Scan Port 8080 Scan

Process /dev/shm/apache2 scanned port 8080 on 10 IP Addresses

Port 22 Scan Port 80 Scan Port 8080 Scan

Process /dev/shm/apache2 scanned port 22 on 32 IP Addresses

Port 22 Scan Port 80 Scan Port 8080 Scan

Process /dev/shm/apache2 scanned port 22 on 32 IP Addresses

Port 22 Scan Port 80 Scan Port 8080 Scan

Process /dev/shm/apache2 generated outgoing network traffic to: 100.119.41.158:80, 100.119.41.158:8080, 101.42.108.123:1234, 103.129.239.225:22, 104.21.25.86:443, 106.75.72.63:1234, 112.8.153.118:80, 112.8.153.118:8080, 117.16.44.111:1234, 118.39.149.198:80, 118.39.149.198:8080, 120.111.18.116:80, 120.111.18.116:8080, 121.226.166.193:80, 121.226.166.193:8080, 125.154.83.65:80, 125.154.83.65:8080, 126.17.79.29:22, 129.84.3.232:80, 129.84.3.232:8080, 131.123.192.44:22, 136.2.144.67:80, 136.2.144.67:8080, 142.108.232.116:80, 142.108.232.116:8080, 145.19.189.27:80, 145.19.189.27:8080, 153.128.1.216:80, 153.128.1.216:8080, 16.217.147.98:22, 165.145.186.74:80, 165.145.186.74:8080, 169.37.109.109:80, 169.37.109.109:8080, 172.67.133.228:443, 182.231.244.241:2222, 185.113.77.83:22, 185.216.25.36:1234, 187.161.72.53:22, 187.223.72.151:80, 187.223.72.151:8080, 187.74.197.165:2222, 19.252.146.81:80, 19.252.146.81:8080, 197.123.228.175:2222, 199.89.49.241:80, 199.89.49.241:8080, 2.172.69.60:80, 2.172.69.60:8080, 204.92.199.140:80, 204.92.199.140:8080, 213.116.41.192:80, 213.116.41.192:8080, 22.120.176.219:80, 22.120.176.219:8080, 221.89.201.226:80, 221.89.201.226:8080, 223.171.91.191:1234, 23.124.124.11:80, 23.124.124.11:8080, 23.140.12.209:22, 247.220.157.84:80, 247.220.157.84:8080, 248.19.28.198:80, 248.19.28.198:8080, 31.121.223.250:80, 31.121.223.250:8080, 32.115.48.35:22, 5.209.199.148:80, 5.209.199.148:8080, 51.75.146.174:443, 53.142.155.152:80, 53.142.155.152:8080, 76.204.129.22:80, 76.204.129.22:8080, 77.197.188.22:80, 77.197.188.22:8080, 79.253.57.33:80, 79.253.57.33:8080, 80.177.231.22:2222, 80.7.24.38:2222, 81.180.242.174:1234, 83.40.42.41:22, 84.106.186.176:80, 84.106.186.176:8080, 91.80.135.179:1234, 95.165.130.171:2222, 97.150.224.60:80 and 97.150.224.60:8080

Outgoing Connection

Process /dev/shm/apache2 attempted to access suspicious domains: am0n8.shop, cultimording.org.uk, spd-mgts.ru, telesp.net.br and virginm.net

Access Suspicious Domain Outgoing Connection

Process /dev/shm/apache2 started listening on ports: 1234, 8081 and 8189

Listening

Process /dev/shm/apache2 scanned port 80 on 32 IP Addresses

Port 22 Scan Port 80 Scan Port 8080 Scan

Process /dev/shm/apache2 scanned port 8080 on 32 IP Addresses

Port 22 Scan Port 80 Scan Port 8080 Scan

Process /dev/shm/apache2 scanned port 80 on 32 IP Addresses

Port 22 Scan Port 80 Scan Port 8080 Scan

Process /dev/shm/apache2 scanned port 8080 on 32 IP Addresses

Port 22 Scan Port 80 Scan Port 8080 Scan

Connection was closed due to timeout