ABUSE.MOM
THREAT REPORT

IP Threat Report
167.103.43.26

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 07:23:42
First seen: 2026-03-13 15:00:06
Last seen: 2026-03-13 15:00:06
65

⛔ Verdict: BLOCK

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

BOT_UADANGER_PATH
01

Geolocation & Classification

IP Address
167.103.43.26
Type
Residential
Country
🇯🇵 Japan
City
Tokyo
ISP
ZSCALER, INC.
Organization
Zscaler Tyo4
Autonomous System
AS53813 ZSCALER, INC.
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: pythonKnown bot/crawler User-Agent detected+40
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Σ = 65
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-03-13 15:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: python (+40), Danger strong hits: 1 (+25)
2026-03-13 15:00:06
Last malicious request observed
Total score reached: 65/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

ZSCALER, INC.
AS53813 · 🇯🇵 Japan
06

Recommendations

Actions taken & recommended

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

🤖 User-Agent Anomaly Defense

IP 167.103.43.26 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
Spamhaus ZEN

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

10

Threat Analysis

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

The following attack categories were identified:

User-Agent Anomaly

📊 Threat Analysis

Our monitoring infrastructure has identified 167.103.43.26, geolocated to Tokyo, Japan, operating on the network of ZSCALER, INC., as a source of suspicious network activity. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/day. 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. Detected suspicious User-Agent anomalies including empty, forged, or rapidly rotating UA strings — characteristic of automated scanning tools. Japan currently accounts for 104 blocked IPs in our database, making it a significant source of malicious traffic. At 65/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.

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.243.110.60 (288)20.89.56.154 (280)20.27.221.169 (280)20.210.188.132 (280)View all →

🏢 Same network: AS53813

136.226.254.203 (105)167.103.34.99 (105)167.103.115.101 (105)101.2.203.22 (65)167.103.42.249 (65)View all →
12

Security Intelligence

💡 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.

💡 Content Security Policy Implementation

Content Security Policy headers instruct browsers to restrict resource loading, mitigating XSS and data injection attacks. Properly configured CSP policies prevent inline script execution, restrict iframe embedding, and control which domains can serve content.

🔍 Check Any IP Address

Share this report: