ABUSE.MOM
THREAT REPORT

IP Threat Report
183.90.237.48

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 11:03:15
First seen: 2026-03-06 18:00:04
Last seen: 2026-03-11 05:00:07
180

⛔ Verdict: BLOCK

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

DANGER_PATHBURSTREFERERRATIO_404
01

Geolocation & Classification

IP Address
183.90.237.48
Type
Hosting
Country
🇯🇵 Japan
City
Chiyoda City
ISP
Xserver Inc.
Organization
XSERVER Inc.
Autonomous System
AS131965 Xserver Inc.
Hit Count
2
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 10High-risk paths: shells, RCE vectors, exploits+100
Burst: 8 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 10 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst: 6 req / 2sAbnormally fast request rate — automated scanning+35
Σ = 340
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-03-06 18:00:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 10 (+100), Burst: 8 req / 2s (+35), Burst: 10 req / 10s (+35)
2026-03-11 05:00:07
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

Xserver Inc.
AS131965 · 🇯🇵 Japan
06

Recommendations

Actions taken & recommended

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

🌊 Flood / DDoS Mitigation

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

🔎 Directory Scan Defense

IP 183.90.237.48 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
Spamhaus ZEN

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

10

Threat Analysis

183.90.237.48 has been assigned a threat score of 180/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Request FloodingPath Enumeration

📊 Threat Analysis

Our monitoring infrastructure has identified 183.90.237.48, geolocated to Chiyoda City, Japan, operating on the network of Xserver Inc., as a source of suspicious network activity. During its 4-day observation window, we recorded 2 hostile requests from this IP — roughly 0.5 per day on average. 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 dual attack vectors of Request Flooding combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. Japan currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. A score of 180/100 places this address in the top tier of severity. Block and investigate any historical connections.

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

🏢 Same network: AS131965

View all →
12

Security Intelligence

💡 XML External Entity (XXE) Attacks

XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.

💡 Patch Management Urgency

The window between vulnerability disclosure and exploitation continues to shrink. Critical CVEs are now exploited within hours of publication. Automated patch management, virtual patching through WAFs, and rapid deployment pipelines are essential for timely remediation.

🔍 Check Any IP Address

Share this report: