JavaScript is disabled. Some features of this site may not work properly. For a smoother experience, please enable JavaScript in your browser settings.

AbuseIPDB » 212.13.190.226

212.13.190.226 was found in our database!

This IP was reported 4 times. Confidence of Abuse is 29%: ?

29%

ISP	JSC Kazakhtelecom
Usage Type	Fixed Line ISP
ASN	AS9198
Hostname(s)	212.13.190.226.dynamic.telecom.kz
Domain Name	telecom.kz
Country	🇰🇿 Kazakhstan
City	Oral, West Kazakhstan

IP info including ISP, Usage Type, and Location provided by IPInfo. Updated weekly.

Report 212.13.190.226

Whois 212.13.190.226

IP Abuse Reports for 212.13.190.226:

This IP address has been reported a total of 4 times from 4 distinct sources. 212.13.190.226 was first reported on October 15th 2026, and the most recent report was 17 hours ago.

Recent Reports: We have received reports of abusive activity from this IP address within the last week. It is potentially still actively engaged in abusive activities.

Reporter	IoA Timestamp (UTC)	Comment	Categories
🇺🇸 Penny Packer	2026-10-22 12:15:28 (17 hours ago)	Fail2Ban apache-tripwires	Web App Attack
🇺🇸 Ben Schoolland	2026-10-20 22:10:29 (2 days ago)	Distributed WordPress credential-stuffing against chalkwild.com. POST /wp-login.php at 20/Oct/2026:1 ... show more Distributed WordPress credential-stuffing against chalkwild.com. POST /wp-login.php at 20/Oct/2026:14:48:53 (HTTP 200 = authentication failed), User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/151.0.0.0 Safari/537.36. This was this IP addresss ONLY request to the host in the entire day - it never fetched the login form (zero GET /wp-login.php), i.e. credentials were submitted blind by a script, not typed by a user. Part of a 99-IP campaign on 2026-10-20: each IP made exactly one login attempt, paced ~6/hour evenly across 19 hours, rotating Chrome 149-152 UA strings, specifically to stay under per-IP rate limits. No login succeeded. show less	Brute-Force Web App Attack
🇫🇷 LRob	2026-10-20 14:09:55 (2 days ago)	Not following 301 redirects — wasted requests \| method: POST \| path: /wp-login.php \| ua: Mozilla/5.0 ... show more Not following 301 redirects — wasted requests \| method: POST \| path: /wp-login.php \| ua: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/152.0.0.0 Safari/537.36 show less	Bad Web Bot
🇺🇸 TPI-Abuse	2026-10-15 07:09:47 (1 week ago)	(mod_security) mod_security (id:225170) triggered by 212.13.190.226 (212.13.190.226.dynamic.telecom. ... show more (mod_security) mod_security (id:225170) triggered by 212.13.190.226 (212.13.190.226.dynamic.telecom.kz): 1 in the last 300 secs; Ports: *; Direction: 1; Trigger: LF_MODSEC; Logs: [Thu Oct 15 03:09:41.362469 2026] [security2:error] [pid 13124:tid 13124] [client 212.13.190.226:45410] ModSecurity: Access denied with code 403 (phase 2). Operator EQ matched 0 at REQUEST_COOKIES_NAMES. [file "/etc/apache2/conf.d/modsec_vendor_configs/comodo_apache/26_Apps_WordPress.conf"] [line "155"] [id "225170"] [rev "3"] [msg "COMODO WAF: Sensitive Information Disclosure Vulnerability in WordPress 4.7 (CVE-2017-5487)\|\|rochesterhistorical.org\|F\|2"] [severity "CRITICAL"] [tag "CWAF"] [tag "WordPress"] [hostname "rochesterhistorical.org"] [uri "/wp-json/wp/v2/users/me"] [unique_id "atB8NfQHjuFTWfWB5AIzsQAAAA4"] show less	Brute-Force Bad Web Bot Web App Attack

Showing 1 to 4 of 4 reports

Think this IP has been falsely reported? You may request to have the associated reports reviewed and removed. Request Takedown 🚩

Recently Reported IPs:

🇺🇸 2601:1c0:4400:b3c6::1d08

🇫🇷 217.182.253.249

🇺🇸 216.26.230.253

🇺🇸 216.25.89.116

🇧🇬 185.9.16.100

🇫🇮 147.185.133.157

🇯🇵 138.3.223.188

🇺🇸 129.121.123.73

🇨🇳 112.26.30.212

🇺🇸 91.230.168.38

🇷🇴 80.94.95.115

🇺🇸 66.132.186.224

🇺🇸 20.118.235.123

🇺🇸 2602:fa59:10:f1::1

🇳🇱 213.177.179.91

🇺🇸 205.210.31.59

🇺🇸 195.184.76.32

🇳🇱 195.178.110.217

🇨🇱 190.171.189.85

🇨🇳 175.165.81.80