ABUSE.MOM
THREAT REPORT

IP Threat Report
15.152.216.219

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 11:32:47
First seen: 2026-05-25 05:54:39
Last seen: 2026-05-30 11:24:50
203

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHMETHODRATIO_404
01

Geolocation & Classification

IP Address
15.152.216.219
Type
Hosting
Country
🇯🇵 Japan
City
Osaka
ISP
Amazon Technologies Inc.
Organization
AWS EC2 (ap-northeast-3)
Autonomous System
AS16509 Amazon.com, Inc.
Hit Count
239
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 10/2sAbnormally fast request rate — automated scanning+35
Burst 33/10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 209High-risk paths: shells, RCE vectors, exploits+100
POST seenBehavioral anomaly detected by automated analysis+8
Σ = 203
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-25 05:54:39
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Burst 10/2s (+35), Burst 33/10s (+35)
2026-05-30 11:24:50
Last malicious request observed
Total score reached: 203/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 15.152.216.219 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 15.152.216.219 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Traffic Flood Defense

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

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
psbl.surriel.com
✓ Clean
zen.spamhaus.org
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

15.152.216.219 has been assigned a threat score of 203/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 EnumerationRequest Flooding

📊 Threat Analysis

Our monitoring infrastructure has identified 15.152.216.219, geolocated to Osaka, Japan, operating on the network of Amazon Technologies Inc., as a source of suspicious network activity. During its 5-day observation window, we recorded 239 hostile requests from this IP — roughly 47.8 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 (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 101 malicious IPs originating from Japan, positioning it as a significant contributor to global threat activity. With a threat score of 203/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 Japan

103.163.220.216 (340)35.243.110.60 (288)20.89.56.154 (280)20.27.221.169 (280)20.210.188.132 (280)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.

💡 TLS Fingerprinting (JA3/JA4)

TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.

🔍 Check Any IP Address

Share this report: