
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Danger medium hits: 5 | Medium-risk: admin panels, config files | +50 | |
| Directory Scan | Behavioral anomaly detected by automated analysis | +0 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 | |
| Spam | Spam/malware keywords in request content | +0 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 104.223.49.245 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
IP 104.223.49.245 is flooding forms with spam. Implement time-based tokens and block IPs submitting more than 5 forms per hour.
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.
104.223.49.245 has been assigned a threat score of 130/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:
The address 104.223.49.245 originates from Buffalo, United States, operating on the network of HostPapa. It was identified through automated analysis of incoming network traffic across monitored endpoints. During its 39-day observation window, we recorded 4,856 hostile requests from this IP — roughly 124.5 per day on average. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 103 flagged addresses, United States represents a significant presence in our threat database. A score of 130/100 places this address in the top tier of severity. Block and investigate any historical connections.
Insecure file upload functionality allows attackers to upload web shells, malware, or scripts that execute on the server. Proper validation must check file content, not just extensions, and uploaded files should be stored outside the web root.
Effective rate limiting must balance protection against abuse with allowing legitimate traffic bursts. Sliding window algorithms, token buckets, and adaptive thresholds based on client reputation provide layered defense against flooding attacks.