ABUSE.MOM
THREAT REPORT

IP Threat Report
217.181.82.212

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:11:12
First seen: 2026-03-17 18:00:05
Last seen: 2026-03-17 18:00:05
185

⛔ Verdict: BLOCK

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

BOT_UAUA_CHANGEDDANGER_PATHRATIO_404REFERER
01

Geolocation & Classification

IP Address
217.181.82.212
Type
Residential
Country
🇨🇦 Canada
City
Toronto
ISP
FTR
Organization
FTR
Autonomous System
AS200373 3xK Tech GmbH
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: javaKnown bot/crawler User-Agent detected+40
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger medium hits: 1Medium-risk: admin panels, config files+10
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Foreign referer seenReferer from unrelated external domain+10
Σ = 185
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-17 18:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: java (+40), UA changed for same IP (+25), Danger strong hits: 3 (+75)
2026-03-17 18:00:05
Last malicious request observed
Total score reached: 185/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

FTR
AS200373 · 🇨🇦 Canada
06

Recommendations

Actions taken & recommended

  • IP 217.181.82.212 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 217.181.82.212: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

🔎 Path Enumeration Protection

Block scanning from 217.181.82.212: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

08

Open Ports & Services

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

OPEN PORTS (3)
PortServiceRiskDescription
179UnknownLowService on port 179
1337UnknownLowService on port 1337
8081UnknownLowService on port 8081

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
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ 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

217.181.82.212 has been assigned a threat score of 185/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

User-Agent AnomalyPath Enumeration

📊 Threat Analysis

217.181.82.212 is registered in Toronto, Canada, operating on the network of FTR. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. 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 is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. Two attack patterns were identified (User-Agent Anomaly and Path Enumeration), suggesting a semi-automated campaign that targets multiple vulnerabilities. A score of 185/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 Canada

45.3.46.214 (205)217.181.80.13 (185)View all →

🏢 Same network: AS200373

45.3.45.201 (268)104.207.57.125 (233)65.111.24.117 (215)65.111.11.101 (210)45.3.46.214 (205)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.

💡 Container Security Challenges

Containerized applications face unique security challenges including vulnerable base images, excessive privileges, shared kernel attacks, and insecure orchestration configurations. Runtime security monitoring and immutable container policies mitigate these risks.

🔍 Check Any IP Address

Share this report: