ABUSE.MOM
THREAT REPORT

IP Threat Report
88.218.173.13

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 02:04:07
First seen: 2026-03-16 06:00:06
Last seen: 2026-03-16 06:00:06
70

⛔ Verdict: BLOCK

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

BURST
01

Geolocation & Classification

IP Address
88.218.173.13
Type
Residential
Country
🇺🇸 United States
City
New York
ISP
GTT Communications Inc.
Organization
ISP4Life INC
Autonomous System
AS3257 GTT Communications Inc.
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst: 13 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 13 req / 10sAbnormally fast request rate — automated scanning+35
Σ = 70
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-16 06:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst: 13 req / 2s (+35), Burst: 13 req / 10s (+35)
2026-03-16 06:00:06
Last malicious request observed
Total score reached: 70/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

GTT Communications Inc.
AS3257 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 88.218.173.13 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 88.218.173.0/24
  • 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 88.218.173.13.

07

Neighbors in 88.218.173.0/24

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

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (2)
PortServiceRiskDescription
29840UnknownLowService on port 29840
29842UnknownLowService on port 29842

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

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
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
zen.spamhaus.org
✓ Clean
psbl.surriel.com
✓ Clean
truncate.gbudb.net
✓ Clean
b.barracudacentral.org

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

10

Threat Analysis

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

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

The address 88.218.173.13 originates from New York, United States, operating on the network of GTT Communications Inc.. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 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. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. United States currently accounts for 21 blocked IPs in our database, making it a notable source of malicious traffic. At 70/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

64.57.129.39 (130)45.41.174.207 (130)134.195.153.64 (105)45.41.166.41 (105)207.97.130.53 (105)View all →

🏢 Same network: AS3257

64.57.129.39 (130)45.41.174.207 (130)134.195.153.64 (105)45.41.166.41 (105)207.97.130.53 (105)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.

💡 Web Application Firewall Strategies

WAFs inspect HTTP traffic to block common attacks but require careful tuning. Overly aggressive rules cause false positives while permissive configurations miss attacks. Modern WAFs combine signature matching with behavioral analysis and machine learning.

🔍 Check Any IP Address

Share this report: