ABUSE.MOM
THREAT REPORT

IP Threat Report
213.139.221.201

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-28 15:50:13
First seen: 2026-09-19 06:02:50
Last seen: 2026-10-28 15:49:44
100

⛔ Verdict: BLOCK

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

BURSTMETHODREFERERUA_CHANGEDUA_SUSspam
01

Geolocation & Classification

IP Address
213.139.221.201
Type
VPN
Country
🇰🇿 KZ
City
Astana
ISP
INETTECH
Organization
Internet technologies LLC
Autonomous System
AS39238 OKB PROGRESS LLC
Hit Count
368
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 6/2sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
POST seenBehavioral anomaly detected by automated analysis+8
UA changedMultiple User-Agents — bot rotation technique+25
UA suspiciousBehavioral anomaly detected by automated analysis+15
spam:no_js_checkSpam/malware keywords in request content+0
Σ = 93
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-09-19 06:02:50
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 6/2s (+35), Foreign referer (+10), POST seen (+8)
2026-10-28 15:49:44
Last malicious request observed
Total score reached: 100/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

INETTECH
AS39238 · 🇰🇿 KZ

We have detected 14 malicious IPs from this autonomous system.

View all IPs from AS39238 →
06

Recommendations

Actions taken & recommended

  • IP 213.139.221.201 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 213.139.221.201.

🤖 Bot Detection

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

📧 Content Abuse Prevention

IP 213.139.221.201 is flooding forms with spam. Implement time-based tokens and block IPs submitting more than 5 forms per hour.

09

Blacklist Status (DNSBL)

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

✓ Clean
bl.blocklist.de
✓ Clean
zen.spamhaus.org
✓ Clean
cbl.abuseat.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
b.barracudacentral.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

213.139.221.201 has been assigned a threat score of 100/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 213.139.221.201, located in Astana, KZ, operating on the network of INETTECH, has been classified as malicious by our automated threat scoring engine. During its 39-day observation window, we recorded 368 hostile requests from this IP — roughly 9.4 per day on average. Classified as a VPN or proxy server, this IP serves as an anonymization layer. While VPNs have legitimate uses, this address has been observed routing clearly malicious traffic. Two attack patterns were identified (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 157 malicious IPs originating from KZ, positioning it as a significant contributor to global threat activity. At 100/100, this is an extremely high-risk address. All traffic should be considered hostile.

This IP is associated with a VPN or proxy service. Attackers frequently route their traffic through anonymizing services to obscure their true location. This makes attribution more challenging but the malicious behavior patterns remain detectable.

11

Related Threats

🇰🇿 Top threats from KZ

173.239.196.75 (255)173.239.196.79 (255)173.239.196.73 (255)173.239.196.71 (255)173.239.196.67 (255)View all →

🏢 Same network: AS39238

188.119.127.75 (165)45.89.72.124 (140)45.89.74.124 (140)45.89.74.29 (140)45.89.75.22 (105)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.

💡 HTTP Request Smuggling

Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.

🔍 Check Any IP Address

Share this report: