ABUSE.MOM
THREAT REPORT

IP Threat Report
198.11.183.50

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 10:04:23
First seen: 2026-02-19 22:00:06
Last seen: 2026-02-19 23:25:05
220

⛔ Verdict: BLOCK

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

BOT_UADANGER_PATHBURSTREFERERRATIO_404
01

Geolocation & Classification

IP Address
198.11.183.50
Type
Residential
Country
🇺🇸 United States
City
Minkler
ISP
Alibaba (US) Technology Co., Ltd.
Organization
Alibaba.com LLC
Autonomous System
AS45102 Alibaba (US) Technology Co., Ltd.
Hit Count
2
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
Danger strong hits: 14High-risk paths: shells, RCE vectors, exploits+100
Burst: 8 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 14 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Σ = 345
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-02-19 22:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: Go-http-client (+40), Danger strong hits: 14 (+100), Burst: 8 req / 2s (+35)
2026-02-19 23:25:05
Last malicious request observed
Total score reached: 220/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Alibaba (US) Technology Co., Ltd.
AS45102 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

🤖 Bot Detection

Address UA spoofing from 198.11.183.50: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

🌊 Flood / DDoS Mitigation

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

🔎 Path Enumeration Protection

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

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (4)
PortServiceRiskDescription
22SSHLowSecure Shell — common brute force target for remote access
80HTTPLowHTTP web server — standard web traffic
443HTTPSLowHTTPS web server — encrypted web traffic
8888HTTP-AltLowService on port 8888
KNOWN VULNERABILITIES (CVE) (20)
CVE IDLink
CVE-2025-32728NVD →
CVE-2018-15473NVD →
CVE-2017-15906NVD →
CVE-2023-38408NVD →
CVE-2023-51767NVD →
CVE-2023-48795NVD →
CVE-2019-6110NVD →
CVE-2020-15778NVD →
CVE-2019-6111NVD →
CVE-2008-3844NVD →
CVE-2019-6109NVD →
CVE-2021-36368NVD →
CVE-2025-26465NVD →
CVE-2021-41617NVD →
CVE-2023-51385NVD →
CVE-2016-20012NVD →
CVE-2018-15919NVD →
CVE-2018-20685NVD →
CVE-2007-2768NVD →
CVE-2020-14145NVD →

🔴 Security scanning identified 20 vulnerability entries on this host. This volume strongly suggests severely outdated software. Consult NVD advisories for details.

DETECTED TECHNOLOGIES
f5:nginxopenbsd:openssh:7.4
Hostnames: default.veikk.com
PTR: default.veikk.com

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

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

198.11.183.50 has been assigned a threat score of 220/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

User-Agent AnomalyRequest FloodingPath Enumeration

📊 Threat Analysis

IP address 198.11.183.50 has been traced to Minkler, United States, operating on the network of Alibaba (US) Technology Co., Ltd.. Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 1 days in our monitoring system, producing 2 flagged requests at a rate of ~2/day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. At 220/100, this is an extremely high-risk address. All traffic should be considered hostile.

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 United States

View all →

🏢 Same network: AS45102

8.213.218.53 (305)47.237.199.253 (300)8.215.205.243 (265)8.217.181.151 (215)43.99.86.17 (215)View all →
12

Security Intelligence

💡 HTTP Header Analysis for Threat Detection

Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.

💡 GraphQL Security Risks

GraphQL APIs introduce specific vulnerabilities including introspection information disclosure, query complexity attacks, batching abuse, and authorization bypass through nested queries. Depth limiting, cost analysis, and field-level authorization address these GraphQL-specific threats.

🔍 Check Any IP Address

Share this report: