ABUSE.MOM
THREAT REPORT

IP Threat Report
185.233.211.224

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-28 13:42:58
First seen: 2026-10-27 22:53:46
Last seen: 2026-10-28 13:20:03
245

⛔ Verdict: BLOCK

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

BOT_UABURSTDANGER_PATHREFERER
01

Geolocation & Classification

IP Address
185.233.211.224
Type
Hosting
Country
🇲🇰 MK
City
Skopje
ISP
TELEKS DOOEL Skopje
Organization
Teleks Web Hosting
Autonomous System
AS205119 TELEKS DOOEL Skopje
Hit Count
32
02

Detection Signatures

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

Network Provider

TELEKS DOOEL Skopje
AS205119 · 🇲🇰 MK

We have detected 4 malicious IPs from this autonomous system.

View all IPs from AS205119 →
06

Recommendations

Actions taken & recommended

  • IP 185.233.211.224 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 185.233.211.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 185.233.211.224.

🤖 User-Agent Anomaly Defense

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

07

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

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

10

Threat Analysis

185.233.211.224 has been assigned a threat score of 245/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

185.233.211.224 is registered in Skopje, MK, operating on the network of TELEKS DOOEL Skopje. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. The address has been active for 1 days in our monitoring system, producing 32 flagged requests at a rate of ~32/day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. Two attack patterns were identified (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 27 malicious IPs originating from MK, positioning it as a notable contributor to global threat activity. A score of 245/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 MK

185.233.211.91 (295)185.233.211.216 (295)185.233.211.16 (200)213.135.191.226 (103)92.53.35.143 (103)View all →

🏢 Same network: AS205119

185.233.211.91 (295)185.233.211.216 (295)185.233.211.16 (200)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.

💡 Rate Limiting and Throttling Strategies

Effective rate limiting must balance protection against abuse with allowing legitimate traffic bursts. Sliding window algorithms, token buckets, and adaptive thresholds based on client reputation provide layered defense against flooding attacks.

🔍 Check Any IP Address

Share this report: