ABUSE.MOM
THREAT REPORT

IP Threat Report
170.106.136.181

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-05 04:54:38
First seen: 2026-06-03 11:04:27
Last seen: 2026-07-05 04:01:46
95

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 95/100. Total malicious requests observed: 1160.

DANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
170.106.136.181
Type
Unknown
Country
🇺🇸 United States
City
Santa Clara
ISP
Tencent Cloud Computing (Beijing) Co
Organization
Tencent Cloud Computing (Beijing) Co
Autonomous System
Unknown
Hit Count
1160
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger medium hits: 3Medium-risk: admin panels, config files+30
Directory ScanBehavioral anomaly detected by automated analysis+0
Foreign refererReferer from unrelated external domain+10
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 75
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-06-03 11:04:27
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger medium hits: 3 (+30), Directory Scan
2026-07-05 04:01:46
Last malicious request observed
Total score reached: 95/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 170.106.136.181 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Directory Scan Defense

IP 170.106.136.181 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
bl.spamcop.net
✓ Clean
dnsbl.dronebl.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
psbl.surriel.com
✓ Clean
bl.blocklist.de

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

170.106.136.181 has been assigned a threat score of 95/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

Our monitoring infrastructure has identified 170.106.136.181, geolocated to Santa Clara, United States, operating on the network of Tencent Cloud Computing (Beijing) Co, as a source of suspicious network activity. During its 31-day observation window, we recorded 1,160 hostile requests from this IP — roughly 37.4 per day on average. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 101 flagged addresses, United States represents a significant presence in our threat database. At 95/100, this is an extremely high-risk address. All traffic should be considered hostile.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)103.215.74.213 (340)103.168.66.237 (340)34.187.158.4 (340)34.186.187.208 (340)View all →
12

Security Intelligence

💡 WordPress-Specific Attack Vectors

WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.

💡 Web Cache Poisoning Attacks

Cache poisoning manipulates web cache behavior to serve malicious content to other users. By identifying unkeyed inputs that influence cached responses, attackers can inject JavaScript, redirect users, or cause denial of service at scale through the cache infrastructure.

🔍 Check Any IP Address

Share this report: