
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| 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 53/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 54/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 55/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 58/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 60/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 61/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 62/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 63/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 65/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 66/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 119 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 172 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 238 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 16 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger strong hits: 32 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 43 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 | |
| UA suspicious | Behavioral anomaly detected by automated analysis | +15 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 74.225.168.179 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 74.225.168.179.
Address UA spoofing from 74.225.168.179: 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.
74.225.168.179 has been assigned a threat score of 280/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.
The following attack categories were identified:
The address 74.225.168.179 originates from Pune, India, operating on the network of AT&T Corp.. It was identified through automated analysis of incoming network traffic across monitored endpoints. During its 10-day observation window, we recorded 790 hostile requests from this IP — roughly 79 per day on average. 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. With 4,286 flagged addresses, India represents a major presence in our threat database. At 280/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.
Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.