ABUSE.MOM
THREAT REPORT

IP Threat Report
20.46.122.23

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 00:48:15
First seen: 2026-06-30 15:25:59
Last seen: 2026-07-05 04:02:54
280

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404REDIRECT_PROBEUA_SUS
01

Geolocation & Classification

IP Address
20.46.122.23
Type
Hosting
Country
🇯🇵 Japan
City
Tokyo
ISP
Microsoft Corporation
Organization
Microsoft Azure Cloud (japaneast)
Autonomous System
AS8075 Microsoft Corporation
Hit Count
1883
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 11/2sAbnormally fast request rate — automated scanning+35
Burst 12/2sAbnormally fast request rate — automated scanning+35
Burst 25/10sAbnormally fast request rate — automated scanning+35
Burst 32/10sAbnormally fast request rate — automated scanning+35
Burst 36/10sAbnormally fast request rate — automated scanning+35
Burst 37/10sAbnormally fast request rate — automated scanning+35
Burst 38/10sAbnormally fast request rate — automated scanning+35
Burst 39/10sAbnormally fast request rate — automated scanning+35
Burst 40/10sAbnormally fast request rate — automated scanning+35
Burst 41/10sAbnormally fast request rate — automated scanning+35
Burst 42/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 103Medium-risk: admin panels, config files+60
Danger medium hits: 117Medium-risk: admin panels, config files+60
Danger medium hits: 220Medium-risk: admin panels, config files+60
Danger medium hits: 24Medium-risk: admin panels, config files+60
Danger medium hits: 25Medium-risk: admin panels, config files+60
Danger medium hits: 255Medium-risk: admin panels, config files+60
Danger medium hits: 340Medium-risk: admin panels, config files+60
Danger medium hits: 347Medium-risk: admin panels, config files+60
Danger medium hits: 348Medium-risk: admin panels, config files+60
Danger medium hits: 349Medium-risk: admin panels, config files+60
Danger medium hits: 526Medium-risk: admin panels, config files+60
Danger medium hits: 67Medium-risk: admin panels, config files+60
Danger strong hits: 107High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 115High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 118High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 12High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 170High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 172High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 230High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 32High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 34High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 47High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 81High-risk paths: shells, RCE vectors, exploits+100
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 2330
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 15:25:59
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), 404 ratio >= 60% (+25), Burst 11/2s (+35)
2026-07-05 04:02:54
Last malicious request observed
Total score reached: 280/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Microsoft Corporation
AS8075 · 🇯🇵 Japan
06

Recommendations

Actions taken & recommended

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

🔎 Path Enumeration Protection

Block scanning from 20.46.122.23: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 20.46.122.23.

🤖 User-Agent Anomaly Defense

IP 20.46.122.23 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
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
cbl.abuseat.org
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
bl.blocklist.de
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

20.46.122.23 has been assigned a threat score of 280/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

The address 20.46.122.23 originates from Tokyo, Japan, operating on the network of Microsoft Corporation. It was identified through automated analysis of incoming network traffic across monitored endpoints. The address has been active for 4 days in our monitoring system, producing 1,883 flagged requests at a rate of ~470.8/day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. Japan currently accounts for 106 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 280/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.189.151.182 (320)194.5.48.175 (305)34.97.45.15 (295)35.243.110.60 (288)View all →

🏢 Same network: AS8075

20.48.26.146 (280)52.140.193.66 (280)20.48.63.27 (280)104.46.220.175 (280)20.89.230.101 (280)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.

💡 CORS Misconfiguration Exploitation

Cross-Origin Resource Sharing misconfigurations can expose sensitive APIs to unauthorized origins. Wildcard policies, reflected origins, and null origin allowlisting create vulnerabilities that attackers exploit for data theft and unauthorized actions.

🔍 Check Any IP Address

Share this report: