ABUSE.MOM
THREAT REPORT

IP Threat Report
20.12.79.171

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 08:18:46
First seen: 2026-03-08 20:00:05
Last seen: 2026-03-09 01:00:08
280

⛔ Verdict: BLOCK

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

UA_SUSDANGER_PATHBURSTRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
UA suspicious (short/empty)Behavioral anomaly detected by automated analysis+15
Danger strong hits: 9High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 96Medium-risk: admin panels, config files+60
Burst: 24 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 78 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 144Medium-risk: admin panels, config files+60
Burst: 15 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 54 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst: 22 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 48 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 23 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 75 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 12High-risk paths: shells, RCE vectors, exploits+100
Burst: 83 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 21 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 72 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 22Medium-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: 20 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 24 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 77 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger medium hits: 11Medium-risk: admin panels, config files+60
Burst: 12 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 12 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 17 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 36 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 19 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 18 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 23 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 33Medium-risk: admin panels, config files+60
Burst: 32 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 35 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger medium hits: 2Medium-risk: admin panels, config files+20
Σ = 1625
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-03-08 20: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: 9 (+100), Danger medium hits: 96 (+60)
2026-03-09 01:00:08
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 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 20.12.79.171 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.12.79.171: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

🌊 Traffic Flood Defense

IP 20.12.79.171 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.12.79.171: 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.12.79.171 has been assigned a threat score of 280/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

User-Agent AnomalyRequest FloodingPath Enumeration

📊 Threat Analysis

IP address 20.12.79.171 has been traced to Boydton, United States, operating on the network of Microsoft Corporation. Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 1 days in our monitoring system, producing 34 flagged requests at a rate of ~34/day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. United States currently accounts for 135 blocked IPs in our database, making it a significant source of malicious traffic. 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.

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)20.29.71.103 (283)172.190.142.176 (280)20.96.32.182 (280)20.163.110.166 (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.

💡 Critical Infrastructure Targeting

Attacks on power grids, water systems, and transportation networks have moved from theoretical to practical threats. Industrial control systems often lack modern security features, making them vulnerable to both targeted and opportunistic attacks.

🔍 Check Any IP Address

Share this report: