ABUSE.MOM
THREAT REPORT

IP Threat Report
216.24.210.115

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:20:10
First seen: 2026-05-24 03:30:59
Last seen: 2026-05-24 09:50:59
255

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHUA_CHANGED
01

Geolocation & Classification

IP Address
216.24.210.115
Type
Hosting
Country
🇺🇸 United States
City
Los Angeles
ISP
Ipxo LLC
Organization
Unknown
Autonomous System
AS62240 Clouvider
Hit Count
12
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 13/2sAbnormally fast request rate — automated scanning+35
Burst 45/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 969Medium-risk: admin panels, config files+60
Danger strong hits: 372High-risk paths: shells, RCE vectors, exploits+100
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 255
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-05-24 03:30:59
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 13/2s (+35), Burst 45/10s (+35), Danger medium hits: 969 (+60)
2026-05-24 09:50:59
Last malicious request observed
Total score reached: 255/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Ipxo LLC
AS62240 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 216.24.210.115 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 216.24.210.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 216.24.210.115.

🤖 Bot Detection

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

07

Neighbors in 216.24.210.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
zen.spamhaus.org
✓ Clean
cbl.abuseat.org
✓ Clean
bl.spamcop.net
✓ Clean
psbl.surriel.com
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
bl.blocklist.de
✓ Clean
b.barracudacentral.org
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

216.24.210.115 has been assigned a threat score of 255/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

The address 216.24.210.115 originates from Los Angeles, United States, operating on the network of Ipxo LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 12 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~12 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The dual attack vectors of Request Flooding combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. United States currently accounts for 213 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 255/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

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

92.119.36.49 (330)45.147.244.27 (313)45.131.195.77 (305)98.159.37.212 (305)92.119.36.41 (305)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.

💡 False Positive Management

False positives erode trust in security systems and waste analyst resources. Effective management requires feedback loops, allowlisting mechanisms, contextual analysis, and regular tuning of detection rules based on operational experience.

🔍 Check Any IP Address

Share this report: