ABUSE.MOM
THREAT REPORT

IP Threat Report
52.243.57.116

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 08:01:03
First seen: 2026-03-20 01:00:06
Last seen: 2026-03-26 09:00:07
255

⛔ Verdict: BLOCK

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

DANGER_PATHBURSTRATIO_404
01

Geolocation & Classification

IP Address
52.243.57.116
Type
Hosting
Country
🇯🇵 Japan
City
Tokyo
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (japaneast)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
49
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 30High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 204Medium-risk: admin panels, config files+60
Burst: 11 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 39 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 19High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 48Medium-risk: admin panels, config files+60
Burst: 6 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 22 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 38 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 12 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 42 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 41 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 27High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 207Medium-risk: admin panels, config files+60
Burst: 40 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 14High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 47Medium-risk: admin panels, config files+60
Danger strong hits: 40High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 107Medium-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: 11High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 34Medium-risk: admin panels, config files+60
Danger medium hits: 22Medium-risk: admin panels, config files+60
Burst: 24 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 15High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 55Medium-risk: admin panels, config files+60
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger strong hits: 9High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 31Medium-risk: admin panels, config files+60
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger medium hits: 21Medium-risk: admin panels, config files+60
Burst: 23 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 23Medium-risk: admin panels, config files+60
Danger strong hits: 22High-risk paths: shells, RCE vectors, exploits+100
Σ = 2180
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-20 01:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 30 (+100), Danger medium hits: 204 (+60), Burst: 11 req / 2s (+35)
2026-03-26 09:00:07
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 · 🇯🇵 Japan
06

Recommendations

Actions taken & recommended

  • IP 52.243.57.116 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 52.243.57.116.

🔎 Directory Scan Defense

IP 52.243.57.116 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

52.243.57.116 has been assigned a threat score of 255/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

Request FloodingPath Enumeration

📊 Threat Analysis

52.243.57.116 is registered in Tokyo, Japan, operating on the network of Microsoft Corporation. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 6 days, this IP generated 49 malicious requests, averaging approximately 8.2 requests per 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. Two attack patterns were identified (Request Flooding and Path Enumeration), suggesting a semi-automated campaign that targets multiple vulnerabilities. With 101 flagged addresses, Japan 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 Japan

103.163.220.216 (340)35.243.110.60 (288)20.89.56.154 (280)20.27.221.169 (280)20.210.188.132 (280)View all →

🏢 Same network: AS8075

20.89.56.154 (280)20.27.221.169 (280)20.210.188.132 (280)20.194.153.120 (280)104.46.236.39 (280)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.

💡 GDPR and Threat Intelligence

Processing IP addresses for security purposes under GDPR requires balancing legitimate interest in network protection with data minimization principles. Threat intelligence platforms must implement appropriate retention policies and provide mechanisms for data subject rights.

🔍 Check Any IP Address

Share this report: