ABUSE.MOM
THREAT REPORT

IP Threat Report
20.215.70.55

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 09:50:51
First seen: 2026-04-04 17:00:05
Last seen: 2026-04-08 17:00:06
280

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 280/100. Total malicious requests observed: 35.

UA_SUSDANGER_PATHBURSTRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

IP Address
20.215.70.55
Type
Hosting
Country
🇵🇱 Poland
City
Warsaw
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (polandcentral)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
35
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA suspicious (short/empty)Behavioral anomaly detected by automated analysis+15
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 262Medium-risk: admin panels, config files+60
Burst: 41 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 120 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 176Medium-risk: admin panels, config files+60
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Burst: 112 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 50 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 160 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 47 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 152 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 53 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 145 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 57 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 164 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 119 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 174Medium-risk: admin panels, config files+60
Burst: 51 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 55 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 117 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 45 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 133 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 8High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 264Medium-risk: admin panels, config files+60
Burst: 198 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 62 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 200 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 114 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 42 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 140 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 44 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 137 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 166 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 48 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 154 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 43 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 106 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 131 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 256Medium-risk: admin panels, config files+60
Burst: 115 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 153 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 49 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 134 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 142 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 163 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 132 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 261Medium-risk: admin panels, config files+60
Burst: 124 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 150 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 54 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 161 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 147 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 63 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 149 req / 10sAbnormally fast request rate — automated scanning+35
Σ = 2285
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
[redacted]
GET
/page
200
Requests shown: 2 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-04-04 17:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA suspicious (short/empty) (+15), Danger strong hits: 6 (+100), Danger medium hits: 262 (+60)
2026-04-08 17:00:06
Last malicious request observed
Total score reached: 280/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Microsoft Corporation
AS8075 · 🇵🇱 Poland
06

Recommendations

Actions taken & recommended

  • IP 20.215.70.55 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.215.70.55: 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.215.70.55.

🔎 Directory Scan Defense

IP 20.215.70.55 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
bl.spamcop.net
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

20.215.70.55 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:

User-Agent AnomalyRequest FloodingPath Enumeration

📊 Threat Analysis

The address 20.215.70.55 originates from Warsaw, Poland, operating on the network of Microsoft Corporation. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 4 days, this IP generated 35 malicious requests, averaging approximately 8.8 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. With 102 flagged addresses, Poland represents a significant 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.

11

Related Threats

🇵🇱 Top threats from Poland

170.168.175.156 (313)170.168.96.250 (313)170.168.175.34 (313)74.248.132.176 (280)74.248.96.218 (280)View all →

🏢 Same network: AS8075

74.248.132.176 (280)74.248.96.218 (280)74.248.34.156 (280)20.215.67.86 (280)20.215.69.209 (280)View all →
12

Security Intelligence

💡 HTTP Header Analysis for Threat Detection

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.

💡 Open Source Intelligence Methods

OSINT techniques leverage publicly available information for security research. DNS records, WHOIS data, certificate transparency logs, social media, and code repositories all provide valuable intelligence for threat analysis without requiring special access or tools.

🔍 Check Any IP Address

Share this report: