ABUSE.MOM
THREAT REPORT

IP Threat Report
172.98.33.125

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:22:20
First seen: 2026-05-14 16:00:06
Last seen: 2026-05-14 21:00:06
200

⛔ Verdict: BLOCK

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

BOT_UADANGER_PATH
01

Geolocation & Classification

IP Address
172.98.33.125
Type
Residential
Country
🇺🇸 United States
City
Dallas
ISP
LayerSwitch
Organization
Prefixx, Inc
Autonomous System
AS396356 Latitude.sh
Hit Count
2
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 7Medium-risk: admin panels, config files+60
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger medium hits: 3Medium-risk: admin panels, config files+30
Σ = 305
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-14 16:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: Go-http-client (+40), Danger strong hits: 4 (+100), Danger medium hits: 7 (+60)
2026-05-14 21:00:06
Last malicious request observed
Total score reached: 200/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

LayerSwitch
AS396356 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 172.98.33.125 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.98.33.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🤖 Bot Detection

Address UA spoofing from 172.98.33.125: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

Neighbors in 172.98.33.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.

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

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

10

Threat Analysis

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

The following attack categories were identified:

User-Agent Anomaly

📊 Threat Analysis

Our monitoring infrastructure has identified 172.98.33.125, geolocated to Dallas, United States, operating on the network of LayerSwitch, 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. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. The IP exhibits User-Agent manipulation, switching between different browser identities or sending empty headers. Our records show 222 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. At 200/100, this is an extremely high-risk address. All traffic should be considered hostile.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

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

173.239.224.82 (320)185.223.152.42 (320)185.223.152.45 (320)185.223.152.53 (305)45.132.115.4 (305)View all →
12

Security Intelligence

💡 TLS Fingerprinting (JA3/JA4)

TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.

💡 Privacy-Preserving Threat Detection

Advanced techniques enable threat detection while minimizing privacy impact. Encrypted DNS, differential privacy in analytics, and federated learning for threat models allow effective security monitoring without unnecessary surveillance of legitimate user behavior.

🔍 Check Any IP Address

Share this report: