
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Burst 107/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 109/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 13/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 14/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 15/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 16/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 17/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 18/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 23/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 24/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 41/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 43/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 44/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 50/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 51/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 56/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 57/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 61/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 71/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 79/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 84/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 40 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 225 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 227 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 241 | 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.7.178 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
IP 35.252.7.178 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.
35.252.7.178 has been assigned a threat score of 263/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:
IP address 35.252.7.178 has been traced to Tel Aviv, IL, operating on the network of Google LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 1 days in our monitoring system, producing 114 flagged requests at a rate of ~114/day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The dual attack vectors of Request Flooding combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. IL currently accounts for 205 blocked IPs in our database, making it a significant source of malicious traffic. At 263/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.
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.
Modern phishing operations use sophisticated infrastructure including lookalike domains, valid TLS certificates, and evasion techniques like cloaking and geofencing. Analyzing this infrastructure reveals campaigns before they reach their targets.