Cyber Threat Intelligence

Discover malicious IPs and domains with Akamai Guardicore Segmentation

IP Address: 124.79.72.174Previously Malicious

IP Address: 124.79.72.174Previously Malicious

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

Threat Information

Role

Attacker, Scanner

Services Targeted

SCP SSH

Tags

Port 1234 Scan Port 80 Scan Successful SSH Login SCP Download File SSH Download and Execute Outgoing Connection Port 8080 Scan Superuser Operation

Associated Attack Servers

aeza.network attdns.com cloudhost.asia dscga.com innovatelekom.com inter.net.il ip-51-222-212.net kbtelecom.net mycingular.net ntust.edu.tw pikara.ne.jp spcsdns.net versatel.nl

2.87.72.160 3.91.21.110 3.110.236.209 4.63.124.222 8.26.162.32 11.208.54.64 15.98.75.12 19.136.196.8 20.51.115.180 20.58.184.140 20.82.195.11 20.226.25.68 21.44.112.71 24.164.138.87 28.51.34.114 29.106.133.21 29.132.42.68 31.115.9.149 31.201.33.220 37.126.197.221 39.2.177.221 41.39.182.198 42.169.171.113 42.231.29.38 45.142.122.215 48.222.205.126 50.87.233.199 51.222.212.139 54.150.227.19 54.183.22.120

Basic Information

IP Address

124.79.72.174

Domain

-

ISP

China Telecom Shanghai

Country

China

WHOIS

Created Date

-

Updated Date

-

Organization

-

First seen in Akamai Guardicore Segmentation

2022-03-25

Last seen in Akamai Guardicore Segmentation

2022-05-15

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 2 times

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

The file /tmp/apache2 was downloaded and executed 165 times

Download and Execute

Process /tmp/apache2 scanned port 1234 on 26 IP Addresses

Port 1234 Scan Port 80 Scan Port 8080 Scan

Process /tmp/apache2 scanned port 80 on 26 IP Addresses

Port 1234 Scan Port 80 Scan Port 8080 Scan

Process /tmp/apache2 scanned port 8080 on 26 IP Addresses

Port 1234 Scan Port 80 Scan Port 8080 Scan

Process /tmp/apache2 scanned port 1234 on 32 IP Addresses

Port 1234 Scan Port 80 Scan Port 8080 Scan

Process /tmp/apache2 scanned port 1234 on 19 IP Addresses

Port 1234 Scan Port 80 Scan Port 8080 Scan

Process /usr/sbin/sshd scanned port 1234 on 26 IP Addresses

Port 1234 Scan

Process /bin/bash scanned port 1234 on 26 IP Addresses

Port 1234 Scan

Process /tmp/apache2 generated outgoing network traffic to: 1.1.1.1:443, 1.44.130.66:80, 103.105.12.48:1234, 103.44.122.152:80, 103.44.122.152:8080, 105.183.241.121:80, 110.57.118.232:80, 111.53.11.130:1234, 117.16.44.111:1234, 118.218.209.149:1234, 120.224.34.31:1234, 120.224.34.31:22, 120.31.133.162:1234, 132.242.124.36:80, 132.242.124.36:8080, 135.45.200.178:80, 135.45.200.178:8080, 136.192.113.49:80, 136.192.113.49:8080, 136.97.162.12:80, 139.209.222.134:1234, 14.44.192.136:80, 142.250.191.132:443, 150.107.95.20:1234, 161.107.113.34:1234, 161.35.79.199:1234, 163.117.93.98:80, 168.207.59.210:80, 172.67.133.228:443, 173.18.35.41:1234, 184.83.112.246:1234, 185.189.49.83:443, 185.189.49.83:80, 185.189.49.83:8080, 190.68.216.188:80, 190.68.216.188:8080, 20.141.185.205:1234, 200.57.46.209:80, 218.146.15.97:1234, 218.146.15.97:22, 222.100.124.62:1234, 223.171.91.127:1234, 223.171.91.160:1234, 223.171.91.191:1234, 251.149.190.158:80, 251.149.190.158:8080, 253.40.41.97:80, 253.40.41.97:8080, 30.188.199.190:80, 34.121.83.127:80, 34.121.83.127:8080, 37.178.49.121:80, 37.178.49.121:8080, 39.175.68.100:1234, 4.251.134.165:80, 4.251.134.165:8080, 43.242.247.139:1234, 45.120.216.114:1234, 49.115.64.109:80, 49.115.64.109:8080, 51.159.19.47:1234, 51.75.146.174:443, 54.91.6.156:80, 54.91.6.156:8080, 57.186.232.13:80, 61.221.53.175:80, 61.221.53.175:8080, 62.85.138.42:80, 64.235.66.150:80, 64.235.66.150:8080, 72.64.197.156:80, 74.129.147.49:80, 74.129.147.49:8080, 8.8.4.4:443, 8.8.8.8:443, 81.114.111.27:80, 82.66.5.84:1234, 83.149.68.109:80, 83.149.68.109:8080, 85.105.82.39:1234, 85.234.184.198:80, 85.234.184.198:8080, 85.238.240.45:80 and 85.238.240.45:8080

Outgoing Connection

Process /tmp/apache2 started listening on ports: 1234, 8089 and 8184

Listening

Process /tmp/apache2 scanned port 80 on 32 IP Addresses

Port 1234 Scan Port 80 Scan Port 8080 Scan

Process /tmp/apache2 scanned port 8080 on 32 IP Addresses

Port 1234 Scan Port 80 Scan Port 8080 Scan

Process /tmp/apache2 scanned port 80 on 19 IP Addresses

Port 1234 Scan Port 80 Scan Port 8080 Scan

Process /tmp/apache2 attempted to access suspicious domains: inleed.net

Access Suspicious Domain Outgoing Connection

Process /tmp/apache2 scanned port 8080 on 19 IP Addresses

Port 1234 Scan Port 80 Scan Port 8080 Scan

The file /usr/bin/uptime was downloaded and executed

Download and Execute

Connection was closed due to timeout

Associated Files

/tmp/ifconfig

SHA256: 9605e4e56eed344c6e178e023ac3191fda19a952f031574a9e18103c6ff4de2e

917504 bytes