ABUSE.MOM
THREAT REPORT

IP Threat Report
193.19.109.191

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-12 01:37:43
First seen: 2026-06-12 23:59:41
Last seen: 2026-07-12 00:26:09
100

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404
01

Geolocation & Classification

IP Address
193.19.109.191
Type
Unknown
Country
🇺🇸 United States
City
Seattle
ISP
F.N.S. HOLDINGS LIMITED
Organization
F.N.S. HOLDINGS LIMITED
Autonomous System
Unknown
Hit Count
228
02

Detection Signatures

SignatureDescriptionPointsSeverity
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
Directory ScanBehavioral anomaly detected by automated analysis+0
Σ = 60
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-06-12 23:59:41
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Danger medium hits: 1 (+10), Danger strong hits: 1 (+25)
2026-07-12 00:26:09
Last malicious request observed
Total score reached: 100/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 193.19.109.191 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
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Directory Scan Defense

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

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

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

10

Threat Analysis

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

Path Enumeration

📊 Threat Analysis

193.19.109.191 is registered in Seattle, United States, operating on the network of F.N.S. HOLDINGS LIMITED. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 29 days, this IP generated 228 malicious requests, averaging approximately 7.9 requests per day. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. With 151 flagged addresses, United States represents a significant presence in our threat database. With a threat score of 100/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.214.122 (350)103.215.74.213 (340)103.168.66.237 (340)34.187.158.4 (340)View all →
12

Security Intelligence

💡 Server-Side Request Forgery (SSRF)

SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.

💡 WebSocket Security Considerations

WebSocket connections bypass traditional HTTP security controls, creating opportunities for cross-site WebSocket hijacking, denial of service, and data injection. Proper origin validation, authentication, and message rate limiting are essential for secure WebSocket implementations.

🔍 Check Any IP Address

Share this report: