ABUSE.MOM
THREAT REPORT

IP Threat Report
170.106.101.170

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 16:14:17
First seen: 2026-02-19 21:35:05
Last seen: 2026-03-04 17:00:05
160

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEUA_CHANGED
01

Geolocation & Classification

IP Address
170.106.101.170
Type
Hosting
Country
🇺🇸 United States
City
Santa Clara
ISP
Tencent Cloud Computing (Beijing) Co
Organization
Unknown
Autonomous System
AS132203 Tencent Building, Kejizhongyi Avenue
Hit Count
57
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Σ = 310
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-02-19 21:35:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 2 (+50), 404 ratio 40-60% (+15), Probe pattern 302->404 same path (+20)
2026-03-04 17:00:05
Last malicious request observed
Total score reached: 160/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Tencent Cloud Computing (Beijing) Co
AS132203 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 170.106.101.170 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • 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 170.106.101.170: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🤖 Bot Detection

Address UA spoofing from 170.106.101.170: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

09

Blacklist Status (DNSBL)

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

⛔ LISTED
Spamhaus ZEN

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

10

Threat Analysis

170.106.101.170 has been assigned a threat score of 160/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:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 170.106.101.170 to malicious activity originating from Santa Clara, United States, operating on the network of Tencent Cloud Computing (Beijing) Co. The address has been under observation since its initial detection. Our sensors captured 57 malicious requests from this address across a 12-day span, reflecting a sustained attack cadence of ~4.8 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The dual attack vectors of Path Enumeration combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. Our records show 126 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. At 160/100, this is an extremely high-risk address. All traffic should be considered hostile.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

11

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: AS132203

43.153.215.90 (243)43.135.130.196 (230)43.128.88.177 (183)43.135.108.57 (175)43.167.158.248 (170)View all →
12

Security Intelligence

💡 Remote Code Execution (RCE)

RCE vulnerabilities allow attackers to execute arbitrary code on target servers. These critical flaws often arise from deserialization bugs, template injection, or file upload vulnerabilities, and represent the highest severity class of web application weaknesses.

💡 DNS-Based Threat Detection

Monitoring DNS queries reveals malicious activity including command-and-control communication, data exfiltration through DNS tunneling, and connections to known malicious domains. DNS is often the first indicator of compromise in network forensics.

🔍 Check Any IP Address

Share this report: