ABUSE.MOM
THREAT REPORT

IP Threat Report
52.90.102.38

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 05:06:18
First seen: 2026-04-04 01:00:05
Last seen: 2026-04-04 01:00:05
60

⛔ Verdict: BLOCK

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

UA_CHANGEDRATIO_404REFERER
01

Geolocation & Classification

IP Address
52.90.102.38
Type
Hosting
Country
🇺🇸 United States
City
Ashburn
ISP
Amazon.com, Inc.
Organization
AWS EC2 (us-east-1)
Autonomous System
AS14618 Amazon.com, Inc.
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA changed for same IPMultiple User-Agents — bot rotation technique+25
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Foreign referer seenReferer from unrelated external domain+10
Σ = 60
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-04 01:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA changed for same IP (+25), 404 ratio >= 60% (+25), Foreign referer seen (+10)
2026-04-04 01:00:05
Last malicious request observed
Total score reached: 60/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Amazon.com, Inc.
AS14618 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

🔎 Directory Scan Defense

IP 52.90.102.38 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
bl.spamcop.net
✓ Clean
zen.spamhaus.org
✓ 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.90.102.38 has been assigned a threat score of 60/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.

The following attack categories were identified:

User-Agent AnomalyPath Enumeration

📊 Threat Analysis

The address 52.90.102.38 originates from Ashburn, United States, operating on the network of Amazon.com, Inc.. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The dual attack vectors of User-Agent Anomaly combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. Our records show 201 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. At 60/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.

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: AS14618

185.117.225.111 (275)185.117.225.174 (275)3.238.226.143 (263)3.237.21.73 (263)3.231.166.236 (263)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.

💡 Vulnerability Scanning Explained

Vulnerability scanning is the automated process of probing web applications for known weaknesses. Attackers use tools like Nuclei, Nikto, and ZAP to test thousands of hosts per hour, looking for exposed configuration files, outdated software, and default credentials.

🔍 Check Any IP Address

Share this report: