ABUSE.MOM
THREAT REPORT

IP Threat Report
213.135.191.226

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 08:20:54
First seen: 2026-03-16 19:00:07
Last seen: 2026-03-16 19:00:07
103

⛔ Verdict: BLOCK

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

DANGER_PATHMETHOD
01

Geolocation & Classification

IP Address
213.135.191.226
Type
Residential
Country
🇲🇰 MK
City
Prilep
ISP
KDS KabelNet
Organization
Unknown
Autonomous System
AS44566 KDS-Kabel Net DOO
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger medium hits: 2Medium-risk: admin panels, config files+20
POST requests presentBehavioral anomaly detected by automated analysis+8
Σ = 103
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-03-16 19:00:07
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 3 (+75), Danger medium hits: 2 (+20), POST requests present (+8)
2026-03-16 19:00:07
Last malicious request observed
Total score reached: 103/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

KDS KabelNet
AS44566 · 🇲🇰 MK
06

Recommendations

Actions taken & recommended

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

⚙️ General Security

Add 213.135.191.226 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

⛔ LISTED
zen.spamhaus.org
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
truncate.gbudb.net
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

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

📊 Threat Analysis

The address 213.135.191.226 originates from Prilep, MK, operating on the network of KDS KabelNet. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per day. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. Our records show 21 malicious IPs originating from MK, positioning it as a notable contributor to global threat activity. A score of 103/100 places this address in the top tier of severity. Block and investigate any historical connections.

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 MK

92.53.35.143 (103)92.53.35.13 (93)92.53.30.161 (75)45.153.126.81 (70)98.159.226.199 (70)View all →

🏢 Same network: AS44566

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: