ABUSE.MOM
THREAT REPORT

IP Threat Report
172.56.32.105

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 06:57:35
First seen: 2026-03-07 04:00:06
Last seen: 2026-03-07 04:00:06
90

⛔ Verdict: BLOCK

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

DANGER_PATHBURSTREFERER
01

Geolocation & Classification

IP Address
172.56.32.105
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
2
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 1Medium-risk: admin panels, config files+10
Burst: 20 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 20 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Σ = 90
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-03-07 04:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 1 (+10), Burst: 20 req / 2s (+35), Burst: 20 req / 10s (+35)
2026-03-07 04:00:06
Last malicious request observed
Total score reached: 90/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.56.32.105 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.56.32.105.

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

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

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

Our monitoring infrastructure has identified 172.56.32.105, geolocated to Washington, United States, operating on the network of T-Mobile USA, Inc., as a source of suspicious network activity. Our sensors captured 2 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~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. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. With 152 flagged addresses, United States represents a significant presence in our threat database. With a threat score of 90/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.

💡 Directory Traversal Attacks

Path traversal attacks attempt to access files outside the intended directory by manipulating file path references. Attackers use sequences like ../ to reach sensitive system files such as /etc/passwd or application configuration files.

🔍 Check Any IP Address

Share this report: