ABUSE.MOM
THREAT REPORT

IP Threat Report
200.162.150.81

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-24 23:58:03
First seen: 2026-10-03 05:22:27
Last seen: 2026-10-04 00:59:08
235

⛔ Verdict: BLOCK

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

BOT_UABURSTDANGER_PATH
01

Geolocation & Classification

IP Address
200.162.150.81
Type
Hosting
Country
🇱🇮 LI
City
Vaduz
ISP
Clouvider Limited
Organization
Express Technologies Ltd
Autonomous System
AS62240 Clouvider
Hit Count
16
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 13/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 19Medium-risk: admin panels, config files+60
Danger strong hits: 13High-risk paths: shells, RCE vectors, exploits+100
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
Σ = 235
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-10-03 05:22:27
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 13/10s (+35), Danger medium hits: 19 (+60), Danger strong hits: 13 (+100)
2026-10-04 00:59:08
Last malicious request observed
Total score reached: 235/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Clouvider Limited
AS62240 · 🇱🇮 LI

We have detected 523 malicious IPs from this autonomous system.

View all IPs from AS62240 →
06

Recommendations

Actions taken & recommended

  • IP 200.162.150.81 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 200.162.150.0/24
  • 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 200.162.150.81.

🤖 User-Agent Anomaly Defense

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

07

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

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

10

Threat Analysis

200.162.150.81 has been assigned a threat score of 235/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

Network traffic from 200.162.150.81, located in Vaduz, LI, operating on the network of Clouvider Limited, has been classified as malicious by our automated threat scoring engine. Over a period of 1 days, this IP generated 16 malicious requests, averaging approximately 16 requests per day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Two attack patterns were identified (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. A score of 235/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 LI

200.162.150.151 (295)200.162.150.55 (245)193.107.20.12 (65)View all →

🏢 Same network: AS62240

85.203.15.117 (305)85.203.36.147 (305)85.203.36.151 (305)85.203.36.226 (305)185.192.69.167 (305)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.

💡 Subnet-Level vs IP-Level Blocking

When multiple IPs in a subnet show malicious behavior, subnet blocking efficiently neutralizes the threat. However, overly broad blocking risks impacting legitimate users. Analysis of subnet ownership and historical behavior guides appropriate blocking scope.

🔍 Check Any IP Address

Share this report: