ABUSE.MOM
THREAT REPORT

IP Threat Report
172.58.245.81

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-26 15:45:31
First seen: 2026-05-29 07:08:54
Last seen: 2026-06-26 02:52:49
60

⛔ Verdict: BLOCK

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

01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Directory ScanBehavioral anomaly detected by automated analysis+0
Σ = 0
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-05-29 07:08:54
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Directory Scan
2026-06-26 02:52:49
Last malicious request observed
Total score reached: 60/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.58.245.81 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

⚙️ Defensive Recommendations

Block 172.58.245.81 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.

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
zen.spamhaus.org
✓ Clean
psbl.surriel.com
✓ Clean
dnsbl.dronebl.org
✓ Clean
bl.blocklist.de
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
cbl.abuseat.org
✓ Clean
b.barracudacentral.org

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

10

Threat Analysis

172.58.245.81 has been assigned a threat score of 60/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.

📊 Threat Analysis

172.58.245.81 is registered in Washington, United States, operating on the network of T-Mobile USA, Inc.. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 27 days, this IP generated 132 malicious requests, averaging approximately 4.9 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. With 36,332 flagged addresses, United States represents a major presence in our threat database. At 60/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.

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

💡 Edge Computing Attack Surface

Edge computing pushes processing closer to users but expands the attack surface. Edge nodes often run in less secure environments than centralized data centers, creating new opportunities for physical access attacks and supply chain compromises.

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