Cyber Threat Intelligence

Discover malicious IPs and domains with Akamai Guardicore Segmentation

IP Address: 1.15.102.11Previously Malicious

IP Address: 1.15.102.11Previously 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 2222 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

aniar.ie btcentralplus.com checkpoint.com cultimording.org.uk fju.edu.tw gvt.net.br harvard.edu integra.net mchsi.com prima.net.ar starman.ee telefonica.net telenet.be telenormobil.no telmex.net.ar tesene.it vultrusercontent.com

2.150.76.23 3.55.167.151 8.44.15.210 8.89.187.150 9.135.61.231 11.148.227.180 13.87.67.199 13.122.185.50 14.230.229.67 17.128.140.55 18.212.180.57 18.251.179.19 20.44.224.63 20.58.184.140 26.134.200.20 26.211.116.12 29.203.93.168 30.162.194.198 32.124.177.201 33.130.224.131 34.195.158.59 34.229.7.53 35.33.205.36 35.170.191.119 36.69.131.107 36.77.94.79 37.31.205.4 37.135.22.223 38.106.131.117

Basic Information

IP Address

1.15.102.11

Domain

-

ISP

Tencent cloud computing

Country

China

WHOIS

Created Date

-

Updated Date

-

Organization

-

First seen in Akamai Guardicore Segmentation

2022-04-13

Last seen in Akamai Guardicore Segmentation

2022-10-24

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 generated outgoing network traffic to: 1.1.1.1:443, 1.15.102.11:1234, 101.248.130.12:80, 101.248.130.12:8080, 103.16.70.245:1234, 103.249.236.11:80, 103.249.236.11:8080, 109.169.174.211:2222, 109.250.59.167:80, 109.250.59.167:8080, 112.49.182.128:80, 112.49.182.128:8080, 112.52.170.218:22, 116.46.52.198:80, 116.46.52.198:8080, 117.54.14.169:1234, 118.18.166.148:2222, 129.63.52.15:80, 129.63.52.15:8080, 143.244.138.59:1234, 144.70.240.33:80, 144.70.240.33:8080, 145.102.239.149:80, 145.102.239.149:8080, 148.82.250.113:80, 148.82.250.113:8080, 15.119.6.131:1234, 152.235.33.104:80, 152.235.33.104:8080, 163.240.58.170:80, 163.240.58.170:8080, 167.148.165.195:22, 170.178.4.140:2222, 174.52.212.151:80, 174.52.212.151:8080, 176.1.33.100:2222, 18.212.180.57:1234, 183.242.11.105:80, 183.242.11.105:8080, 190.137.245.44:22, 190.239.71.36:80, 190.239.71.36:8080, 195.7.212.78:80, 195.7.212.78:8080, 20.246.235.145:2222, 205.206.218.244:2222, 206.177.214.248:2222, 209.122.248.228:80, 209.122.248.228:8080, 212.204.162.180:80, 212.204.162.180:8080, 222.125.31.101:80, 222.125.31.101:8080, 243.4.249.153:80, 243.4.249.153:8080, 243.99.212.165:80, 243.99.212.165:8080, 246.147.210.236:2222, 247.195.106.2:80, 247.195.106.2:8080, 30.21.208.125:80, 30.21.208.125:8080, 35.177.122.60:80, 35.177.122.60:8080, 38.106.131.117:22, 39.73.252.46:80, 39.73.252.46:8080, 47.240.206.171:80, 47.240.206.171:8080, 56.250.207.107:80, 56.250.207.107:8080, 57.55.85.49:80, 57.55.85.49:8080, 58.44.63.192:2222, 62.12.106.6:1234, 81.69.238.110:80, 81.69.238.110:8080, 84.135.202.29:80, 84.135.202.29:8080, 84.200.235.95:22, 89.46.103.102:22, 92.66.41.32:80, 92.66.41.32:8080, 94.198.78.227:80, 94.198.78.227:8080, 94.92.71.219:2222, 99.139.222.88:22, 99.54.40.39:80 and 99.54.40.39:8080

Outgoing Connection

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

Listening

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

Port 2222 Scan Port 80 Scan Port 8080 Scan

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

Port 2222 Scan Port 80 Scan Port 8080 Scan

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

Port 2222 Scan Port 80 Scan Port 8080 Scan

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

Port 2222 Scan Port 80 Scan Port 8080 Scan

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

Port 2222 Scan Port 80 Scan Port 8080 Scan

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

Port 2222 Scan Port 80 Scan Port 8080 Scan

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

Port 2222 Scan Port 80 Scan Port 8080 Scan

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

Port 2222 Scan Port 80 Scan Port 8080 Scan

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

Port 2222 Scan Port 80 Scan Port 8080 Scan

Process /dev/shm/apache2 attempted to access suspicious domains: intelicontacts.com and telecom.net.ar

Access Suspicious Domain Outgoing Connection

Connection was closed due to timeout

Associated Files

/var/tmp/php-fpm

SHA256: d9ee6cbbc40b3b337e3af157b14a1e7ac276c9f27c2efcd8daa21ded4bd810b6

2875940 bytes