ABUSE.MOM
THREAT REPORT

IP Threat Report
18.179.223.49

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-08-23 22:13:32
First seen: 2026-08-21 22:11:03
Last seen: 2026-08-23 02:06:01
95

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404
01

Geolocation & Classification

IP Address
18.179.223.49
Type
Hosting
Country
🇯🇵 Japan
City
Tokyo
ISP
Amazon Technologies Inc.
Organization
AWS EC2 (ap-northeast-1)
Autonomous System
AS16509 Amazon.com, Inc.
Hit Count
187
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 medium hits: 1Medium-risk: admin panels, config files+10
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Σ = 220
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-08-21 22:11:03
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 medium hits: 1 (+10)
2026-08-23 02:06:01
Last malicious request observed
Total score reached: 95/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Amazon Technologies Inc.
AS16509 · 🇯🇵 Japan
06

Recommendations

Actions taken & recommended

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

🔎 Directory Scan Defense

IP 18.179.223.49 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.dronebl.org
✓ Clean
zen.spamhaus.org
✓ Clean
bl.blocklist.de
✓ Clean
cbl.abuseat.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

18.179.223.49 has been assigned a threat score of 95/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

Our monitoring infrastructure has identified 18.179.223.49, geolocated to Tokyo, Japan, operating on the network of Amazon Technologies Inc., as a source of suspicious network activity. Over a period of 1 days, this IP generated 187 malicious requests, averaging approximately 187 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 IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. Japan currently accounts for 107 blocked IPs in our database, making it a significant source of malicious traffic. At 95/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 Japan

103.163.220.216 (340)35.189.151.182 (320)168.110.63.243 (320)129.225.172.187 (310)194.5.48.175 (305)View all →

🏢 Same network: AS16509

35.180.172.183 (298)3.129.218.216 (288)18.191.74.68 (288)34.244.9.175 (288)51.44.13.36 (288)View all →
12

Security Intelligence

💡 Cross-Site Scripting (XSS) Attacks

XSS attacks inject malicious scripts into web pages viewed by other users. Reflected XSS uses crafted URLs, while stored XSS persists in databases. Both types can steal session cookies, redirect users, or deface websites.

💡 CAPTCHA and Bot Detection

CAPTCHAs remain a primary bot defense but face increasing bypass rates from AI-powered solvers. Modern alternatives include invisible behavioral analysis, proof-of-work challenges, and device fingerprinting that detect bots without impacting user experience.

🔍 Check Any IP Address

Share this report: