ABUSE.MOM
THREAT REPORT

IP Threat Report
193.19.109.24

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-29 16:10:56
First seen: 2026-03-27 06:00:08
Last seen: 2026-05-29 15:47:14
90

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404UA_SUS
01

Geolocation & Classification

IP Address
193.19.109.24
Type
VPN/Proxy
Country
🇺🇸 United States
City
Seattle
ISP
F.N.S. HOLDINGS LIMITED
Organization
VPN Consumer Seattle, United States of America
Autonomous System
AS206092 F.N.S. HOLDINGS LIMITED
Hit Count
237
02

Detection Signatures

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

Network Provider

F.N.S. HOLDINGS LIMITED
AS206092 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

🔎 Directory Scan Defense

IP 193.19.109.24 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🤖 Bot Detection

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

07

Neighbors in 193.19.109.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.dronebl.org
✓ Clean
bl.blocklist.de

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

10

Threat Analysis

193.19.109.24 has been assigned a threat score of 90/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 193.19.109.24 to malicious activity originating from Seattle, United States, operating on the network of F.N.S. HOLDINGS LIMITED. The address has been under observation since its initial detection. During its 63-day observation window, we recorded 237 hostile requests from this IP — roughly 3.8 per day on average. Classified as a VPN or proxy server, this IP serves as an anonymization layer. While VPNs have legitimate uses, this address has been observed routing clearly malicious traffic. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. United States currently accounts for 150 blocked IPs in our database, making it a significant source of malicious traffic. A score of 90/100 places this address in the top tier of severity. Block and investigate any historical connections.

This IP is associated with a VPN or proxy service. Attackers frequently route their traffic through anonymizing services to obscure their true location. This makes attribution more challenging but the malicious behavior patterns remain detectable.

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

💡 WordPress-Specific Attack Vectors

WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.

💡 Mobile Malware Distribution

Mobile malware reaches devices through unofficial app stores, malicious links, and even occasionally through official stores using obfuscation techniques. Banking trojans, spyware, and ransomware variants specifically designed for mobile platforms continue to proliferate.

🔍 Check Any IP Address

Share this report: