
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Burst 112/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 112/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 113/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 113/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 116/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 116/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 118/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 118/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 119/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 119/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 120/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 120/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 121/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 121/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 122/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 122/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 124/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 125/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 125/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 126/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 129/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 131/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 131/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 86/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 86/2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 | |
| Danger medium hits: 5 | Medium-risk: admin panels, config files | +50 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger strong hits: 58 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 71 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 72 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 73 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 74 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 75 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 76 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| POST seen | Behavioral anomaly detected by automated analysis | +8 | |
| 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 35.240.100.200 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
IP 35.240.100.200 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
IP 35.240.100.200 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
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.
35.240.100.200 has been assigned a threat score of 278/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.
The following attack categories were identified:
The address 35.240.100.200 originates from Brussels, Belgium, operating on the network of Google LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 30 days, this IP generated 3,562 malicious requests, averaging approximately 118.7 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. Belgium currently accounts for 842 blocked IPs in our database, making it a major source of malicious traffic. A score of 278/100 places this address in the top tier of severity. Block and investigate any historical connections.
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.
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.
Immutable, offline backups remain the most effective defense against ransomware. The 3-2-1 rule — three copies on two media types with one offsite — combined with regular recovery testing ensures business continuity after encryption attacks.