Go
106.13.56.204
is a
Hacker
100 %
China
Report Abuse
161attacks reported
95Brute-ForceSSH
25Port Scan
14FTP Brute-ForceHacking
8uncategorized
6SSH
3Port ScanHacking
2Port ScanSSH
1HackingBrute-Force
1Port ScanHackingBrute-ForceSSH
1Port ScanBrute-ForceSSH
...
3reputation reported
3uncategorized
1abuse reported
1Email Spam
from 59 distinct reporters
and 9 distinct sources : BadIPs.com, Blocklist.de, blocklist.net.ua, FireHOL, GreenSnow.co, Charles Haley, VoIPBL.org, darklist.de, AbuseIPDB
106.13.56.204 was first signaled at 2019-08-20 17:20 and last record was at 2020-08-03 12:51.
IP

106.13.56.204

Localisation
China
Beijing, Beijing
NetRange : First & Last IP
106.12.0.0 - 106.13.255.255
Network CIDR
106.12.0.0/15

Cybercrime IP Feeds

Date UTC Category Sub Categories Source List Source Logs
2020-08-01 11:09 attacks Brute-ForceSSH AbuseIPDB 2020-08-01T20:00:33.568272abusebot-2.cloudsearch.cf sshd[30541]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rho
2020-08-01 10:19 attacks Brute-ForceSSH AbuseIPDB  
2020-08-01 05:55 attacks Brute-ForceSSH AbuseIPDB Aug 1 16:49:15 piServer sshd[12254]: Failed password for root from 106.13.56.204 port 60582 ssh2 Aug 1 16:51:24 piServer sshd[12408]: Failed password
2020-08-01 05:36 attacks Brute-ForceSSH AbuseIPDB Aug 1 16:28:14 piServer sshd[10187]: Failed password for root from 106.13.56.204 port 42056 ssh2 Aug 1 16:30:25 piServer sshd[10324]: Failed password
2020-08-01 05:17 attacks Brute-ForceSSH AbuseIPDB Aug 1 16:11:11 piServer sshd[8723]: Failed password for root from 106.13.56.204 port 49764 ssh2 Aug 1 16:13:20 piServer sshd[8874]: Failed password fo
2020-08-01 04:52 attacks Brute-ForceSSH AbuseIPDB Aug 1 15:46:16 piServer sshd[6508]: Failed password for root from 106.13.56.204 port 33080 ssh2 Aug 1 15:50:31 piServer sshd[6891]: Failed password fo
2020-08-01 04:35 attacks Brute-ForceSSH AbuseIPDB Aug 1 15:31:47 piServer sshd[5221]: Failed password for root from 106.13.56.204 port 53910 ssh2 Aug 1 15:33:52 piServer sshd[5457]: Failed password fo
2020-08-01 04:19 attacks Brute-ForceSSH AbuseIPDB Aug 1 15:11:44 piServer sshd[3523]: Failed password for root from 106.13.56.204 port 35372 ssh2 Aug 1 15:17:45 piServer sshd[4061]: Failed password fo
2020-08-01 04:01 attacks Brute-ForceSSH AbuseIPDB Aug 1 14:57:45 piServer sshd[2278]: Failed password for root from 106.13.56.204 port 56262 ssh2 Aug 1 14:59:39 piServer sshd[2433]: Failed password fo
2020-08-01 03:40 attacks Brute-ForceSSH AbuseIPDB Aug 1 14:34:33 piServer sshd[32535]: Failed password for root from 106.13.56.204 port 39612 ssh2 Aug 1 14:38:28 piServer sshd[414]: Failed password fo
2020-07-31 21:45 attacks Port Scan AbuseIPDB " "
2020-07-31 21:30 attacks Port Scan AbuseIPDB firewall-block, port(s): 18309/tcp
2020-07-31 16:16 attacks Brute-ForceSSH AbuseIPDB Jul 31 21:55:30 ws24vmsma01 sshd[65005]: Failed password for root from 106.13.56.204 port 33630 ssh2 Jul 31 22:16:26 ws24vmsma01 sshd[161696]: Failed
2020-07-31 13:39 attacks Port Scan AbuseIPDB <SCAN PORTS> TCP (SYN) 106.13.56.204:44011 -> port 18309, len 44
2020-07-31 12:01 attacks HackingBrute-Force AbuseIPDB Fail2Ban Ban Triggered
2020-07-31 10:39 attacks Port Scan AbuseIPDB <SCAN PORTS> TCP (SYN) 106.13.56.204:59559 -> port 11788, len 44
2020-07-30 22:21 attacks Brute-ForceSSH AbuseIPDB [SID2] Fail2ban detected 5 failed SSH login attempts within 30 minutes. This report was submitted automatically.
2020-07-30 19:53 attacks Brute-ForceSSH AbuseIPDB Jul 31 09:49:06 gw1 sshd[17235]: Failed password for root from 106.13.56.204 port 49644 ssh2
2020-07-30 19:27 attacks Brute-ForceSSH AbuseIPDB Jul 31 09:19:41 gw1 sshd[16074]: Failed password for root from 106.13.56.204 port 56970 ssh2
2020-07-30 19:07 attacks Brute-ForceSSH AbuseIPDB Jul 31 09:03:33 gw1 sshd[15478]: Failed password for root from 106.13.56.204 port 44982 ssh2
2020-07-30 18:22 attacks Brute-ForceSSH AbuseIPDB Jul 31 08:18:05 gw1 sshd[14122]: Failed password for root from 106.13.56.204 port 40306 ssh2
2020-07-30 18:05 attacks Brute-ForceSSH AbuseIPDB Jul 31 07:56:52 gw1 sshd[13518]: Failed password for root from 106.13.56.204 port 53558 ssh2
2020-07-30 17:40 attacks Brute-ForceSSH AbuseIPDB Jul 31 07:35:44 gw1 sshd[12913]: Failed password for root from 106.13.56.204 port 38604 ssh2
2020-07-30 16:54 attacks Brute-ForceSSH AbuseIPDB Jul 31 03:53:30 ns381471 sshd[12427]: Failed password for root from 106.13.56.204 port 60268 ssh2
2020-07-30 16:23 attacks Brute-ForceSSH AbuseIPDB Jul 31 03:22:04 ns381471 sshd[11067]: Failed password for root from 106.13.56.204 port 45278 ssh2
2020-07-30 15:50 attacks Brute-ForceSSH AbuseIPDB Jul 31 02:48:50 ns381471 sshd[9506]: Failed password for root from 106.13.56.204 port 41452 ssh2
2020-07-30 15:18 attacks Brute-ForceSSH AbuseIPDB Jul 31 02:17:28 ns381471 sshd[7841]: Failed password for root from 106.13.56.204 port 37728 ssh2
2020-07-30 14:46 attacks Brute-ForceSSH AbuseIPDB Jul 31 01:43:50 ns381471 sshd[6239]: Failed password for root from 106.13.56.204 port 36680 ssh2
2020-07-30 14:13 attacks Brute-ForceSSH AbuseIPDB Jul 31 01:08:31 ns381471 sshd[4162]: Failed password for root from 106.13.56.204 port 55280 ssh2
2020-07-29 21:40 attacks Brute-ForceSSH AbuseIPDB Jul 30 08:40:30 [host] sshd[16283]: Invalid user p Jul 30 08:40:30 [host] sshd[16283]: pam_unix(sshd: Jul 30 08:40:32 [host] sshd[16283]: Failed passw
2020-07-29 21:08 attacks Brute-ForceSSH AbuseIPDB Jul 30 08:08:42 [host] sshd[14712]: Invalid user h Jul 30 08:08:42 [host] sshd[14712]: pam_unix(sshd: Jul 30 08:08:44 [host] sshd[14712]: Failed passw
2020-07-29 20:50 attacks Port Scan AbuseIPDB Port scan denied
2020-07-29 20:37 attacks Brute-ForceSSH AbuseIPDB Jul 30 07:37:04 [host] sshd[13509]: Invalid user e Jul 30 07:37:04 [host] sshd[13509]: pam_unix(sshd: Jul 30 07:37:06 [host] sshd[13509]: Failed passw
2020-07-29 20:10 attacks Brute-ForceSSH AbuseIPDB SSH invalid-user multiple login try
2020-07-29 20:05 attacks Brute-ForceSSH AbuseIPDB Jul 30 07:05:24 [host] sshd[12392]: Invalid user s Jul 30 07:05:24 [host] sshd[12392]: pam_unix(sshd: Jul 30 07:05:26 [host] sshd[12392]: Failed passw
2020-07-29 20:01 attacks Brute-ForceSSH AbuseIPDB Jul 30 06:39:12 dev0-dcde-rnet sshd[15591]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.56.204 Jul
2020-07-29 19:32 attacks Brute-ForceSSH AbuseIPDB Jul 30 06:32:31 [host] sshd[11208]: Invalid user q Jul 30 06:32:31 [host] sshd[11208]: pam_unix(sshd: Jul 30 06:32:33 [host] sshd[11208]: Failed passw
2020-07-29 12:57 attacks Brute-ForceSSH AbuseIPDB Bruteforce detected by fail2ban
2020-07-29 00:41 attacks Brute-ForceSSH AbuseIPDB Jul 29 11:41:41 host sshd[4527]: Invalid user naomi from 106.13.56.204 port 36234
2020-07-28 22:39 attacks Port ScanSSH AbuseIPDB <SCAN PORTS> TCP (SYN) 106.13.56.204:48147 -> port 31734, len 44
2020-07-28 20:56 attacks Brute-ForceSSH AbuseIPDB (sshd) Failed SSH login from 106.13.56.204 (CN/China/-): 5 in the last 3600 secs
2020-07-28 20:36 attacks Port ScanHackingBrute-ForceSSH AbuseIPDB SSH Brute-Force. Ports scanning.
2020-07-28 20:24 attacks Port Scan AbuseIPDB " "
2020-07-28 17:39 attacks Port ScanSSH AbuseIPDB <SCAN PORTS> TCP (SYN) 106.13.56.204:48147 -> port 31734, len 44
2020-07-28 16:59 attacks SSH AbuseIPDB Connection to SSH Honeypot - Detected by HoneypotDB
2020-07-28 15:49 attacks Brute-ForceSSH AbuseIPDB Invalid user adminrig from 106.13.56.204 port 43162
2020-07-28 05:39 attacks Port ScanBrute-ForceSSH AbuseIPDB <SCAN PORTS> TCP (SYN) 106.13.56.204:49955 -> port 10020, len 44
2020-07-28 04:21 attacks Port Scan AbuseIPDB Jul 28 15:21:33 debian-2gb-nbg1-2 kernel: \[18200994.126558\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=106.13.56.2
2020-07-28 02:39 attacks Brute-ForceSSH AbuseIPDB Failed password for invalid user sako from 106.13.56.204 port 37178 ssh2
2020-07-27 21:39 attacks Port Scan AbuseIPDB Port scan denied
2020-05-02 00:41 attacks FTP Brute-ForceHacking AbuseIPDB May 2 05:12:26 cumulus sshd[3894]: Invalid user zym from 106.13.56.204 port 39782 May 2 05:12:26 cumulus sshd[3894]: pam_unix(sshd:auth): authenticati
2020-05-02 03:42 attacks FTP Brute-ForceHacking AbuseIPDB May 2 05:12:26 cumulus sshd[3894]: Invalid user zym from 106.13.56.204 port 39782 May 2 05:12:26 cumulus sshd[3894]: pam_unix(sshd:auth): authenticati
2020-05-02 10:23 attacks FTP Brute-ForceHacking AbuseIPDB May 2 05:12:26 cumulus sshd[3894]: Invalid user zym from 106.13.56.204 port 39782 May 2 05:12:26 cumulus sshd[3894]: pam_unix(sshd:auth): authenticati
2020-05-02 11:06 attacks FTP Brute-ForceHacking AbuseIPDB May 2 05:12:26 cumulus sshd[3894]: Invalid user zym from 106.13.56.204 port 39782 May 2 05:12:26 cumulus sshd[3894]: pam_unix(sshd:auth): authenticati
2020-05-02 11:24 attacks FTP Brute-ForceHacking AbuseIPDB May 2 05:12:26 cumulus sshd[3894]: Invalid user zym from 106.13.56.204 port 39782 May 2 05:12:26 cumulus sshd[3894]: pam_unix(sshd:auth): authenticati
2020-05-02 11:45 attacks FTP Brute-ForceHacking AbuseIPDB May 2 05:12:26 cumulus sshd[3894]: Invalid user zym from 106.13.56.204 port 39782 May 2 05:12:26 cumulus sshd[3894]: pam_unix(sshd:auth): authenticati
2020-05-02 12:05 attacks FTP Brute-ForceHacking AbuseIPDB May 2 05:12:26 cumulus sshd[3894]: Invalid user zym from 106.13.56.204 port 39782 May 2 05:12:26 cumulus sshd[3894]: pam_unix(sshd:auth): authenticati
2020-05-02 12:24 attacks FTP Brute-ForceHacking AbuseIPDB May 2 05:12:26 cumulus sshd[3894]: Invalid user zym from 106.13.56.204 port 39782 May 2 05:12:26 cumulus sshd[3894]: pam_unix(sshd:auth): authenticati
2020-05-02 13:06 attacks FTP Brute-ForceHacking AbuseIPDB May 2 05:12:26 cumulus sshd[3894]: Invalid user zym from 106.13.56.204 port 39782 May 2 05:12:26 cumulus sshd[3894]: pam_unix(sshd:auth): authenticati
2020-05-02 16:23 attacks FTP Brute-ForceHacking AbuseIPDB May 2 05:12:26 cumulus sshd[3894]: Invalid user zym from 106.13.56.204 port 39782 May 2 05:12:26 cumulus sshd[3894]: pam_unix(sshd:auth): authenticati
2020-07-31 15:54 reputation alienvault_reputation  
2020-07-31 15:56 attacks bi_any_0_1d BadIPs.com  
2020-07-31 15:56 attacks SSH bi_sshd_0_1d BadIPs.com  
2020-07-31 15:57 attacks SSH bi_ssh_0_1d BadIPs.com  
2020-07-31 15:57 attacks blocklist_de Blocklist.de  
2020-07-31 15:57 attacks SSH blocklist_de_ssh Blocklist.de  
2020-07-31 15:57 abuse Email Spam blocklist_net_ua blocklist.net.ua  
2020-07-31 15:58 reputation ciarmy  
2020-07-31 16:01 attacks firehol_level2 FireHOL  
2020-07-31 16:02 attacks firehol_level3 FireHOL  
2020-07-31 16:02 attacks firehol_level4 FireHOL  
2020-07-31 16:10 attacks greensnow GreenSnow.co  
2020-07-31 16:10 attacks SSH haley_ssh Charles Haley  
2020-07-31 16:11 reputation iblocklist_ciarmy_malicious  
2020-07-31 16:24 attacks Fraud VoIP voipbl VoIPBL.org  
2020-08-01 14:55 attacks Bad Web Bot bi_badbots_0_1d BadIPs.com  
2020-08-01 14:55 attacks Brute-Force bi_bruteforce_0_1d BadIPs.com  
2020-08-03 12:51 attacks SSH bi_ssh-ddos_0_1d BadIPs.com  
2019-09-03 03:47 attacks darklist_de darklist.de  
2019-08-20 17:20 attacks darklist_de darklist.de  
only last 50 and first 10 AbuseIPDB logs are shown

Threats Categories :

abuse
IPs used to spam forum, boards, blogs or smtp servers, automated web scripts or scrappers (bad bots)
anonymizer
Onion Router IP addresses. TOR network IPs, TOR exit points, socks or ssl proxy.
attacks
bruteforce ssh/ftp/system account, IPs that have been detected by fail2ban, ports scan, vulnerabilities scan, DDoS.
malware
Addresses that have been identified distributing malware, form-grabber and stealer, Viruses, Worms, Trojans, Ransomware, Adware, Spyware

Whois

inetnum: 106.12.0.0 - 106.13.255.255
netname: Baidu
descr: Beijing Baidu Netcom Science and Technology Co., Ltd.
descr: Baidu Plaza, No.10, Shangdi 10th street,
descr: Haidian District Beijing,100080
admin-c: SD753-AP
tech-c: SD753-AP
country: CN
mnt-by: MAINT-CNNIC-AP
mnt-lower: MAINT-CNNIC-AP
mnt-irt: IRT-CNNIC-CN
mnt-routes: MAINT-CNNIC-AP
status: ALLOCATED PORTABLE
last-modified: 2015-01-28T09:58:01Z
source: APNIC

irt: IRT-CNNIC-CN
address: Beijing, China
e-mail: ipas@cnnic.cn
abuse-mailbox: ipas@cnnic.cn
admin-c: IP50-AP
tech-c: IP50-AP
auth: # Filtered
remarks: Please note that CNNIC is not an ISP and is not
remarks: empowered to investigate complaints of network abuse.
remarks: Please contact the tech-c or admin-c of the network.
mnt-by: MAINT-CNNIC-AP
last-modified: 2017-11-01T08:57:39Z
source: APNIC

person: Supeng Deng
nic-hdl: SD753-AP
address: No.6 2nd North Street Haidian District Beijing
country: CN
phone: +86-10-58003402
fax-no: +86-10-58003402
e-mail: zhangyukun@baidu.com
mnt-by: MAINT-CNNIC-AP
last-modified: 2016-11-01T08:04:01Z
source: APNIC

route: 106.13.0.0/18
descr: Baidu
country: CN
origin: AS38365
notify: zhangyukun@baidu.com
mnt-by: MAINT-CNNIC-AP
last-modified: 2018-11-14T23:46:02Z
source: APNIC

route: 106.13.0.0/18
descr: Baidu
country: CN
origin: AS55967
notify: zhangyukun@baidu.com
mnt-by: MAINT-CNNIC-AP
last-modified: 2018-11-14T23:46:02Z
source: APNIC
most specific ip range is highlighted
Updated : 2020-08-02