IP Threat Report
20.91.190.16
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 48 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 264 | Medium-risk: admin panels, config files | +60 | |
| Burst: 121 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 200 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 102 | Medium-risk: admin panels, config files | +60 | |
| Burst: 44 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 143 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 18 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 88 | Medium-risk: admin panels, config files | +60 | |
| Burst: 67 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 135 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 56 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 151 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 70 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 63 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 71 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| 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: 47 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 102 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 69 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 90 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 66 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 68 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 64 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 48 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 59 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 153 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 37 req / 2s | Abnormally fast request rate — automated scanning | +35 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
Recommendations
Actions taken & recommended
- IP 20.91.190.16 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🤖 Bot Detection
Address UA spoofing from 20.91.190.16: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 20.91.190.16.
🔎 Directory Scan Defense
IP 20.91.190.16 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Blacklist Status (DNSBL)
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.
Threat Analysis
20.91.190.16 has been assigned a threat score of 280/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 Analysis
Network traffic from 20.91.190.16, located in Gävle, Sweden, operating on the network of Microsoft Corporation, has been classified as malicious by our automated threat scoring engine. During its 1-day observation window, we recorded 18 hostile requests from this IP — roughly 18 per day on average. 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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. With 121 flagged addresses, Sweden represents a significant presence in our threat database. A score of 280/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.
Related Threats
Security Intelligence
💡 User-Agent Analysis Techniques
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.
💡 Cryptojacking Detection and Prevention
Cryptojacking hijacks computing resources to mine cryptocurrency without consent. Indicators include unusual CPU usage, specific network connections to mining pools, and JavaScript miners embedded in compromised websites. Server-side cryptojacking can persist undetected for months.