Report for IP: 169.40.142.202

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 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.

• 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 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.

This IP probed a debug or admin endpoint from a non-WordPress stack — Spring Boot's actuator, Go's pprof, Symfony's profiler, a Vite dev-server file read, or similar. None of these exist on a WordPress install; the request is a blind, automated sweep fingerprinting whatever stack happens to answer.

This request's User-Agent self-identified as an automated vulnerability scanner or security-research bot (rather than a browser). Genuine security researchers and monitoring tools that announce themselves this way are still uninvited probing from this site's point of view — the traffic is automated reconnaissance, not a human visitor.