ABUSE.MOM
THREAT REPORT

IP Threat Report
172.56.153.155

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-26 08:04:03
First seen: 2026-06-11 06:45:48
Last seen: 2026-06-26 02:52:49
80

⛔ Verdict: BLOCK

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

01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
DDoS / FloodBehavioral 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-06-11 06:45:48
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
DDoS / Flood
2026-06-26 02:52:49
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.56.153.155 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Other malicious IPs detected in the same /24 subnet — consider blocking 172.56.153.0/24
  • 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.56.153.155 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.

07

Neighbors in 172.56.153.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

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
psbl.surriel.com
✓ Clean
cbl.abuseat.org
✓ Clean
zen.spamhaus.org

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

10

Threat Analysis

172.56.153.155 has been assigned a threat score of 80/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

📊 Threat Analysis

Network traffic from 172.56.153.155, located in Upland, United States, operating on the network of T-Mobile USA, Inc., has been classified as malicious by our automated threat scoring engine. The address has been active for 14 days in our monitoring system, producing 218 flagged requests at a rate of ~15.6/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. United States currently accounts for 36,320 blocked IPs in our database, making it a major source of malicious traffic. The score of 80/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.

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.

💡 Server-Side Template Injection

SSTI occurs when user input is embedded in server-side templates without sanitization. Successful exploitation often leads to remote code execution, as template engines typically have access to powerful server-side functionality.

🔍 Check Any IP Address

Share this report: