ABUSE.MOM
THREAT REPORT

IP Threat Report
20.127.109.224

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-26 22:39:37
First seen: 2026-05-18 04:00:06
Last seen: 2026-05-24 09:50:59
115

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHREFERER
01

Geolocation & Classification

IP Address
20.127.109.224
Type
Hosting
Country
🇺🇸 United States
City
Boydton
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (eastus)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
300
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 29/10sAbnormally fast request rate — automated scanning+35
Burst 29/2sAbnormally fast request rate — automated scanning+35
Burst: 29 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 29 req / 2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Foreign refererReferer from unrelated external domain+10
Foreign referer seenReferer from unrelated external domain+10
Σ = 195
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-05-18 04:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 29/10s (+35), Burst 29/2s (+35), Burst: 29 req / 10s (+35)
2026-05-24 09:50:59
Last malicious request observed
Total score reached: 115/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Microsoft Corporation
AS8075 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 20.127.109.224.

09

Blacklist Status (DNSBL)

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

✓ Clean
dnsbl.dronebl.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
zen.spamhaus.org

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

10

Threat Analysis

20.127.109.224 has been assigned a threat score of 115/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:

Request Flooding

📊 Threat Analysis

Network traffic from 20.127.109.224, located in Boydton, United States, operating on the network of Microsoft Corporation, has been classified as malicious by our automated threat scoring engine. During its 6-day observation window, we recorded 300 hostile requests from this IP — roughly 50 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. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. Our records show 101 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. With a threat score of 115/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.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →

🏢 Same network: AS8075

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

Security Intelligence

💡 DDoS Mitigation Approaches

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.

💡 Deepfake Technology in Social Engineering

Deepfake audio and video enable convincing impersonation of executives and trusted individuals. Real-time voice cloning has been used in successful fraud campaigns, adding a new dimension to social engineering that traditional security training does not address.

🔍 Check Any IP Address

Share this report: