Cyber Threat Intelligence

Discover malicious IPs and domains with Akamai Guardicore Segmentation

IP Address: 159.75.19.149Previously Malicious

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

1blu.de adslplus.ch aeza.network az1am5.shop belong.com.au chief.net.tw cloudfront.net ekk.bg gba.gov.ar kuas.edu.tw Majordomo.ru mchsi.com mycingular.net orange.sk pkje32x1.cn tenet.odessa.ua timbrasil.com.br tokai.or.jp tpnet.pl vorboss.net wellcom.at zcrtyshop.club

1.15.13.216 1.82.141.125 1.123.167.11 2.237.103.55 3.91.21.110 4.34.57.102 5.57.102.125 6.199.92.177 7.115.244.137 9.133.11.41 10.33.0.9 16.19.102.191 16.188.57.14 17.219.89.210 17.227.155.110 18.66.18.121 19.43.238.191 20.28.113.86 20.46.41.204 20.195.231.146 20.226.25.68 21.203.238.6 22.220.43.103 24.233.26.241 27.116.28.211 29.206.141.213 31.39.246.235 34.158.202.118 34.206.217.206 34.217.204.47

Basic Information

IP Address

159.75.19.149

Domain

-

ISP

Tencent Cloud Computing (Beijing) Co.

Country

China

WHOIS

Created Date

-

Updated Date

-

Organization

-

First seen in Akamai Guardicore Segmentation

2022-02-25

Last seen in Akamai Guardicore Segmentation

2022-04-08

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.53.183.209:2222, 102.201.185.60:80, 102.201.185.60:8080, 103.96.41.245:1234, 104.200.190.122:22, 104.21.25.86:443, 106.232.182.190:80, 106.232.182.190:8080, 113.234.204.159:80, 113.234.204.159:8080, 115.212.101.1:2222, 120.197.154.22:1234, 123.207.26.100:1234, 126.159.218.241:2222, 139.50.225.247:80, 139.50.225.247:8080, 149.46.97.220:80, 149.46.97.220:8080, 149.55.73.170:2222, 156.133.252.85:80, 156.133.252.85:8080, 159.75.19.149:1234, 161.62.42.72:80, 161.62.42.72:8080, 163.181.197.76:80, 163.181.197.76:8080, 166.139.176.167:80, 166.139.176.167:8080, 166.144.94.89:2222, 169.48.144.158:80, 169.48.144.158:8080, 17.26.227.17:80, 17.26.227.17:8080, 171.241.210.207:80, 171.241.210.207:8080, 172.67.133.228:443, 183.148.62.86:80, 183.148.62.86:8080, 188.13.229.138:80, 188.13.229.138:8080, 188.181.92.221:2222, 190.252.121.251:80, 190.252.121.251:8080, 191.239.145.186:80, 191.239.145.186:8080, 191.245.223.76:22, 2.3.19.44:80, 2.3.19.44:8080, 20.168.244.124:80, 20.168.244.124:8080, 204.4.145.145:80, 204.4.145.145:8080, 210.70.144.80:80, 210.70.144.80:8080, 213.43.70.248:80, 213.43.70.248:8080, 215.20.163.208:80, 215.20.163.208:8080, 222.165.136.99:1234, 250.129.238.87:22, 26.231.55.112:2222, 31.39.246.235:1234, 4.34.57.102:1234, 5.186.22.204:80, 5.186.22.204:8080, 50.5.149.243:2222, 51.124.209.44:80, 51.124.209.44:8080, 51.75.146.174:443, 53.198.18.247:80, 53.198.18.247:8080, 55.111.211.88:80, 55.111.211.88:8080, 56.119.133.143:2222, 57.91.210.26:80, 57.91.210.26:8080, 66.121.33.165:80, 66.121.33.165:8080, 66.171.206.102:80, 66.171.206.102:8080, 71.219.94.64:80, 71.219.94.64:8080, 74.49.47.136:80, 74.49.47.136:8080, 74.55.106.225:2222, 76.203.121.139:80, 76.203.121.139:8080, 91.179.98.76:2222 and 95.110.179.250:2222

Outgoing Connection

Process /dev/shm/apache2 started listening on ports: 1234, 8084 and 8180

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 12 IP Addresses

Port 2222 Scan Port 80 Scan Port 8080 Scan

Process /dev/shm/apache2 attempted to access suspicious domains: bbox.fr, claro.net.br and limerick.co.in

Access Suspicious Domain Outgoing Connection

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 12 IP Addresses

Port 2222 Scan Port 80 Scan Port 8080 Scan

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

Port 2222 Scan Port 80 Scan Port 8080 Scan

Connection was closed due to timeout