
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 96 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Burst: 67 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 96 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 69 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Burst: 68 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 144 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 63 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 36 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 859 | Medium-risk: admin panels, config files | +60 | |
| Burst: 32 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 91 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 372 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 2919 | Medium-risk: admin panels, config files | +60 | |
| Burst: 37 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 107 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 | |
| Burst: 5 req / 2s | Abnormally fast request rate — automated scanning | +35 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 20.240.45.211 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
Block scanning from 20.240.45.211: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
IP 20.240.45.211 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
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.
20.240.45.211 has been assigned a threat score of 245/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:
Threat intelligence analysis has linked 20.240.45.211 to malicious activity originating from Gävle, Sweden, operating on the network of Microsoft Corporation. The address has been under observation since its initial detection. The address has been active for 1 days in our monitoring system, producing 11 flagged requests at a rate of ~11/day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. 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 102 malicious IPs originating from Sweden, positioning it as a significant contributor to global threat activity. At 245/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.
Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.
Mobile carrier NAT (CGNAT) means thousands of users share a single public IP, making mobile IPs unreliable for reputation scoring. However, mobile networks are increasingly used as attack platforms through compromised apps and malicious SDKs.