
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 | |
| Burst 16/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 16/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 35/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 37/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 39/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 47/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 47/2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 20 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 8 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| UA changed | Multiple User-Agents — bot rotation technique | +25 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 208.84.100.191 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
IP 208.84.100.191 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
IP 208.84.100.191 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
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.
208.84.100.191 has been assigned a threat score of 230/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:
Network traffic from 208.84.100.191, located in North Kansas City, United States, operating on the network of Fro LLC, has been classified as malicious by our automated threat scoring engine. During its 5-day observation window, we recorded 651 hostile requests from this IP — roughly 130.2 per day on average. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. Our records show 178 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. At 230/100, this is an extremely high-risk address. All traffic should be considered hostile.
This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.
Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.
BEC attacks use compromised or spoofed executive email accounts to request fraudulent wire transfers or sensitive data. These attacks cause billions in annual losses and rely on social engineering rather than technical exploitation.