ABUSE.MOM
THREAT REPORT

IP Threat Report
54.36.164.71

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-25 21:08:00
First seen: 2026-09-06 22:02:03
Last seen: 2026-09-13 01:18:17
105

⛔ Verdict: BLOCK

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

DANGER_PATHMETHODRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

IP Address
54.36.164.71
Type
Hosting
Country
🇬🇧 United Kingdom
City
City of London
ISP
OVH SAS
Organization
OVH Ltd
Autonomous System
AS16276 OVH SAS
Hit Count
360
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
POST seenBehavioral anomaly detected by automated analysis+8
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 198
03

Observed Activity

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

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

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

04

Timeline

2026-09-06 22:02:03
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger medium hits: 1 (+10), Danger medium hits: 2 (+20)
2026-09-13 01:18:17
Last malicious request observed
Total score reached: 105/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

OVH SAS
AS16276 · 🇬🇧 United Kingdom

We have detected 786 malicious IPs from this autonomous system.

View all IPs from AS16276 →
06

Recommendations

Actions taken & recommended

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

✓ Clean
dnsbl.dronebl.org
✓ Clean
zen.spamhaus.org
✓ Clean
psbl.surriel.com
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
bl.blocklist.de
✓ Clean
cbl.abuseat.org
✓ Clean
b.barracudacentral.org

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

10

Threat Analysis

54.36.164.71 has been assigned a threat score of 105/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

Network traffic from 54.36.164.71, located in City of London, United Kingdom, operating on the network of OVH SAS, has been classified as malicious by our automated threat scoring engine. The address has been active for 6 days in our monitoring system, producing 360 flagged requests at a rate of ~60/day. 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. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. United Kingdom currently accounts for 3,202 blocked IPs in our database, making it a major source of malicious traffic. At 105/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 Kingdom

45.86.203.126 (350)45.138.12.41 (350)91.230.225.114 (350)45.138.12.46 (350)185.192.71.72 (350)View all →

🏢 Same network: AS16276

51.195.86.200 (310)51.75.142.41 (310)139.99.56.79 (310)54.38.200.157 (300)51.38.99.224 (280)View all →
12

Security Intelligence

💡 Server-Side Request Forgery (SSRF)

SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.

💡 Command Injection Techniques

Command injection occurs when attackers insert operating system commands through application inputs. Successful exploitation grants direct server access, enabling data theft, malware installation, and lateral movement across networks.

🔍 Check Any IP Address

Share this report: