ABUSE.MOM
THREAT REPORT

IP Threat Report
176.11.0.190

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 13:07:24
First seen: 2026-04-09 10:00:07
Last seen: 2026-04-09 10:00:07
68

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404METHOD
01

Geolocation & Classification

IP Address
176.11.0.190
Type
Mobile
Country
🇳🇴 Norway
City
Oslo
ISP
NetCom Mobile Broadband
Organization
Unknown
Autonomous System
AS25400 Telia Norge AS
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger medium hits: 1Medium-risk: admin panels, config files+10
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
POST requests presentBehavioral anomaly detected by automated analysis+8
Σ = 68
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-04-09 10:00:07
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 1 (+25), Danger medium hits: 1 (+10), 404 ratio >= 60% (+25)
2026-04-09 10:00:07
Last malicious request observed
Total score reached: 68/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

NetCom Mobile Broadband
AS25400 · 🇳🇴 Norway
06

Recommendations

Actions taken & recommended

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

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

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

10

Threat Analysis

176.11.0.190 has been assigned a threat score of 68/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

Threat intelligence analysis has linked 176.11.0.190 to malicious activity originating from Oslo, Norway, operating on the network of NetCom Mobile Broadband. The address has been under observation since its initial detection. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. This is a mobile network IP. While mobile addresses are typically shared via CGNAT, persistent malicious activity from this specific address suggests automated abuse. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 107 flagged addresses, Norway represents a significant presence in our threat database. At 68/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.

11

Related Threats

🇳🇴 Top threats from Norway

45.13.191.15 (305)20.100.191.215 (280)20.100.195.34 (280)20.100.193.95 (280)20.100.192.217 (280)View all →

🏢 Same network: AS25400

178.232.37.128 (70)46.212.111.230 (70)84.215.107.152 (70)84.212.201.19 (70)84.213.186.95 (70)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.

💡 GraphQL Security Risks

GraphQL APIs introduce specific vulnerabilities including introspection information disclosure, query complexity attacks, batching abuse, and authorization bypass through nested queries. Depth limiting, cost analysis, and field-level authorization address these GraphQL-specific threats.

🔍 Check Any IP Address

Share this report: