ABUSE.MOM
THREAT REPORT

IP Threat Report
172.98.32.182

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 06:06:06
First seen: 2026-04-24 03:00:06
Last seen: 2026-04-24 03:00:06
75

⛔ Verdict: BLOCK

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

UA_SUSDANGER_PATH
01

Geolocation & Classification

IP Address
172.98.32.182
Type
Residential
Country
🇺🇸 United States
City
Washington
ISP
LayerSwitch
Organization
Prefixx, Inc
Autonomous System
AS206092 F.N.S. HOLDINGS LIMITED
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA suspicious (short/empty)Behavioral anomaly detected by automated analysis+15
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger medium hits: 1Medium-risk: admin panels, config files+10
Σ = 75
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-04-24 03:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA suspicious (short/empty) (+15), Danger strong hits: 2 (+50), Danger medium hits: 1 (+10)
2026-04-24 03:00:06
Last malicious request observed
Total score reached: 75/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

LayerSwitch
AS206092 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 172.98.32.182 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.32.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.32.182: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

Neighbors in 172.98.32.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
dnsbl.sorbs.net
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
zen.spamhaus.org
✓ 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.32.182 has been assigned a threat score of 75/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.

The following attack categories were identified:

User-Agent Anomaly

📊 Threat Analysis

IP address 172.98.32.182 has been traced to Washington, United States, operating on the network of LayerSwitch. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 1 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~1 requests per day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. The IP exhibits User-Agent manipulation, switching between different browser identities or sending empty headers. Our records show 150 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. At 75/100, this IP warrants immediate defensive action.

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

103.163.220.216 (340)85.203.21.101 (320)85.203.21.157 (310)85.203.21.172 (305)91.217.249.222 (305)View all →
12

Security Intelligence

💡 HTTP Header Analysis for Threat Detection

Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.

💡 DNS Sinkholing for Malware Defense

DNS sinkholing redirects queries for known malicious domains to controlled IP addresses. This technique blocks malware communication, prevents data exfiltration, and identifies compromised internal hosts attempting to contact command-and-control servers.

🔍 Check Any IP Address

Share this report: