IP Address: 122.51.146.36Previously Malicious
IP Address: 122.51.146.36Previously Malicious
This IP address attempted an attack on a machine in our threat sensors network
Role |
Attacker, Connect-Back, Scanner |
Services Targeted |
SSH |
Tags |
Superuser Operation SFTP Bulk Files Tampering New SSH Key Download and Execute 21 Shell Commands Successful SSH Login Port 22 Scan SSH Download File |
Associated Attack Servers |
18.214.132.216 18.235.112.207 23.60.68.98 23.223.159.179 39.98.201.31 39.105.13.218 47.52.92.175 47.52.202.185 47.75.87.139 47.75.173.102 47.75.173.243 47.91.234.92 47.93.85.225 47.93.206.19 47.93.226.60 47.94.83.63 47.94.101.75 47.95.145.40 47.99.196.196 47.100.30.15 47.100.57.138 47.101.146.220 47.101.192.165 47.102.102.46 47.102.195.168 47.102.199.98 47.104.161.36 47.105.96.139 47.105.184.110 47.107.84.175 |
IP Address |
122.51.146.36 |
|
Domain |
- |
|
ISP |
Tencent cloud computing |
|
Country |
China |
|
WHOIS |
Created Date |
- |
Updated Date |
- |
|
Organization |
- |
First seen in Akamai Guardicore Segmentation |
2020-05-17 |
Last seen in Akamai Guardicore Segmentation |
2022-02-14 |
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 |
A possibly malicious Superuser Operation was detected 2 times |
Superuser Operation |
/tmp/.X25-unix/dota3.tar.gz was downloaded |
Download File |
The file /tmp/.X25-unix/.rsync/c/lib/64/tsm was downloaded and executed 85 times |
Download and Execute |
Process /bin/bash generated outgoing network traffic to: 192.168.0.100:22, 192.168.0.10:22, 192.168.0.11:22, 192.168.0.12:22, 192.168.0.13:22, 192.168.0.14:22, 192.168.0.15:22, 192.168.0.16:22, 192.168.0.17:22, 192.168.0.18:22, 192.168.0.19:22, 192.168.0.1:22, 192.168.0.20:22, 192.168.0.21:22, 192.168.0.22:22, 192.168.0.23:22, 192.168.0.24:22, 192.168.0.25:22, 192.168.0.26:22, 192.168.0.27:22, 192.168.0.28:22, 192.168.0.29:22, 192.168.0.2:22, 192.168.0.30:22, 192.168.0.31:22, 192.168.0.32:22, 192.168.0.33:22, 192.168.0.34:22, 192.168.0.35:22, 192.168.0.36:22, 192.168.0.37:22, 192.168.0.38:22, 192.168.0.39:22, 192.168.0.3:22, 192.168.0.40:22, 192.168.0.41:22, 192.168.0.42:22, 192.168.0.43:22, 192.168.0.44:22, 192.168.0.45:22, 192.168.0.46:22, 192.168.0.47:22, 192.168.0.48:22, 192.168.0.49:22, 192.168.0.4:22, 192.168.0.50:22, 192.168.0.51:22, 192.168.0.52:22, 192.168.0.53:22, 192.168.0.54:22, 192.168.0.55:22, 192.168.0.56:22, 192.168.0.57:22, 192.168.0.58:22, 192.168.0.59:22, 192.168.0.5:22, 192.168.0.60:22, 192.168.0.61:22, 192.168.0.62:22, 192.168.0.63:22, 192.168.0.64:22, 192.168.0.65:22, 192.168.0.66:22, 192.168.0.67:22, 192.168.0.68:22, 192.168.0.69:22, 192.168.0.6:22, 192.168.0.70:22, 192.168.0.71:22, 192.168.0.72:22, 192.168.0.73:22, 192.168.0.74:22, 192.168.0.75:22, 192.168.0.76:22, 192.168.0.77:22, 192.168.0.78:22, 192.168.0.79:22, 192.168.0.7:22, 192.168.0.80:22, 192.168.0.81:22, 192.168.0.82:22, 192.168.0.83:22, 192.168.0.84:22, 192.168.0.85:22, 192.168.0.86:22, 192.168.0.87:22, 192.168.0.88:22, 192.168.0.89:22, 192.168.0.8:22, 192.168.0.90:22, 192.168.0.91:22, 192.168.0.92:22, 192.168.0.93:22, 192.168.0.94:22, 192.168.0.95:22, 192.168.0.96:22, 192.168.0.97:22, 192.168.0.98:22, 192.168.0.99:22 and 192.168.0.9:22 |
|
Process /bin/bash scanned port 22 on 100 IP Addresses |
Port 22 Scan |
Connection was closed due to timeout |
|
An attempt to download /root/.ssh/authorized_keys was made |
New SSH Key |
Process /bin/bash performed bulk changes in {/} on 36 files |
Bulk Files Tampering |