Cyber Threat Intelligence

Discover malicious IPs and domains with Akamai Guardicore Segmentation

IP Address: 125.59.11.21Previously Malicious

IP Address: 125.59.11.21Previously Malicious

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

Threat Information

Role

Attacker, Scanner

Services Targeted

SSH

Tags

1 Shell Commands System File Modification Kill Process Service Creation Executable File Modification Download File Service Start SSH Listening Outgoing Connection Access Suspicious Domain Successful SSH Login Download and Allow Execution Download and Execute Port 80 Scan

Associated Attack Servers

ipfs.io

104.131.131.82 136.144.56.255 147.75.47.199

Basic Information

IP Address

125.59.11.21

Domain

-

ISP

HK Cable TV

Country

Hong Kong

WHOIS

Created Date

-

Updated Date

-

Organization

-

First seen in Akamai Guardicore Segmentation

2020-09-02

Last seen in Akamai Guardicore Segmentation

2020-09-02

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 possibly malicious Kill Process was detected 2 times

Kill Process

The file /tmp/storm was downloaded and executed 19 times

Download and Execute

System file /etc/storm.key was modified 4 times

System File Modification

Executable file /usr/bin/storm was modified 16 times

Executable File Modification

Service storm was created and started

Service Start Service Creation

The file /usr/bin/storm was downloaded and executed 11 times

Download and Execute

Process /usr/bin/storm generated outgoing network traffic to: 104.131.131.82:4001, 104.24.122.146:80, 104.24.123.146:80, 107.20.34.193:80, 136.144.56.255:443, 146.112.255.205:80, 147.75.47.199:443, 172.217.9.83:80, 172.67.189.102:80, 176.58.123.25:80, 18.209.184.162:80, 18.235.80.73:80, 193.200.132.187:80, 204.237.142.122:80, 204.237.142.144:80, 216.239.32.21:443, 216.239.34.21:443, 216.239.36.21:443, 216.239.38.21:443, 23.21.47.155:80, 3.224.112.167:80, 3.226.27.10:80, 3.92.247.111:80, 34.193.114.5:80, 34.205.208.47:80, 52.20.94.130:80, 52.70.92.19:80, 54.157.99.255:80 and 8.8.8.8:53

Outgoing Connection

Process /usr/bin/storm started listening on ports: 36683

Listening

Process /usr/bin/storm attempted to access suspicious domains: dns.google, icanhazip-dfw-1 and icanhazip-iad-1

Access Suspicious Domain Outgoing Connection

Process /usr/bin/storm scanned port 80 on 21 IP Addresses

Port 80 Scan

Connection was closed due to timeout