ABUSE.MOM
THREAT REPORT

IP Threat Report
91.92.241.188

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:56:39
First seen: 2026-05-13 01:00:06
Last seen: 2026-05-16 15:00:05
80

⛔ Verdict: BLOCK

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

BOT_UADANGER_PATHRATIO_404UA_CHANGEDREDIRECT_PROBE
01

Geolocation & Classification

IP Address
91.92.241.188
Type
Residential
Country
🇳🇱 Netherlands
City
Amsterdam
ISP
Omegatech LTD
Organization
Omegatech LTD
Autonomous System
AS202412 Omegatech LTD
Hit Count
7
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: javaKnown bot/crawler User-Agent detected+40
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
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger medium hits: 2Medium-risk: admin panels, config files+20
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Σ = 180
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-05-13 01:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: java (+40), Danger strong hits: 1 (+25), Danger medium hits: 1 (+10)
2026-05-16 15:00:05
Last malicious request observed
Total score reached: 80/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Omegatech LTD
AS202412 · 🇳🇱 Netherlands
06

Recommendations

Actions taken & recommended

  • IP 91.92.241.188 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Other malicious IPs detected in the same /24 subnet — consider blocking 91.92.241.0/24
  • 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 91.92.241.188: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

🔎 Path Enumeration Protection

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

07

Neighbors in 91.92.241.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

08

Open Ports & Services

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

OPEN PORTS (2)
PortServiceRiskDescription
22SSHLowSecure Shell — common brute force target for remote access
3001UnknownLowService on port 3001
DETECTED TECHNOLOGIES
canonical:ubuntu_linuxopenbsd:openssh:8.2p1

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.

⛔ 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

91.92.241.188 has been assigned a threat score of 80/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

User-Agent AnomalyPath Enumeration

📊 Threat Analysis

Threat intelligence analysis has linked 91.92.241.188 to malicious activity originating from Amsterdam, Netherlands, operating on the network of Omegatech LTD. The address has been under observation since its initial detection. Our sensors captured 7 malicious requests from this address across a 3-day span, reflecting a sustained attack cadence of ~2.3 requests per day. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. Two attack patterns were identified (User-Agent Anomaly and Path Enumeration), suggesting a semi-automated campaign that targets multiple vulnerabilities. Netherlands currently accounts for 113 blocked IPs in our database, making it a significant source of malicious traffic. The score of 80/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.

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 Netherlands

185.184.192.251 (338)45.88.138.44 (320)45.82.64.236 (315)5.181.169.192 (313)157.22.73.141 (313)View all →

🏢 Same network: AS202412

178.16.55.142 (300)158.94.208.149 (295)158.94.211.226 (253)158.94.210.233 (238)130.12.180.90 (210)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.

💡 Satellite Internet Security

Satellite internet introduces unique security challenges including high latency that affects real-time threat detection, shared bandwidth that enables traffic sniffing, and coverage areas that cross multiple jurisdictions complicating legal response.

🔍 Check Any IP Address

Share this report: