IP Threat Report
64.64.116.13
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst 32/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 9/2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| Danger medium hits: 47 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger strong hits: 30 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Form spam: no_js_check | Spam/malware keywords in request content | +0 | |
| UA bot: Go-http-client | Known bot/crawler User-Agent detected | +40 | |
| UA changed | Multiple User-Agents — bot rotation technique | +25 | |
| UA suspicious | Behavioral anomaly detected by automated analysis | +15 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
Recommendations
Actions taken & recommended
- IP 64.64.116.13 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Other malicious IPs detected in the same /24 subnet — consider blocking 64.64.116.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🔎 Path Enumeration Protection
Block scanning from 64.64.116.13: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🌊 Traffic Flood Defense
IP 64.64.116.13 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
📧 Spam Protection
Enable CAPTCHA on all public forms. Add honeypot fields. Rate-limit submissions to 3 per minute per IP. Deploy Akismet or CleanTalk.
🤖 Bot Detection
Address UA spoofing from 64.64.116.13: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
Neighbors in 64.64.116.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Blacklist Status (DNSBL)
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
Threat Analysis
64.64.116.13 has been assigned a threat score of 330/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.
The following attack categories were identified:
📊 Threat Analysis
The address 64.64.116.13 originates from Chicago, United States, operating on the network of LogicWeb Inc. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 224 malicious requests from this address across a 46-day span, reflecting a sustained attack cadence of ~4.9 requests per day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. United States currently accounts for 222 blocked IPs in our database, making it a significant source of malicious traffic. At 330/100, this is an extremely high-risk address. All traffic should be considered hostile.
This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.
Related Threats
🇺🇸 Top threats from United States
104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →🏢 Same network: AS262287
64.64.116.14 (305)64.64.116.12 (305)64.64.116.4 (305)64.64.116.16 (305)View all →Security Intelligence
💡 DDoS Mitigation Approaches
Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.
💡 Memory Safety and Buffer Overflows
Buffer overflow vulnerabilities remain relevant in C/C++ applications despite decades of mitigation efforts. Modern protections like ASLR, stack canaries, and DEP reduce exploitability but determined attackers continue finding bypass techniques.