ABUSE.MOM
THREAT REPORT

IP Threat Report
202.78.167.209

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-20 08:46:36
First seen: 2026-06-30 05:23:57
Last seen: 2026-07-20 08:39:39
78

⛔ Verdict: BLOCK

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

BURSTMETHODRATIO_404REFERER
01

Geolocation & Classification

IP Address
202.78.167.209
Type
Residential
Country
🇯🇵 Japan
City
Tokyo
ISP
G-Core Labs S.A.
Organization
GCL
Autonomous System
AS202422 G-Core Labs S.A.
Hit Count
2670
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 5/2sAbnormally fast request rate — automated scanning+35
Burst 8/2sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
POST seenBehavioral anomaly detected by automated analysis+8
Σ = 113
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-06-30 05:23:57
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Burst 5/2s (+35), Burst 8/2s (+35)
2026-07-20 08:39:39
Last malicious request observed
Total score reached: 78/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

G-Core Labs S.A.
AS202422 · 🇯🇵 Japan
06

Recommendations

Actions taken & recommended

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

🌊 Traffic Flood Defense

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

07

Neighbors in 202.78.167.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
psbl.surriel.com
✓ Clean
cbl.abuseat.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
bl.blocklist.de

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

10

Threat Analysis

202.78.167.209 has been assigned a threat score of 78/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.

The following attack categories were identified:

Path EnumerationRequest Flooding

📊 Threat Analysis

202.78.167.209 is registered in Tokyo, Japan, operating on the network of G-Core Labs S.A.. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. During its 20-day observation window, we recorded 2,670 hostile requests from this IP — roughly 133.5 per day on average. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. Two attack patterns were identified (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 102 malicious IPs originating from Japan, positioning it as a significant contributor to global threat activity. At 78/100, this IP warrants immediate defensive action.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

11

Related Threats

🇯🇵 Top threats from Japan

103.163.220.216 (340)35.189.151.182 (320)194.5.48.175 (305)34.97.45.15 (295)35.243.110.60 (288)View all →

🏢 Same network: AS202422

202.78.167.117 (78)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.

💡 IPv6 Scanning Challenges

The vast IPv6 address space makes traditional sequential scanning impractical. However, attackers use DNS records, certificate transparency logs, and predictable address patterns to identify active IPv6 hosts, adapting their techniques to the expanded address space.

🔍 Check Any IP Address

Share this report: