WP Beacon
Critical code_pattern
Resolved · tencent_doh_public_dns_explicit_curl_fix
2026-05-08 09:56:56 (1mo ago)
| Slug | safly-curl-patch |
|---|---|
| Pattern | hardcoded_ip_url |
| Kind | builtin |
| Version | 1.0.0 |
| Hit count | 1 |
| First hit |
|
| Explanation | plugin source hardcodes a raw IPv4 URL (e.g. `https://94.156.79.8/...`) — legitimate plugins use DNS hostnames because IPs change. Hardcoded IPs in plugin code are almost always either dev leftovers or attacker C2 infrastructure. The June 2024 social-warfare keylogger (audit #14) used `https://94.156.79.8/sc-top.js` for the JS payload host, `/AddSites` for victim registration, `/CMSUsers` for filesystem-recon exfil. Operator infrastructure on raw IPs avoids domain registration / RDAP detection paths. Post-filtered to skip RFC1918/loopback/link-local ranges and `vendor/`/`tests/` paths. |
View raw JSON
{
"slug": "safly-curl-patch",
"pattern": "hardcoded_ip_url",
"kind": "builtin",
"version": "1.0.0",
"hit_count": 1,
"first_hit": {
"file": "SaFly-Curl-Patch.php",
"line": 70,
"snippet": "$ip = wp_remote_retrieve_body(wp_remote_get('http://119.29.29.29/d?dn=' . $domain));"
},
"explanation": "plugin source hardcodes a raw IPv4 URL (e.g. `https://94.156.79.8/...`) \u2014 legitimate plugins use DNS hostnames because IPs change. Hardcoded IPs in plugin code are almost always either dev leftovers or attacker C2 infrastructure. The June 2024 social-warfare keylogger (audit #14) used `https://94.156.79.8/sc-top.js` for the JS payload host, `/AddSites` for victim registration, `/CMSUsers` for filesystem-recon exfil. Operator infrastructure on raw IPs avoids domain registration / RDAP detection paths. Post-filtered to skip RFC1918/loopback/link-local ranges and `vendor/`/`tests/` paths."
}