ABUSE.MOM
THREAT REPORT

IP Threat Report
52.91.46.136

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:54:24
First seen: 2026-03-13 21:00:05
Last seen: 2026-03-13 21:00:05
230

⛔ Verdict: BLOCK

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

DANGER_PATHBURST
01

Geolocation & Classification

IP Address
52.91.46.136
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
Danger strong hits: 96High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 6Medium-risk: admin panels, config files+60
Burst: 100 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 100 req / 10sAbnormally fast request rate — automated scanning+35
Σ = 230
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-13 21:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 96 (+100), Danger medium hits: 6 (+60), Burst: 100 req / 2s (+35)
2026-03-13 21:00:05
Last malicious request observed
Total score reached: 230/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.91.46.136 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.91.46.136.

09

Blacklist Status (DNSBL)

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

✓ Clean
Spamhaus ZEN

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

10

Threat Analysis

52.91.46.136 has been assigned a threat score of 230/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 Flooding

📊 Threat Analysis

Network traffic from 52.91.46.136, located in Ashburn, United States, operating on the network of Amazon.com, Inc., has been classified as malicious by our automated threat scoring engine. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/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. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. United States currently accounts for 248 blocked IPs in our database, making it a significant source of malicious traffic. A score of 230/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: 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

💡 WordPress-Specific Attack Vectors

WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.

💡 Data Breach Impact Assessment

The impact of data breaches extends beyond immediate financial losses. Regulatory fines, legal liability, reputational damage, and customer churn create long-term costs that often exceed the direct costs of incident response and remediation.

🔍 Check Any IP Address

Share this report: