ABUSE.MOM
THREAT REPORT

IP Threat Report
52.225.25.97

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-21 20:31:44
First seen: 2026-04-26 12:00:05
Last seen: 2026-04-26 12:00:05
113

⛔ Verdict: BLOCK

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

DANGER_PATHREFERERMETHODRATIO_404
01

Geolocation & Classification

IP Address
52.225.25.97
Type
Hosting
Country
🇺🇸 United States
City
San Francisco
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (westus)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
2
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger medium hits: 2Medium-risk: admin panels, config files+20
Foreign referer seenReferer from unrelated external domain+10
POST requests presentBehavioral anomaly detected by automated analysis+8
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger medium hits: 1Medium-risk: admin panels, config files+10
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Σ = 173
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-04-26 12:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 3 (+75), Danger medium hits: 2 (+20), Foreign referer seen (+10)
2026-04-26 12:00:05
Last malicious request observed
Total score reached: 113/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 52.225.25.97 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

🔎 Directory Scan Defense

IP 52.225.25.97 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.

⛔ 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
truncate.gbudb.net
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

52.225.25.97 has been assigned a threat score of 113/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

52.225.25.97 is registered in San Francisco, United States, 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 1 days, this IP generated 2 malicious requests, averaging approximately 2 requests per 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. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. United States currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. At 113/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

74.241.249.229 (340)4.182.24.88 (285)20.65.61.3 (283)4.205.39.97 (283)20.29.71.103 (283)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.

💡 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.

🔍 Check Any IP Address

Share this report: