ABUSE.MOM
THREAT REPORT

IP Threat Report
35.77.69.111

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-21 17:34:55
First seen: 2026-04-09 16:00:07
Last seen: 2026-04-09 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: 12.

DANGER_PATHRATIO_404BURST
01

Geolocation & Classification

IP Address
35.77.69.111
Type
Hosting
Country
🇯🇵 Japan
City
Tokyo
ISP
Amazon.com, Inc.
Organization
AWS EC2 (ap-northeast-1)
Autonomous System
AS16509 Amazon.com, Inc.
Hit Count
12
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
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst: 11 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 21 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 10 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 20 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 9 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 8 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 19 req / 10sAbnormally fast request rate — automated scanning+35
Σ = 355
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-09 16:00:07
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), 404 ratio >= 60% (+25)
2026-04-09 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, Inc.
AS16509 · 🇯🇵 Japan
06

Recommendations

Actions taken & recommended

  • IP 35.77.69.111 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 35.77.69.111 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Traffic Flood Defense

IP 35.77.69.111 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
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
bl.spamcop.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

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

📊 Threat Analysis

Our monitoring infrastructure has identified 35.77.69.111, geolocated to Tokyo, Japan, operating on the network of Amazon.com, Inc., as a source of suspicious network activity. During its 1-day observation window, we recorded 12 hostile requests from this IP — roughly 12 per day on average. 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. 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. 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

💡 WordPress-Specific Attack Vectors

WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.

💡 Watering Hole Attack Strategy

Watering hole attacks compromise websites frequently visited by target organizations. Rather than attacking targets directly, adversaries infect trusted resources, exploiting the inherent trust users place in regularly visited sites.

🔍 Check Any IP Address

Share this report: