
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Burst 100/10s | 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 117/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 117/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/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 129/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 129/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 65/2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 5 | Medium-risk: admin panels, config files | +50 | |
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 67 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 72 | 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.241.178.74 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 35.241.178.74.
IP 35.241.178.74 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.241.178.74 has been assigned a threat score of 273/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.
The following attack categories were identified:
35.241.178.74 is registered in Brussels, Belgium, operating on the network of Google LLC. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 20 days, this IP generated 703 malicious requests, averaging approximately 35.2 requests per 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. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. Our records show 844 malicious IPs originating from Belgium, positioning it as a major contributor to global threat activity. A score of 273/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.
Residential proxies route traffic through real home internet connections, making malicious traffic appear to come from legitimate users. Some networks install proxy software bundled with free applications, unknowingly conscripting millions of devices.