ABUSE.MOM
THREAT REPORT

IP Threat Report
20.29.71.103

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:22:20
First seen: 2026-05-03 18:00:05
Last seen: 2026-05-05 08:00:05
283

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEUA_CHANGEDBURSTREFERERMETHOD
01

Geolocation & Classification

IP Address
20.29.71.103
Type
Hosting
Country
🇺🇸 United States
City
Des Moines
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (centralus)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
7
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger medium hits: 4Medium-risk: admin panels, config files+40
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 6Medium-risk: admin panels, config files+60
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Burst: 12 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 12 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
POST requests presentBehavioral anomaly detected by automated analysis+8
Σ = 473
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-03 18:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 2 (+50), Danger medium hits: 4 (+40), 404 ratio 40-60% (+15)
2026-05-05 08:00:05
Last malicious request observed
Total score reached: 283/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.29.71.103 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

🔎 Path Enumeration Protection

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

🤖 Bot Detection

Address UA spoofing from 20.29.71.103: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

🌊 Traffic Flood Defense

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

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (1)
PortServiceRiskDescription
49153UnknownLowService on port 49153

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

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

Path EnumerationUser-Agent AnomalyRequest Flooding

📊 Threat Analysis

The address 20.29.71.103 originates from Des Moines, United States, operating on the network of Microsoft Corporation. It was identified through automated analysis of incoming network traffic across monitored endpoints. The address has been active for 1 days in our monitoring system, producing 7 flagged requests at a rate of ~7/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. United States currently accounts for 222 blocked IPs in our database, making it a significant source of malicious traffic. At 283/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 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

20.65.61.3 (283)172.190.142.176 (280)20.96.32.182 (280)20.163.110.166 (280)104.209.148.10 (280)View all →
12

Security Intelligence

💡 Directory Traversal Attacks

Path traversal attacks attempt to access files outside the intended directory by manipulating file path references. Attackers use sequences like ../ to reach sensitive system files such as /etc/passwd or application configuration files.

💡 Remote Code Execution (RCE)

RCE vulnerabilities allow attackers to execute arbitrary code on target servers. These critical flaws often arise from deserialization bugs, template injection, or file upload vulnerabilities, and represent the highest severity class of web application weaknesses.

🔍 Check Any IP Address

Share this report: