IP Address: 184.64.30.200Previously Malicious
IP Address: 184.64.30.200Previously Malicious
This IP address attempted an attack on a machine in our threat sensors network
Role |
Attacker, Scanner |
Services Targeted |
SCP SSH |
Tags |
Download File SSH Superuser Operation Successful SSH Login Download and Execute SCP Download and Allow Execution |
Associated Attack Servers |
health.mil Majordomo.ru nile-online.net pkje32x1.cn telia.com 30.101.154.48 34.60.221.232 36.84.63.238 38.192.19.59 41.199.18.253 44.14.229.109 45.153.186.205 60.15.18.121 65.163.25.144 81.70.94.80 81.198.117.224 84.61.123.63 86.196.176.132 89.138.104.70 89.162.206.103 94.176.145.45 101.42.108.123 103.152.118.20 110.42.139.41 111.90.78.135 114.211.126.49 115.254.63.51 117.50.179.61 118.214.142.44 123.13.155.101 128.243.167.244 129.152.6.35 143.219.33.46 153.121.36.169 155.196.223.235 |
IP Address |
184.64.30.200 |
|
Domain |
- |
|
ISP |
Shaw Communications |
|
Country |
Canada |
|
WHOIS |
Created Date |
- |
Updated Date |
- |
|
Organization |
- |
First seen in Akamai Guardicore Segmentation |
2022-03-27 |
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 |
/tmp/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 /tmp/apache2 scanned port 22 on 12 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /tmp/apache2 scanned port 80 on 12 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /tmp/apache2 scanned port 8080 on 12 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /tmp/apache2 scanned port 22 on 32 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /tmp/apache2 scanned port 22 on 32 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
The file /tmp/apache2 was downloaded and executed 197 times |
Download and Execute |
Process /tmp/apache2 generated outgoing network traffic to: 104.21.25.86:443, 11.128.180.18:80, 11.128.180.18:8080, 11.200.239.165:80, 11.200.239.165:8080, 110.103.38.226:80, 110.103.38.226:8080, 111.229.46.240:80, 111.229.46.240:8080, 117.146.172.106:1234, 123.120.124.149:80, 123.120.124.149:8080, 125.130.183.146:1234, 129.73.7.182:80, 129.73.7.182:8080, 130.61.80.99:80, 130.61.80.99:8080, 132.75.198.57:80, 132.75.198.57:8080, 136.23.148.56:80, 136.23.148.56:8080, 136.8.214.1:80, 136.8.214.1:8080, 138.48.150.126:22, 138.6.32.10:80, 138.6.32.10:8080, 148.109.24.28:22, 152.44.23.169:80, 152.44.23.169:8080, 153.154.82.80:80, 153.154.82.80:8080, 160.27.103.184:80, 160.27.103.184:8080, 164.19.3.55:22, 170.206.29.232:80, 170.206.29.232:8080, 172.67.133.228:443, 173.126.194.47:80, 173.126.194.47:8080, 173.4.177.121:2222, 174.86.8.34:80, 174.86.8.34:8080, 176.6.141.124:80, 176.6.141.124:8080, 176.60.230.63:22, 180.244.123.10:80, 180.244.123.10:8080, 180.89.36.89:2222, 185.37.10.54:22, 193.172.4.250:22, 195.59.206.39:22, 215.8.66.243:80, 215.8.66.243:8080, 215.96.148.158:80, 215.96.148.158:8080, 220.243.148.80:1234, 24.134.37.161:80, 24.134.37.161:8080, 240.248.63.146:22, 243.138.147.88:80, 243.138.147.88:8080, 247.188.93.234:80, 247.188.93.234:8080, 3.4.197.120:80, 3.4.197.120:8080, 36.92.125.163:1234, 40.76.124.23:2222, 43.160.19.238:80, 43.160.19.238:8080, 51.152.101.86:80, 51.152.101.86:8080, 51.75.146.174:443, 52.18.234.91:80, 52.18.234.91:8080, 56.9.249.84:22, 61.41.97.76:80, 61.41.97.76:8080, 65.202.157.235:1234, 74.245.15.165:80, 74.245.15.165:8080, 77.37.104.68:22, 81.78.232.204:2222, 82.157.127.47:1234, 88.67.131.152:1234, 92.110.142.249:22, 94.148.239.239:80, 94.148.239.239:8080, 94.67.167.104:80 and 94.67.167.104:8080 |
Outgoing Connection |
Process /tmp/apache2 started listening on ports: 1234, 8086 and 8183 |
Listening |
Process /tmp/apache2 scanned port 80 on 32 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /tmp/apache2 scanned port 8080 on 32 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /tmp/apache2 scanned port 80 on 32 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
Process /tmp/apache2 attempted to access suspicious domains: spcsdns.net and vodafone-ip.de |
Access Suspicious Domain Outgoing Connection |
Process /tmp/apache2 scanned port 8080 on 32 IP Addresses |
Port 22 Scan Port 80 Scan Port 8080 Scan |
The file /usr/bin/free was downloaded and executed |
Download and Execute |
The file /usr/bin/uptime was downloaded and executed |
Download and Execute |
The file /tmp/php-fpm was downloaded and executed 25 times |
Download and Execute |
The file /tmp/php-fpm was downloaded and executed 21 times |
Download and Execute |
The file /tmp/php-fpm was downloaded and executed 17 times |
Download and Execute |
Connection was closed due to timeout |
|