Report for IP: 188.165.193.125

This IP was blocked attempting to log into a WordPress site's wp-login.php — either from a disallowed country or after exceeding the allowed number of failed login attempts. Automated credential-stuffing and brute-force tools account for the overwhelming majority of this traffic; legitimate users rarely trigger a hard IP block on login alone.

This IP generated over 20 HTTP 4xx errors in 60 seconds using a User-Agent identified as a bad bot (scraper, headless browser, or attack proxy). The high error rate indicates automated probing for vulnerabilities while trying to appear as generic traffic. Legitimate services respect robots.txt and do not flood servers with errors.

• This site (WordPress attackers, 90 days) — This site's own data: an IP that attacked WordPress sites and was reported here within the last 90 days. Independent of the third-party lists above.

A single community list matches, so treat this as moderate evidence.

This IP rapidly probed multiple non-existent PHP paths in under 60 seconds — a hallmark of automated webshell scanning tools hunting for previously uploaded backdoors or vulnerable file-upload endpoints. If successful, a webshell grants the attacker full remote code execution on the server.

This IP attempted the "wp2shell" exploit chain (CVE-2026-63030 / CVE-2026-60137) — a WordPress core REST API vulnerability where the /batch/v1 endpoint's route dispatch can be confused into bypassing authentication, then chained with a SQL injection for unauthenticated remote code execution. Publicly weaponized since July 2026 with automated exploit toolkits circulating on GitHub. Patched in WordPress core 7.0.2 and 6.9.5 — any unpatched site remains fully exposed to this pre-auth RCE.