
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Burst 100/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 102/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 103/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 104/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 105/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 106/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 107/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 108/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 110/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 112/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 113/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 25/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 27/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 28/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 29/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 30/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 31/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 49/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 90/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 91/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 93/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 94/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 98/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 40 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 80 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 240 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 241 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 482 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| 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.252.20.145 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Address UA spoofing from 35.252.20.145: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
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.252.20.145 has been assigned a threat score of 263/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.252.20.145 originates from Tel Aviv, IL, operating on the network of Google LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. The address has been active for 5 days in our monitoring system, producing 1,116 flagged requests at a rate of ~223.2/day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Two attack patterns were identified (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. With 205 flagged addresses, IL represents a significant presence in our threat database. With a threat score of 263/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
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.
Zero trust eliminates implicit trust based on network location. Every access request is verified regardless of source, minimizing the impact of compromised credentials or network breaches. Implementation requires strong identity verification and continuous authorization.