Cyber Threat Intelligence

Discover malicious IPs and domains with Akamai Guardicore Segmentation

IP Address: 144.217.5.204Malicious

IP Address: 144.217.5.204Malicious

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

Successful SSH Login SCP Download File SSH Download and Execute Superuser Operation

Associated Attack Servers

61.in-addr.arpa ameritech.net az1am5.shop cable.net.co cloudwaysapps.com dreamhost.com herza.id iia.cl neu.edu ovh.ca ovh.net poneytelecom.eu rr.com scw.cloud sfr.net spd-mgts.ru srasia-great.com telecomitalia.it telenet.be turktelekom.com.tr vultrusercontent.com ziplyfiber.com

1.1.1.1 1.116.153.164 1.214.98.77 2.160.230.244 3.212.187.48 5.188.79.92 5.222.27.166 7.67.233.227 8.215.36.214 9.3.207.171 9.151.125.199 13.87.67.199 14.124.239.120 15.167.115.70 16.96.185.90 16.139.253.208 18.31.29.76 18.86.62.44 20.111.78.83 20.215.149.68 23.123.78.241 23.232.167.148 25.113.121.111 25.163.6.154 26.131.114.248 31.239.126.20 34.91.173.198 36.77.94.79 37.190.57.217 40.72.206.216

Basic Information

IP Address

144.217.5.204

Domain

-

ISP

OVH Hosting

Country

Canada

WHOIS

Created Date

-

Updated Date

-

Organization

-

First seen in Akamai Guardicore Segmentation

2022-03-28

Last seen in Akamai Guardicore Segmentation

2023-03-29

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

System file /etc/apache2 was modified 4 times

System File Modification

The file /etc/ifconfig was downloaded and executed 4 times

Download and Execute

The file /etc/apache2 was downloaded and executed 186 times

Download and Execute

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

Port 1234 Scan

Process /etc/apache2 scanned port 1234 on 27 IP Addresses

Port 1234 Scan Port 80 Scan Port 8080 Scan

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

Port 1234 Scan Port 80 Scan Port 8080 Scan

Process /etc/apache2 scanned port 1234 on 29 IP Addresses

Port 1234 Scan Port 80 Scan Port 8080 Scan

Process /etc/apache2 scanned port 80 on 27 IP Addresses

Port 1234 Scan Port 80 Scan Port 8080 Scan

Process /etc/apache2 scanned port 8080 on 27 IP Addresses

Port 1234 Scan Port 80 Scan Port 8080 Scan

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

Port 1234 Scan

Process /etc/apache2 generated outgoing network traffic to: 1.220.98.197:1234, 103.105.12.48:1234, 104.21.25.86:443, 106.76.195.60:80, 106.76.195.60:8080, 111.53.11.130:1234, 120.31.133.162:1234, 124.115.231.214:1234, 124.223.14.100:1234, 129.151.177.31:80, 129.151.177.31:8080, 139.209.222.134:1234, 150.107.95.20:1234, 154.95.102.31:80, 154.95.102.31:8080, 159.152.217.18:80, 159.152.217.18:8080, 160.181.188.5:80, 161.107.113.27:1234, 172.67.133.228:443, 174.15.99.198:80, 174.15.99.198:8080, 175.123.52.38:80, 175.123.52.38:8080, 181.63.2.208:80, 181.63.2.208:8080, 185.210.144.122:1234, 188.27.125.109:80, 188.27.125.109:8080, 189.159.44.73:80, 189.159.44.73:8080, 190.138.240.233:1234, 190.60.239.44:1234, 190.76.247.172:80, 190.76.247.172:8080, 191.105.206.87:80, 191.105.206.87:8080, 191.242.182.210:1234, 197.176.232.107:80, 197.176.232.107:8080, 2.155.234.98:80, 2.155.234.98:8080, 20.104.112.39:80, 20.104.112.39:8080, 200.134.14.64:80, 200.134.14.64:8080, 208.106.20.75:80, 208.106.20.75:8080, 209.216.177.158:1234, 209.216.177.238:1234, 21.108.187.20:80, 21.108.187.20:8080, 212.57.36.20:1234, 216.84.138.221:80, 220.243.148.80:1234, 222.100.124.62:1234, 223.171.91.127:1234, 223.171.91.149:1234, 241.39.35.170:80, 241.39.35.170:8080, 251.209.167.70:80, 251.209.167.70:8080, 252.119.181.25:80, 252.119.181.25:8080, 29.193.56.53:80, 29.193.56.53:8080, 31.19.237.170:1234, 36.32.228.158:80, 36.68.118.209:80, 36.68.118.209:8080, 37.113.118.90:80, 37.113.118.90:8080, 39.143.238.154:80, 39.143.238.154:8080, 39.175.68.100:1234, 40.208.22.236:80, 40.208.22.236:8080, 43.242.247.139:1234, 51.75.146.174:443, 57.237.130.2:80, 57.237.130.2:8080, 61.141.101.185:80, 61.141.101.185:8080, 68.100.188.95:80, 68.100.188.95:8080, 72.41.149.133:80, 72.41.149.133:8080, 80.147.162.151:1234 and 82.149.112.170:1234

Outgoing Connection

Process /etc/apache2 started listening on ports: 1234, 8087 and 8189

Listening

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

Port 1234 Scan Port 80 Scan Port 8080 Scan

Process /etc/apache2 scanned port 80 on 29 IP Addresses

Port 1234 Scan Port 80 Scan Port 8080 Scan

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

Port 1234 Scan Port 80 Scan Port 8080 Scan

Process /etc/apache2 scanned port 8080 on 29 IP Addresses

Port 1234 Scan Port 80 Scan Port 8080 Scan

Connection was closed due to timeout