ABUSE.MOM
THREAT REPORT

IP Threat Report
206.12.127.34

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-19 05:09:48
First seen: 2026-07-16 00:03:46
Last seen: 2026-07-19 04:07:55
85

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

IP Address
206.12.127.34
Type
Residential
Country
🇨🇦 Canada
City
Burnaby
ISP
Simon Fraser University
Organization
BCNET
Autonomous System
AS11105 Simon Fraser University
Hit Count
204
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 85
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-07-16 00:03:46
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger strong hits: 2 (+50), Probe 302→404 (+20)
2026-07-19 04:07:55
Last malicious request observed
Total score reached: 85/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Simon Fraser University
AS11105 · 🇨🇦 Canada
06

Recommendations

Actions taken & recommended

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

🔎 Directory Scan Defense

IP 206.12.127.34 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

206.12.127.34 has been assigned a threat score of 85/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:

Path Enumeration

📊 Threat Analysis

Network traffic from 206.12.127.34, located in Burnaby, Canada, operating on the network of Simon Fraser University, has been classified as malicious by our automated threat scoring engine. During its 3-day observation window, we recorded 204 hostile requests from this IP — roughly 68 per day on average. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 101 flagged addresses, Canada represents a significant presence in our threat database. At 85/100, this IP warrants immediate defensive action.

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.179.130 (308)20.151.111.128 (308)45.91.23.64 (305)45.91.23.164 (305)147.15.149.40 (300)View all →

🏢 Same network: AS11105

View all →
12

Security Intelligence

💡 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.

💡 Data Center IP Reputation

IPs originating from data centers and hosting providers account for a disproportionate amount of malicious traffic. Compromised VPS instances, bulletproof hosting, and abused trial accounts create persistent attack infrastructure that can be difficult to shut down.

🔍 Check Any IP Address

Share this report: