
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 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 42/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 47/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 50/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 | |
| Burst 65/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 66/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| Danger medium hits: 100 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 126 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 135 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 138 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 140 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 141 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 150 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 162 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 164 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 168 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 172 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 178 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 188 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 199 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 200 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 207 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 210 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 235 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 273 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 278 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 280 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 282 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 300 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 302 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 312 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 338 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 345 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 362 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 376 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 40 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 400 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 42 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 45 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 47 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 488 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 70 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 75 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 84 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 90 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 92 | 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: 11 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 14 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 17 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger strong hits: 23 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger strong hits: 34 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 4 | 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: 7 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 8 | 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.
Block scanning from 4.224.122.112: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
IP 4.224.122.112 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Address UA spoofing from 4.224.122.112: 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.
4.224.122.112 has been assigned a threat score of 280/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:
Our monitoring infrastructure has identified 4.224.122.112, geolocated to Pune, India, operating on the network of Microsoft Corporation, as a source of suspicious network activity. The address has been active for 10 days in our monitoring system, producing 6,812 flagged requests at a rate of ~681.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. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. With 4,286 flagged addresses, India represents a major presence in our threat database. With a threat score of 280/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.
SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.