Report for IP: 66.181.46.22

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.

This IP was blocked purely based on its country of origin — the site owner has restricted access from this IP's geographic location due to a pattern of unwanted traffic from that region. This does not necessarily mean the specific IP itself has attacked anything; it reflects a blanket country-level policy.

• FireHOL level2 — FireHOL level2 lists addresses seen attacking in the last 48 hours across many sensors. It is large and volatile: addresses enter and leave quickly, so on its own this is weaker, recent-activity evidence.

Only short-lived or context lists match, so this is weak evidence on its own.

This IP requested common backup file paths (.bak, .sql, .zip, wp-config.bak), hunting for database dumps or config files containing plaintext credentials. A single exposed wp-config.bak can hand an attacker full database access. This attack is automated and deliberate.

This IP requested the /.git/ directory, attempting to download source code, commit history, database credentials, and API keys from an accidentally exposed Git repository. Automated tools can reconstruct an entire codebase from an exposed .git folder. No legitimate client ever requests this path.