ABUSE.MOM
THREAT REPORT

IP Threat Report
38.113.182.191

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-26 02:55:26
First seen: 2026-09-10 16:51:31
Last seen: 2026-09-13 01:16:58
95

⛔ Verdict: BLOCK

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

DANGER_PATH
01

Geolocation & Classification

IP Address
38.113.182.191
Type
Residential
Country
🇨🇦 Canada
City
Mississauga
ISP
Cogent Communications
Organization
Nology Solutions ( ONTARIO INC)
Autonomous System
AS174 Cogent Communications, LLC
Hit Count
65
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Σ = 95
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-09-10 16:51:31
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 2 (+20), Danger strong hits: 3 (+75)
2026-09-13 01:16:58
Last malicious request observed
Total score reached: 95/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Cogent Communications
AS174 · 🇨🇦 Canada

We have detected 100 malicious IPs from this autonomous system.

View all IPs from AS174 →
06

Recommendations

Actions taken & recommended

  • IP 38.113.182.191 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 38.113.182.191 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
bl.blocklist.de
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
cbl.abuseat.org
✓ Clean
zen.spamhaus.org
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

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

📊 Threat Analysis

Network traffic from 38.113.182.191, located in Mississauga, Canada, operating on the network of Cogent Communications, has been classified as malicious by our automated threat scoring engine. Our sensors captured 65 malicious requests from this address across a 2-day span, reflecting a sustained attack cadence of ~32.5 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. With 2,584 flagged addresses, Canada represents a major presence in our threat database. At 95/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.200.44 (315)20.151.179.130 (308)20.151.111.128 (308)45.91.23.64 (305)45.91.23.164 (305)View all →

🏢 Same network: AS174

38.213.66.181 (193)181.41.206.235 (100)154.13.90.176 (95)154.21.111.252 (95)154.21.39.210 (95)View all →
12

Security Intelligence

💡 Server-Side Request Forgery (SSRF)

SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.

💡 CORS Misconfiguration Exploitation

Cross-Origin Resource Sharing misconfigurations can expose sensitive APIs to unauthorized origins. Wildcard policies, reflected origins, and null origin allowlisting create vulnerabilities that attackers exploit for data theft and unauthorized actions.

🔍 Check Any IP Address

Share this report: