Cyber Threat Intelligence

Discover malicious IPs and domains with Akamai Guardicore Segmentation

IP Address: 82.157.139.183Previously Malicious

IP Address: 82.157.139.183Previously 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 Access Suspicious Domain Port 8080 Scan 2 Shell Commands Download File SSH Superuser Operation Port 80 Scan Successful SSH Login Outgoing Connection SCP Listening

Associated Attack Servers

aniar.ie asahi-net.or.jp az1am5.shop aztecmusic.net bitternet.ua btcentralplus.com cloudfront.net cloudsouth.com cultimording.org.uk dial-up.net eastern-tele.com ertelecom.ru herza.id internetia.net.pl ip-54-38-175.eu kagoya.net mycingular.net ovo.sc pacbell.net poneytelecom.eu qwest.net rdsnet.ro safarizero.com smartone.com srasia-great.com tele2.se teol.net tropolys.de uznam.net.pl webpass.net

1.14.166.163 1.54.12.227 1.82.141.125 1.116.153.164 2.108.121.164 3.12.112.121 3.91.21.110 3.156.26.30 3.237.240.103 4.12.204.121 4.192.190.173 5.58.232.39 5.80.169.60 5.188.79.92 6.79.14.130 6.146.150.129 6.175.109.112 6.210.239.227 7.134.44.151 8.175.132.37 8.195.246.243 12.69.140.206 13.20.89.12 13.157.162.139 14.143.180.147 14.173.251.65 15.65.187.38 15.235.38.154 16.138.90.182 16.242.210.22

Basic Information

IP Address

82.157.139.183

Domain

-

ISP

Tencent Cloud Computing (Beijing) Co.

Country

China

WHOIS

Created Date

-

Updated Date

-

Organization

-

First seen in Akamai Guardicore Segmentation

2022-04-01

Last seen in Akamai Guardicore Segmentation

2022-04-23

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

/dev/shm/ifconfig was downloaded

Download File

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.1.1.1:443, 100.106.56.113:80, 100.106.56.113:8080, 101.43.173.48:1234, 105.189.128.148:2222, 110.210.155.109:80, 110.210.155.109:8080, 113.112.38.249:80, 113.112.38.249:8080, 115.120.8.170:80, 115.120.8.170:8080, 124.222.238.185:1234, 124.52.20.31:80, 124.52.20.31:8080, 143.181.73.163:2222, 148.139.38.88:80, 148.139.38.88:8080, 151.168.184.238:2222, 154.235.193.81:22, 154.42.245.95:80, 154.42.245.95:8080, 157.199.145.17:80, 157.199.145.17:8080, 160.177.25.174:2222, 160.57.208.202:80, 160.57.208.202:8080, 161.193.83.62:80, 161.193.83.62:8080, 162.84.160.115:80, 162.84.160.115:8080, 163.122.38.93:80, 163.122.38.93:8080, 164.86.103.18:2222, 169.209.136.35:80, 169.209.136.35:8080, 17.189.190.216:22, 170.100.77.247:80, 170.100.77.247:8080, 173.249.21.91:80, 173.249.21.91:8080, 177.87.8.224:80, 177.87.8.224:8080, 185.103.47.119:22, 185.47.28.60:80, 185.47.28.60:8080, 186.250.157.153:80, 186.250.157.153:8080, 187.177.101.101:2222, 192.144.229.35:1234, 2.108.121.164:22, 20.141.185.205:1234, 202.10.190.2:2222, 206.174.126.189:80, 206.174.126.189:8080, 208.28.101.131:80, 208.28.101.131:8080, 218.146.15.97:1234, 220.105.234.89:80, 220.105.234.89:8080, 222.147.64.156:80, 222.147.64.156:8080, 240.204.19.174:22, 241.31.115.104:22, 244.17.51.242:2222, 244.221.91.218:80, 244.221.91.218:8080, 248.131.165.122:80, 248.131.165.122:8080, 248.231.16.27:80, 248.231.16.27:8080, 25.103.216.77:80, 25.103.216.77:8080, 251.130.108.21:80, 251.130.108.21:8080, 34.150.60.2:2222, 49.116.44.49:80, 49.116.44.49:8080, 56.67.124.183:2222, 72.194.12.166:22, 82.156.217.40:1234, 82.157.139.183:1234, 87.114.100.41:80, 87.114.100.41:8080, 87.168.182.104:80, 87.168.182.104:8080, 90.232.51.166:80, 90.232.51.166:8080, 90.44.139.223:80 and 90.44.139.223:8080

Outgoing Connection

Process /dev/shm/apache2 started listening on ports: 1234, 8082 and 8181

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 10 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 8080 on 10 IP Addresses

Port 2222 Scan Port 80 Scan Port 8080 Scan

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

Port 2222 Scan Port 80 Scan Port 8080 Scan

Process /dev/shm/apache2 attempted to access suspicious domains: tdc.net

Access Suspicious Domain Outgoing Connection

Connection was closed due to timeout