ABUSE.MOM
THREAT REPORT

IP Threat Report
15.237.253.13

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:21:48
First seen: 2026-05-21 10:39:54
Last seen: 2026-05-24 10:19:50
263

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHMETHODRATIO_404
01

Geolocation & Classification

IP Address
15.237.253.13
Type
Hosting
Country
🇫🇷 France
City
Paris
ISP
Amazon Technologies Inc.
Organization
AWS EC2 (eu-west-3)
Autonomous System
AS16509 Amazon.com, Inc.
Hit Count
337
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 200/10sAbnormally fast request rate — automated scanning+35
Burst 60/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 40Medium-risk: admin panels, config files+60
Danger strong hits: 241High-risk paths: shells, RCE vectors, exploits+100
POST seenBehavioral anomaly detected by automated analysis+8
Σ = 263
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-05-21 10:39:54
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Burst 200/10s (+35), Burst 60/2s (+35)
2026-05-24 10:19:50
Last malicious request observed
Total score reached: 263/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Amazon Technologies Inc.
AS16509 · 🇫🇷 France
06

Recommendations

Actions taken & recommended

  • IP 15.237.253.13 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 15.237.253.13: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 15.237.253.13.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

15.237.253.13 has been assigned a threat score of 263/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

Path EnumerationRequest Flooding

📊 Threat Analysis

Our monitoring infrastructure has identified 15.237.253.13, geolocated to Paris, France, operating on the network of Amazon Technologies Inc., as a source of suspicious network activity. The address has been active for 2 days in our monitoring system, producing 337 flagged requests at a rate of ~168.5/day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. Two attack patterns were identified (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. At 263/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 France

35.180.234.238 (263)51.44.11.24 (263)15.188.60.86 (263)35.181.153.137 (263)35.180.198.159 (263)View all →

🏢 Same network: AS16509

15.220.152.241 (320)18.219.106.176 (315)15.220.169.114 (280)108.136.131.13 (265)54.206.58.169 (263)View all →
12

Security Intelligence

💡 DDoS Mitigation Approaches

Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.

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

🔍 Check Any IP Address

Share this report: