ABUSE.MOM
THREAT REPORT

IP Threat Report
20.205.227.70

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 06:07:13
First seen: 2026-02-22 21:00:05
Last seen: 2026-03-19 09:00:08
255

⛔ Verdict: BLOCK

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

DANGER_PATHBURSTRATIO_404
01

Geolocation & Classification

IP Address
20.205.227.70
Type
Hosting
Country
🇸🇬 Singapore
City
Singapore
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (southeastasia)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
282
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 10High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 25Medium-risk: admin panels, config files+60
Burst: 15 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 36 req / 10sAbnormally fast request rate — automated scanning+35
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst: 16 req / 2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 26Medium-risk: admin panels, config files+60
Burst: 37 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 9High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 40Medium-risk: admin panels, config files+60
Burst: 50 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 14 req / 2sAbnormally fast request rate — automated scanning+35
Danger strong hits: 14High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 41Medium-risk: admin panels, config files+60
Burst: 52 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 51 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 49 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 8High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 57Medium-risk: admin panels, config files+60
Burst: 56 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 54 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Burst: 32 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 19Medium-risk: admin panels, config files+60
Burst: 26 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 11 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 13 req / 2sAbnormally fast request rate — automated scanning+35
Danger strong hits: 12High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 48Medium-risk: admin panels, config files+60
Burst: 55 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 53 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 39Medium-risk: admin panels, config files+60
Burst: 44 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 40High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 102Medium-risk: admin panels, config files+60
Danger strong hits: 15High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 56Medium-risk: admin panels, config files+60
Danger strong hits: 24High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 51Medium-risk: admin panels, config files+60
Danger strong hits: 13High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 28Medium-risk: admin panels, config files+60
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger strong hits: 32High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 82Medium-risk: admin panels, config files+60
Burst: 48 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 45 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 27High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 87Medium-risk: admin panels, config files+60
Burst: 40 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 50High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 147Medium-risk: admin panels, config files+60
Danger medium hits: 29Medium-risk: admin panels, config files+60
Burst: 41 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 46Medium-risk: admin panels, config files+60
Danger medium hits: 36Medium-risk: admin panels, config files+60
Σ = 3200
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-02-22 21:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 10 (+100), Danger medium hits: 25 (+60), Burst: 15 req / 2s (+35)
2026-03-19 09:00:08
Last malicious request observed
Total score reached: 255/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Microsoft Corporation
AS8075 · 🇸🇬 Singapore
06

Recommendations

Actions taken & recommended

  • IP 20.205.227.70 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

🌊 Traffic Flood Defense

IP 20.205.227.70 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

🔎 Path Enumeration Protection

Block scanning from 20.205.227.70: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

09

Blacklist Status (DNSBL)

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

⛔ LISTED
Spamhaus ZEN

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

10

Threat Analysis

20.205.227.70 has been assigned a threat score of 255/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

Request FloodingPath Enumeration

📊 Threat Analysis

The address 20.205.227.70 originates from Singapore, Singapore, operating on the network of Microsoft Corporation. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 282 malicious requests from this address across a 24-day span, reflecting a sustained attack cadence of ~11.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 dual attack vectors of Request Flooding combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. With 101 flagged addresses, Singapore represents a significant presence in our threat database. At 255/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 Singapore

85.203.23.12 (340)85.203.23.31 (330)84.17.39.195 (325)192.166.246.30 (325)85.203.21.101 (320)View all →

🏢 Same network: AS8075

74.241.249.229 (340)4.182.24.88 (285)20.65.61.3 (283)4.205.39.97 (283)20.29.71.103 (283)View all →
12

Security Intelligence

💡 Cross-Site Scripting (XSS) Attacks

XSS attacks inject malicious scripts into web pages viewed by other users. Reflected XSS uses crafted URLs, while stored XSS persists in databases. Both types can steal session cookies, redirect users, or deface websites.

💡 Patch Management Urgency

The window between vulnerability disclosure and exploitation continues to shrink. Critical CVEs are now exploited within hours of publication. Automated patch management, virtual patching through WAFs, and rapid deployment pipelines are essential for timely remediation.

🔍 Check Any IP Address

Share this report: