ABUSE.MOM
THREAT REPORT

IP Threat Report
172.59.106.198

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-26 07:47:34
First seen: 2026-08-10 07:22:27
Last seen: 2026-08-16 01:01:23
80

⛔ Verdict: BLOCK

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

BURSTREFERER
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 14/2sAbnormally fast request rate — automated scanning+35
Burst 16/10sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
Σ = 80
03

Observed Activity

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

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

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

04

Timeline

2026-08-10 07:22:27
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 14/2s (+35), Burst 16/10s (+35), Foreign referer (+10)
2026-08-16 01:01:23
Last malicious request observed
Total score reached: 80/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

We have detected 92 malicious IPs from this autonomous system.

View all IPs from AS21928 →
06

Recommendations

Actions taken & recommended

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

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 172.59.106.198.

09

Blacklist Status (DNSBL)

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

✓ Clean
zen.spamhaus.org
✓ Clean
bl.blocklist.de
✓ Clean
cbl.abuseat.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
dnsbl.dronebl.org
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

172.59.106.198 has been assigned a threat score of 80/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

Network traffic from 172.59.106.198, located in Milwaukee, United States, operating on the network of T-Mobile USA, Inc., has been classified as malicious by our automated threat scoring engine. Over a period of 5 days, this IP generated 221 malicious requests, averaging approximately 44.2 requests per day. This is a mobile network IP. While mobile addresses are typically shared via CGNAT, persistent malicious activity from this specific address suggests automated abuse. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. With 36,319 flagged addresses, United States represents a major presence in our threat database. At 80/100, this IP warrants immediate defensive action.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.214.122 (350)216.73.160.52 (350)34.187.158.4 (340)34.186.187.208 (340)View all →

🏢 Same network: AS21928

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

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.

💡 Responsible Disclosure Ethics

Responsible disclosure balances public safety with giving vendors time to patch vulnerabilities. The security community generally supports coordinated disclosure timelines, but disagreements about appropriate timeframes and full disclosure continue to drive policy debates.

🔍 Check Any IP Address

Share this report: