
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 14 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst: 9 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 22 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 13 | Medium-risk: admin panels, config files | +60 | |
| Burst: 13 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 15 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 10 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 10 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 11 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 8 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 15 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 11 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 6 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 16 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 16 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 23 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 17 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 5 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 12 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 7 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 19 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 17 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Imported from old blocklist | Behavioral anomaly detected by automated analysis | +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 167.71.118.212 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
IP 167.71.118.212 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
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.
167.71.118.212 has been assigned a threat score of 155/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.
The following attack categories were identified:
IP address 167.71.118.212 has been traced to Santa Clara, United States, operating on the network of DigitalOcean, LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Over a period of 1 days, this IP generated 24 malicious requests, averaging approximately 24 requests per day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. Two attack patterns were identified (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. United States currently accounts for 128 blocked IPs in our database, making it a significant source of malicious traffic. At 155/100, this is an extremely high-risk address. All traffic should be considered hostile.
This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.
Brute force attacks systematically try username and password combinations to gain unauthorized access. Modern attacks leverage credential databases from previous breaches, testing millions of combinations using distributed botnets across multiple IP addresses.
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.