ABUSE.MOM
THREAT REPORT

IP Threat Report
212.193.27.23

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 05:15:53
First seen: 2026-04-07 23:00:05
Last seen: 2026-04-07 23:00:05
70

⛔ Verdict: BLOCK

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

UA_CHANGEDBURSTREFERER
01

Geolocation & Classification

IP Address
212.193.27.23
Type
Hosting
Country
🇷🇺 Russia
City
Moscow
ISP
JSC "TIMEWEB"
Organization
JSC "TIMEWEB"
Autonomous System
AS9123 JSC TIMEWEB
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Burst: 7 req / 2sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Σ = 70
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-04-07 23:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA changed for same IP (+25), Burst: 7 req / 2s (+35), Foreign referer seen (+10)
2026-04-07 23:00:05
Last malicious request observed
Total score reached: 70/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

JSC "TIMEWEB"
AS9123 · 🇷🇺 Russia
06

Recommendations

Actions taken & recommended

  • IP 212.193.27.23 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 212.193.27.23: 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 212.193.27.23.

08

Open Ports & Services

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

OPEN PORTS (1)
PortServiceRiskDescription
443HTTPSLowHTTPS web server — encrypted web traffic

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
dnsbl.sorbs.net
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
bl.spamcop.net
✓ Clean
zen.spamhaus.org
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

212.193.27.23 has been assigned a threat score of 70/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.

The following attack categories were identified:

User-Agent AnomalyRequest Flooding

📊 Threat Analysis

Network traffic from 212.193.27.23, located in Moscow, Russia, operating on the network of JSC "TIMEWEB", has been classified as malicious by our automated threat scoring engine. Our sensors captured 1 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~1 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The dual attack vectors of User-Agent Anomaly combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. Our records show 115 malicious IPs originating from Russia, positioning it as a significant contributor to global threat activity. At 70/100, this IP warrants immediate defensive action.

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 Russia

157.22.102.172 (313)178.130.54.159 (288)72.56.191.6 (265)95.182.125.201 (265)91.240.87.225 (263)View all →

🏢 Same network: AS9123

85.239.41.242 (163)92.53.96.246 (150)185.119.56.182 (140)89.223.120.107 (125)5.129.246.208 (95)View all →
12

Security Intelligence

💡 TLS Fingerprinting (JA3/JA4)

TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.

💡 Subdomain Takeover Vulnerabilities

Subdomain takeover occurs when DNS records point to decommissioned services. Attackers claim the abandoned resource and serve content under the trusted domain, enabling cookie theft, phishing, and reputation damage.

🔍 Check Any IP Address

Share this report: