IP Address: 81.70.21.147Previously Malicious
IP Address: 81.70.21.147Previously 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 |
airtel.mw alter.net attdns.com btcentralplus.com canl.nc cultimording.org.uk health.mil ip-151-80-242.eu kj4l3yh8.cn mchsi.com pkje32x1.cn qwest.net regruhosting.ru salesforce.com sileman.net.pl spcsdns.net telecel.com.py telia.com veloxzone.com.br zcrtyshop.club 1.235.69.230 2.16.127.160 2.138.136.63 3.23.115.246 3.91.21.110 3.104.143.93 4.19.185.228 5.100.159.216 6.72.128.194 8.35.73.157 8.94.11.219 9.166.39.182 14.85.83.162 17.55.81.72 17.77.181.53 17.144.36.126 17.220.8.149 20.32.246.95 20.250.152.45 22.190.71.211 24.154.232.158 24.209.244.56 28.49.163.221 28.105.69.222 29.68.71.70 29.149.51.117 30.31.48.1 32.55.71.89 33.133.148.167 34.126.28.37 |
IP Address |
81.70.21.147 |
|
Domain |
- |
|
ISP |
Tencent Cloud Computing (Beijing) Co. |
|
Country |
China |
|
WHOIS |
Created Date |
- |
Updated Date |
- |
|
Organization |
- |
First seen in Akamai Guardicore Segmentation |
2022-02-03 |
Last seen in Akamai Guardicore Segmentation |
2022-04-05 |
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: 101.43.113.193:80, 101.43.113.193:8080, 103.90.177.102:1234, 104.201.132.247:80, 104.201.132.247:8080, 104.21.25.86:443, 106.55.235.133:80, 106.55.235.133:8080, 120.140.205.192:80, 120.140.205.192:8080, 121.244.214.119:22, 123.13.155.101:1234, 123.46.142.194:80, 123.46.142.194:8080, 125.130.183.146:1234, 13.98.48.15:22, 132.120.58.220:22, 142.251.32.4:443, 162.144.158.56:1234, 167.166.246.58:80, 167.166.246.58:8080, 169.196.142.79:80, 169.196.142.79:8080, 172.109.185.199:80, 172.109.185.199:8080, 172.67.133.228:443, 173.220.42.243:80, 173.220.42.243:8080, 175.88.155.248:80, 175.88.155.248:8080, 181.140.97.61:80, 181.140.97.61:8080, 186.16.143.140:2222, 188.22.131.39:80, 188.22.131.39:8080, 19.104.38.235:80, 19.104.38.235:8080, 19.172.193.6:80, 19.172.193.6:8080, 193.87.9.129:22, 197.69.217.13:22, 20.30.189.116:22, 203.110.216.205:80, 203.110.216.205:8080, 203.126.134.17:80, 203.126.134.17:8080, 208.109.37.82:1234, 216.14.178.93:22, 22.170.189.158:80, 22.170.189.158:8080, 220.95.77.4:22, 251.83.80.190:80, 251.83.80.190:8080, 253.76.96.48:80, 253.76.96.48:8080, 29.8.62.37:80, 29.8.62.37:8080, 32.55.71.89:2222, 35.193.11.73:80, 35.193.11.73:8080, 37.157.5.45:2222, 38.11.208.158:22, 38.167.179.224:2222, 38.53.193.75:80, 38.53.193.75:8080, 39.206.49.127:80, 39.206.49.127:8080, 45.153.186.205:1234, 50.145.231.57:80, 50.145.231.57:8080, 51.75.146.174:443, 57.14.30.194:80, 57.14.30.194:8080, 60.241.132.109:80, 60.241.132.109:8080, 61.188.172.90:2222, 69.82.235.10:80, 69.82.235.10:8080, 78.77.90.83:80, 78.77.90.83:8080, 81.70.21.147:1234, 85.72.20.187:80, 85.72.20.187:8080, 9.142.25.54:80, 9.142.25.54:8080, 96.33.127.192:80, 96.33.127.192:8080, 98.193.87.189:80 and 98.193.87.189:8080 |
Outgoing Connection |
Process /dev/shm/apache2 started listening on ports: 1234, 8086 and 8188 |
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 attempted to access suspicious domains: adsl, hosted-by-mvps.net and telecel.com.py |
Access Suspicious Domain Outgoing Connection |
Process /dev/shm/apache2 scanned port 8080 on 32 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Connection was closed due to timeout |
|