ABUSE.MOM
THREAT REPORT

IP Threat Report
172.59.216.165

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 06:57:35
First seen: 2026-03-22 13:00:06
Last seen: 2026-03-24 04:00:06
103

⛔ Verdict: BLOCK

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

DANGER_PATHMETHOD
01

Geolocation & Classification

IP Address
172.59.216.165
Type
Mobile
Country
🇺🇸 United States
City
Elizabeth
ISP
T-Mobile USA, Inc.
Organization
T-Mobile USA, Inc.
Autonomous System
AS21928 T-Mobile USA, Inc.
Hit Count
2
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger medium hits: 2Medium-risk: admin panels, config files+20
POST requests presentBehavioral anomaly detected by automated analysis+8
Σ = 103
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-03-22 13:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 3 (+75), Danger medium hits: 2 (+20), POST requests present (+8)
2026-03-24 04:00:06
Last malicious request observed
Total score reached: 103/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

T-Mobile USA, Inc.
AS21928 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 172.59.216.165 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

⚙️ General Security

Add 172.59.216.165 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.

09

Blacklist Status (DNSBL)

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

✓ Clean
ix.dnsbl.manitu.net
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net

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

10

Threat Analysis

172.59.216.165 has been assigned a threat score of 103/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

📊 Threat Analysis

Our monitoring infrastructure has identified 172.59.216.165, geolocated to Elizabeth, United States, operating on the network of T-Mobile USA, Inc., as a source of suspicious network activity. Over a period of 1 days, this IP generated 2 malicious requests, averaging approximately 2 requests per day. The address belongs to a mobile carrier network. The sustained pattern of malicious requests indicates either a compromised device or deliberate abuse. Our records show 152 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. With a threat score of 103/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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

172.58.117.187 (205)172.56.157.49 (175)172.59.113.219 (140)172.58.130.107 (140)172.56.154.193 (140)View all →
12

Security Intelligence

💡 Server-Side Request Forgery (SSRF)

SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.

💡 Content Delivery Network Risks

CDNs can inadvertently mask the true origin of malicious traffic, making attribution difficult. Attackers abuse CDN services to proxy their attacks, leverage cached content for amplification, and exploit misconfigurations in CDN-to-origin connections.

🔍 Check Any IP Address

Share this report: