ABUSE.MOM
THREAT REPORT

IP Threat Report
13.158.77.167

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-21 17:18:00
First seen: 2026-04-02 09:00:06
Last seen: 2026-04-23 18:00:05
180

⛔ Verdict: BLOCK

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

DANGER_PATHBURSTRATIO_404
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger medium hits: 18Medium-risk: admin panels, config files+60
Burst: 6 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: 9 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 20 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-04-02 09: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: 18 (+60), Burst: 6 req / 2s (+35)
2026-04-23 18:00:05
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
AS16509 · 🇯🇵 Japan
06

Recommendations

Actions taken & recommended

  • IP 13.158.77.167 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 13.158.77.167 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

🔎 Directory Scan Defense

IP 13.158.77.167 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
ix.dnsbl.manitu.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net

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

10

Threat Analysis

13.158.77.167 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

Threat intelligence analysis has linked 13.158.77.167 to malicious activity originating from Tokyo, Japan, operating on the network of Amazon.com. The address has been under observation since its initial detection. Over a period of 21 days, this IP generated 3 malicious requests, averaging approximately 0.1 requests per 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 (Request Flooding and Path Enumeration), suggesting a semi-automated campaign that targets multiple vulnerabilities. Japan currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. At 180/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)20.89.56.154 (280)20.27.221.169 (280)20.210.188.132 (280)20.194.153.120 (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

💡 Server-Side Request Forgery (SSRF)

SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.

💡 File Upload Vulnerabilities

Insecure file upload functionality allows attackers to upload web shells, malware, or scripts that execute on the server. Proper validation must check file content, not just extensions, and uploaded files should be stored outside the web root.

🔍 Check Any IP Address

Share this report: