IP Address: 110.42.161.158Previously Malicious
IP Address: 110.42.161.158Previously Malicious
This IP address attempted an attack on a machine in our threat sensors network
Role |
Attacker, Connect-Back, Scanner |
Services Targeted |
SCP SSH |
Tags |
Port 22 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 |
af.mil attdns.com az1am5.shop btcentralplus.com comunitel.net globofiber.com.br innovatelekom.com mycingular.net ntust.edu.tw prostarheaven.net spcsdns.net telia.com tenet.odessa.ua utilitytelephone.net vorboss.net wellcom.at zcrtyshop.club 1.119.152.110 2.71.77.121 2.90.128.144 2.233.242.146 3.91.21.110 6.210.113.169 9.47.218.126 11.22.102.152 11.219.172.201 12.23.46.220 12.176.188.225 13.94.102.8 13.199.202.11 14.144.42.89 15.152.213.8 16.35.190.195 17.120.184.199 18.131.55.234 18.176.208.194 18.248.157.204 20.58.184.140 21.72.205.221 23.94.56.185 23.230.160.52 25.93.50.53 28.68.45.146 28.167.232.15 29.88.162.98 30.111.76.184 30.124.31.242 |
IP Address |
110.42.161.158 |
|
Domain |
- |
|
ISP |
Tencent cloud computing |
|
Country |
China |
|
WHOIS |
Created Date |
- |
Updated Date |
- |
|
Organization |
- |
First seen in Akamai Guardicore Segmentation |
2021-12-26 |
Last seen in Akamai Guardicore Segmentation |
2022-04-08 |
What is Akamai Guardicore SegmentationAkamai 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
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 scanned port 22 on 10 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /dev/shm/apache2 scanned port 80 on 10 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /dev/shm/apache2 scanned port 8080 on 10 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /dev/shm/apache2 scanned port 22 on 32 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /dev/shm/apache2 scanned port 22 on 32 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /dev/shm/apache2 generated outgoing network traffic to: 1.1.1.1:443, 101.43.184.100:1234, 107.112.23.51:80, 107.112.23.51:8080, 110.42.161.158:1234, 112.143.210.68:22, 118.204.60.144:80, 118.204.60.144:8080, 118.31.16.15:2222, 119.91.91.82:1234, 120.53.123.221:1234, 122.217.103.87:2222, 142.250.190.4:443, 143.119.248.37:80, 143.119.248.37:8080, 144.126.38.102:80, 144.126.38.102:8080, 15.145.168.20:80, 15.145.168.20:8080, 160.53.28.41:22, 163.71.153.124:22, 164.148.42.64:80, 164.148.42.64:8080, 166.195.119.106:80, 166.195.119.106:8080, 171.7.125.63:80, 171.7.125.63:8080, 187.14.136.241:80, 187.14.136.241:8080, 190.55.78.173:22, 20.211.71.35:80, 20.211.71.35:8080, 203.165.108.224:2222, 205.165.3.30:80, 205.165.3.30:8080, 205.49.195.86:2222, 208.122.1.41:80, 208.122.1.41:8080, 222.31.149.65:80, 222.31.149.65:8080, 240.132.53.25:22, 240.89.199.179:80, 240.89.199.179:8080, 241.238.51.180:80, 241.238.51.180:8080, 248.216.141.136:80, 248.216.141.136:8080, 249.196.59.38:80, 249.196.59.38:8080, 249.56.70.118:80, 249.56.70.118:8080, 25.93.50.53:2222, 252.214.63.78:22, 32.82.52.203:22, 33.81.206.23:2222, 39.138.229.209:80, 39.138.229.209:8080, 4.150.119.38:80, 4.150.119.38:8080, 42.76.20.78:22, 49.166.59.202:1234, 52.85.131.244:80, 52.85.131.244:8080, 54.239.40.44:80, 54.239.40.44:8080, 6.178.34.38:80, 6.178.34.38:8080, 61.119.249.34:80, 61.119.249.34:8080, 61.187.101.159:80, 61.187.101.159:8080, 61.221.99.76:80, 61.221.99.76:8080, 65.80.102.144:22, 69.176.132.14:80, 69.176.132.14:8080, 75.219.215.179:80, 75.219.215.179:8080, 82.157.127.47:1234, 82.33.228.105:80, 82.33.228.105:8080, 84.215.250.236:80, 84.215.250.236:8080, 89.208.72.234:80, 89.208.72.234:8080, 9.128.44.213:80, 9.128.44.213:8080, 9.47.218.126:2222 and 91.80.149.199:1234 |
Outgoing Connection |
Process /dev/shm/apache2 started listening on ports: 1234, 8080 and 8187 |
Listening |
Process /dev/shm/apache2 scanned port 80 on 32 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /dev/shm/apache2 scanned port 8080 on 32 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /dev/shm/apache2 scanned port 80 on 32 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /dev/shm/apache2 scanned port 8080 on 32 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /dev/shm/apache2 attempted to access suspicious domains: home.ne.jp |
Access Suspicious Domain Outgoing Connection |
Connection was closed due to timeout |
|