
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 193.19.109.85 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
193.19.109.85 has been assigned a threat score of 75/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.
The following attack categories were identified:
Network traffic from 193.19.109.85, located in Seattle, United States, operating on the network of F.N.S. HOLDINGS LIMITED, has been classified as malicious by our automated threat scoring engine. Over a period of 11 days, this IP generated 313 malicious requests, averaging approximately 28.5 requests per day. The address operates as a VPN/proxy exit node. Attackers route traffic through anonymizing services to obscure their real location and evade IP-based security controls. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. United States currently accounts for 151 blocked IPs in our database, making it a significant source of malicious traffic. The score of 75/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.
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.
Path traversal attacks attempt to access files outside the intended directory by manipulating file path references. Attackers use sequences like ../ to reach sensitive system files such as /etc/passwd or application configuration files.
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.