ABUSE.MOM
THREAT REPORT

IP Threat Report
193.19.109.4

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 02:38:57
First seen: 2026-06-02 23:29:40
Last seen: 2026-07-19 04:02:19
100

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404UA_CHANGED
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Directory ScanBehavioral anomaly detected by automated analysis+0
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 100
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-02 23:29:40
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger medium hits: 1 (+10), Danger strong hits: 2 (+50)
2026-07-19 04:02:19
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.4 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.4 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🤖 User-Agent Anomaly Defense

IP 193.19.109.4 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

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

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

10

Threat Analysis

193.19.109.4 has been assigned a threat score of 100/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.4 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. Over a period of 46 days, this IP generated 262 malicious requests, averaging approximately 5.7 requests per day. The dual attack vectors of Path Enumeration combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. 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.168.66.237 (340)34.187.158.4 (340)34.186.187.208 (340)View all →
12

Security Intelligence

💡 Prototype Pollution Attacks

Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.

💡 GeoIP Blocking Considerations

Blocking traffic from specific countries reduces attack surface but impacts legitimate international users. Effective geo-based policies use tiered approaches — blocking, rate limiting, or requiring additional verification based on risk assessment.

🔍 Check Any IP Address

Share this report: