ABUSE.MOM
THREAT REPORT

IP Threat Report
216.24.210.190

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-21 16:54:32
First seen: 2026-04-19 01:00:08
Last seen: 2026-04-19 01:00:08
195

⛔ Verdict: BLOCK

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

UA_CHANGEDDANGER_PATHBURST
01

Geolocation & Classification

IP Address
216.24.210.190
Type
Residential
Country
🇺🇸 United States
City
Los Angeles
ISP
Ipxo LLC
Organization
Unknown
Autonomous System
AS62240 Clouvider
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger strong hits: 14High-risk paths: shells, RCE vectors, exploits+100
Burst: 14 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 48 req / 10sAbnormally fast request rate — automated scanning+35
Σ = 195
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-04-19 01:00:08
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA changed for same IP (+25), Danger strong hits: 14 (+100), Burst: 14 req / 2s (+35)
2026-04-19 01:00:08
Last malicious request observed
Total score reached: 195/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.190 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

🤖 Bot Detection

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

🌊 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.190.

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

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

10

Threat Analysis

216.24.210.190 has been assigned a threat score of 195/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:

User-Agent AnomalyRequest Flooding

📊 Threat Analysis

Network traffic from 216.24.210.190, located in Los Angeles, United States, operating on the network of Ipxo LLC, has been classified as malicious by our automated threat scoring engine. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. The dual attack vectors of User-Agent Anomaly combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. United States currently accounts for 217 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 195/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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

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

💡 IP Geolocation Accuracy Limitations

IP geolocation databases provide approximate locations with varying accuracy. City-level geolocation is typically 50-80% accurate, while country-level exceeds 95%. VPNs, proxies, and mobile networks further reduce reliability, making geolocation a useful but imperfect intelligence signal.

🔍 Check Any IP Address

Share this report: