ABUSE.MOM
THREAT REPORT

IP Threat Report
18.246.171.124

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-26 10:20:15
First seen: 2026-06-28 23:11:27
Last seen: 2026-07-05 04:01:33
120

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

IP Address
18.246.171.124
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
587
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 185
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-06-28 23:11:27
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), 404 ratio >= 60% (+25), Danger strong hits: 2 (+50)
2026-07-05 04:01:33
Last malicious request observed
Total score reached: 120/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.171.124 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Other malicious IPs detected in the same /24 subnet — consider blocking 18.246.171.0/24
  • 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 18.246.171.124: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

07

Neighbors in 18.246.171.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

09

Blacklist Status (DNSBL)

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

✓ Clean
cbl.abuseat.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
bl.spamcop.net

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

10

Threat Analysis

18.246.171.124 has been assigned a threat score of 120/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 Enumeration

📊 Threat Analysis

Our monitoring infrastructure has identified 18.246.171.124, geolocated to Portland, United States, operating on the network of Amazon.com, Inc, as a source of suspicious network activity. Our sensors captured 587 malicious requests from this address across a 6-day span, reflecting a sustained attack cadence of ~97.8 requests per day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. With 42 flagged addresses, United States represents a notable presence in our threat database. A score of 120/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

3.129.218.216 (288)18.191.74.68 (288)3.101.147.242 (278)18.222.210.168 (263)52.53.150.46 (253)View all →

🏢 Same network: AS16509

35.180.172.183 (298)3.129.218.216 (288)18.191.74.68 (288)3.72.250.64 (280)15.220.152.126 (280)View all →
12

Security Intelligence

💡 Brute Force Attack Mechanics

Brute force attacks systematically try username and password combinations to gain unauthorized access. Modern attacks leverage credential databases from previous breaches, testing millions of combinations using distributed botnets across multiple IP addresses.

💡 SSH Brute Force Defense

SSH servers face constant brute force attacks targeting common usernames and weak passwords. Key-based authentication, fail2ban, non-standard ports, and IP allowlisting dramatically reduce the attack surface. Monitoring auth logs reveals active campaigns and compromised credentials.

🔍 Check Any IP Address

Share this report: