Cyber Threat Intelligence

Discover malicious IPs and domains with Akamai Guardicore Segmentation

IP Address: 168.61.44.18Previously Malicious

IP Address: 168.61.44.18Previously 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 Download and Allow Execution Listening Outgoing Connection Port 8080 Scan Superuser Operation 4 Shell Commands

Associated Attack Servers

attdns.com btcentralplus.com cultimording.org.uk spcsdns.net srasia-great.com swisscom.ch vultrusercontent.com

13.140.94.114 23.250.84.116 36.19.64.52 36.29.130.24 42.194.138.246 43.242.247.139 45.32.89.249 47.93.228.251 54.209.216.131 56.118.60.232 58.221.44.158 68.166.75.54 76.106.55.98 80.250.42.42 81.70.147.119 82.157.50.152 86.22.188.226 86.133.233.66 100.200.6.13 101.42.90.177 101.42.101.141 101.42.108.123 101.42.223.157 101.42.237.46 101.43.142.151 103.52.147.126 103.90.177.102 105.60.167.250 107.182.190.58 107.183.145.15

Basic Information

IP Address

168.61.44.18

Domain

-

ISP

Microsoft Corp

Country

United States

WHOIS

Created Date

-

Updated Date

-

Organization

-

First seen in Akamai Guardicore Segmentation

2022-04-14

Last seen in Akamai Guardicore Segmentation

2022-07-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

The file /tmp/ifconfig was downloaded and executed 5 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 1234 on 32 IP Addresses

Port 1234 Scan Port 80 Scan Port 8080 Scan

Process /tmp/apache2 scanned port 1234 on 31 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 /usr/sbin/sshd scanned port 1234 on 26 IP Addresses

Port 1234 Scan

Process /bin/nc.openbsd scanned port 1234 on 26 IP Addresses

Port 1234 Scan

Process /tmp/apache2 generated outgoing network traffic to: 112.5.65.248:80, 112.5.65.248:8080, 117.16.44.111:1234, 117.54.14.169:1234, 117.80.212.33:1234, 117.83.247.134:80, 117.83.247.134:8080, 118.218.209.149:1234, 118.228.177.79:80, 118.228.177.79:8080, 120.224.34.31:1234, 120.236.78.194:1234, 138.144.172.152:80, 138.144.172.152:8080, 139.13.237.173:80, 139.13.237.173:8080, 139.209.222.134:1234, 139.95.206.221:80, 139.95.206.221:8080, 142.250.191.132:443, 148.187.36.16:80, 148.187.36.16:8080, 15.64.114.67:80, 15.64.114.67:8080, 150.107.95.20:1234, 151.10.128.115:80, 151.10.128.115:8080, 153.174.70.235:80, 153.174.70.235:8080, 157.231.37.101:80, 157.231.37.101:8080, 160.17.189.61:80, 160.17.189.61:8080, 160.56.115.194:80, 160.56.115.194:8080, 161.70.98.32:1234, 163.244.72.156:80, 163.244.72.156:8080, 18.199.215.250:80, 18.199.215.250:8080, 184.83.112.246:1234, 185.210.144.122:1234, 191.242.188.103:1234, 198.136.125.226:80, 198.136.125.226:8080, 20.141.185.205:1234, 212.57.36.20:1234, 213.36.154.46:80, 213.36.154.46:8080, 219.81.100.153:80, 219.81.100.153:8080, 221.144.166.130:80, 221.144.166.130:8080, 222.100.124.62:1234, 222.121.63.87:1234, 222.165.136.99:1234, 223.171.91.191:1234, 25.61.2.211:80, 25.61.2.211:8080, 252.222.30.66:80, 252.222.30.66:8080, 253.226.63.178:80, 253.226.63.178:8080, 27.80.237.118:80, 27.80.237.118:8080, 28.179.208.220:80, 39.175.68.100:1234, 49.233.159.222:1234, 50.101.24.47:80, 50.101.24.47:8080, 51.75.146.174:443, 56.75.16.71:80, 56.75.16.71:8080, 58.229.125.66:1234, 61.84.162.66:1234, 62.204.208.216:80, 62.204.208.216:8080, 74.169.116.129:80, 74.169.116.129:8080, 80.147.162.151:1234, 81.13.73.79:80, 81.13.73.79:8080, 82.149.112.170:1234, 82.81.48.18:80, 82.81.48.18:8080, 9.170.21.34:80, 9.170.21.34:8080, 97.172.165.80:80 and 97.172.165.80:8080

Outgoing Connection

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

Listening

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

Download and Execute

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

Port 1234 Scan Port 80 Scan Port 8080 Scan

Process /tmp/apache2 scanned port 80 on 31 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 8080 on 31 IP Addresses

Port 1234 Scan Port 80 Scan Port 8080 Scan

Process /usr/local/mysql/bin/mysqld started listening on ports: 3306

Listening

Process /usr/local/apache2/bin/httpd started listening on ports: 80

Listening

Connection was closed due to user inactivity