ABUSE.MOM
THREAT REPORT

IP Threat Report
18.246.252.25

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 11:03:11
First seen: 2026-02-22 16:00:06
Last seen: 2026-02-22 16:00:06
180

⛔ Verdict: BLOCK

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

DANGER_PATHBURSTRATIO_404
01

Geolocation & Classification

IP Address
18.246.252.25
Type
Hosting
Country
🇺🇸 United States
City
Portland
ISP
Amazon.com, Inc
Organization
AWS EC2 (us-west-2)
Autonomous System
AS16509 Amazon.com, Inc.
Hit Count
2
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger medium hits: 19Medium-risk: admin panels, config files+60
Burst: 9 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 19 req / 10sAbnormally fast request rate — automated scanning+35
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst: 14 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 21 req / 10sAbnormally fast request rate — automated scanning+35
Σ = 250
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-02-22 16:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 1 (+25), Danger medium hits: 19 (+60), Burst: 9 req / 2s (+35)
2026-02-22 16:00:06
Last malicious request observed
Total score reached: 180/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

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

Recommendations

Actions taken & recommended

  • IP 18.246.252.25 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

🌊 Traffic Flood Defense

IP 18.246.252.25 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

🔎 Directory Scan Defense

IP 18.246.252.25 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
Spamhaus ZEN

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

10

Threat Analysis

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

Our monitoring infrastructure has identified 18.246.252.25, geolocated to Portland, United States, operating on the network of Amazon.com, Inc, as a source of suspicious network activity. During its 1-day observation window, we recorded 2 hostile requests from this IP — roughly 2 per day on average. 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 (Request Flooding and Path Enumeration), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 130 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. With a threat score of 180/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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

💡 HTTP Request Smuggling

Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.

💡 Zero Trust Architecture Principles

Zero trust eliminates implicit trust based on network location. Every access request is verified regardless of source, minimizing the impact of compromised credentials or network breaches. Implementation requires strong identity verification and continuous authorization.

🔍 Check Any IP Address

Share this report: