IP Threat Report
91.98.178.11
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Burst: 13 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 13 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Foreign referer seen | Referer from unrelated external domain | +10 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
Recommendations
Actions taken & recommended
- IP 91.98.178.11 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.98.178.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🌊 Traffic Flood Defense
IP 91.98.178.11 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Neighbors in 91.98.178.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 1024 | Unknown | Low | Service on port 1024 |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| 8443 | HTTPS-Alt | Low | Service on port 8443 |
| 9090 | Unknown | Low | Service on port 9090 |
| 9100 | Unknown | Low | Service on port 9100 |
| 10000 | Unknown | Low | Service on port 10000 |
Data source: Shodan InternetDB. Scanned independently of abuse.mom.
Blacklist Status (DNSBL)
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
Threat Analysis
91.98.178.11 has been assigned a threat score of 130/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:
📊 Threat Analysis
Network traffic from 91.98.178.11, located in Falkenstein, Germany, operating on the network of Hetzner Online GmbH, has been classified as malicious by our automated threat scoring engine. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The IP is engaged in request flooding, sending traffic at rates designed to exhaust server capacity. With 63 flagged addresses, Germany represents a notable presence in our threat database. A score of 130/100 places this address in the top tier of severity. Block and investigate any historical connections.
This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.
Related Threats
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.
💡 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.