ABUSE.MOM
THREAT REPORT

IP Threat Report
173.34.36.39

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-26 23:43:38
First seen: 2026-03-17 23:00:06
Last seen: 2026-04-05 09:00:06
103

⛔ Verdict: BLOCK

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

DANGER_PATHMETHOD
01

Geolocation & Classification

IP Address
173.34.36.39
Type
Residential
Country
🇨🇦 Canada
City
Dieppe
ISP
Rogers Communications Canada Inc.
Organization
Rogers Cable Inc. BLOOR
Autonomous System
AS812 Rogers Communications Canada Inc.
Hit Count
2
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-17 23:00:06
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-04-05 09:00:06
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

Rogers Communications Canada Inc.
AS812 · 🇨🇦 Canada
06

Recommendations

Actions taken & recommended

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

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

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

10

Threat Analysis

173.34.36.39 has been assigned a threat score of 103/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

📊 Threat Analysis

173.34.36.39 is registered in Dieppe, Canada, operating on the network of Rogers Communications Canada Inc.. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. During its 18-day observation window, we recorded 2 hostile requests from this IP — roughly 0.1 per day on average. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. Canada currently accounts for 115 blocked IPs in our database, making it a significant source of malicious traffic. At 103/100, this is an extremely high-risk address. All traffic should be considered hostile.

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

20.151.111.128 (308)45.91.23.64 (305)147.15.149.40 (300)148.116.72.171 (300)89.251.0.24 (295)View all →

🏢 Same network: AS812

24.114.60.30 (103)99.237.215.231 (103)99.209.173.182 (103)99.234.135.34 (103)72.136.103.71 (103)View all →
12

Security Intelligence

💡 API Abuse and Enumeration

Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.

💡 IoT Device Compromise Patterns

Internet of Things devices are prime targets for botnet recruitment due to weak default credentials, infrequent updates, and always-on connectivity. Compromised IoT devices generate persistent scanning and attack traffic without their owners knowledge.

🔍 Check Any IP Address

Share this report: