
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 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 31/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 41/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 44/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 45/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 46/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 47/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 48/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 49/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 52/10s | 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 59/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 64/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| Danger medium hits: 119 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 124 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 126 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 146 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 182 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 195 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger medium hits: 212 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 213 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 214 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 215 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 231 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 238 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 247 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 251 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 252 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 253 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 254 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 272 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 3 | Medium-risk: admin panels, config files | +30 | |
| Danger medium hits: 309 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 31 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 314 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 315 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 317 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 374 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 378 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 379 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 41 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 43 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 468 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 471 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 504 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 564 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 57 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 58 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 60 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 61 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 62 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 63 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 64 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 65 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 84 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 93 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 94 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger strong hits: 10 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 11 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 17 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 18 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 19 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger strong hits: 20 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 21 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 22 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 23 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 24 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 25 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 27 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 28 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 29 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger strong hits: 30 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 31 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 33 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 37 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 38 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 40 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 41 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 42 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 5 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 9 | 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.
We have detected 1852 malicious IPs from this autonomous system.
IP 4.240.25.22 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
IP 4.240.25.22 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
IP 4.240.25.22 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.
4.240.25.22 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:
Our monitoring infrastructure has identified 4.240.25.22, geolocated to Pune, India, operating on the network of Microsoft Corporation, as a source of suspicious network activity. Over a period of 10 days, this IP generated 11,547 malicious requests, averaging approximately 1154.7 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 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.
Race conditions occur when application behavior depends on the timing of concurrent operations. Attackers exploit these timing windows to bypass limits, duplicate transactions, or escalate privileges by sending carefully timed parallel requests.