IP Threat Report
192.236.146.245
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 |
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 192.236.146.245 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
🤖 User-Agent Anomaly Defense
IP 192.236.146.245 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
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 |
| 25 | SMTP | Medium | SMTP mail server — can be abused for spam relay |
| 1234 | Unknown | Low | Service on port 1234 |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| CVE ID | Link |
|---|---|
| CVE-2008-3844 | NVD → |
| CVE-2025-26465 | NVD → |
| CVE-2023-51767 | NVD → |
| CVE-2023-51385 | NVD → |
| CVE-2016-20012 | NVD → |
| CVE-2025-32728 | NVD → |
| CVE-2021-41617 | NVD → |
| CVE-2007-2768 | NVD → |
| CVE-2021-36368 | NVD → |
| CVE-2023-38408 | NVD → |
| CVE-2023-48795 | NVD → |
| CVE-2024-6387 | NVD → |
🔴 Security scanning identified 12 vulnerability entries on this host. This volume strongly suggests severely outdated software. Consult NVD advisories for details.
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
192.236.146.245 has been assigned a threat score of 65/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.
The following attack categories were identified:
📊 Threat Analysis
IP address 192.236.146.245 has been traced to Amsterdam, Netherlands, operating on the network of Hostwinds LLC.. Our threat detection systems have flagged this address based on observed malicious behavior patterns. During its 3-day observation window, we recorded 2 hostile requests from this IP — roughly 0.7 per day on average. 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. Detected suspicious User-Agent anomalies including empty, forged, or rapidly rotating UA strings — characteristic of automated scanning tools. Our records show 101 malicious IPs originating from Netherlands, positioning it as a significant contributor to global threat activity. At 65/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.
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.
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: AS54290
View all →Security Intelligence
💡 User-Agent Analysis Techniques
Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.
💡 GeoIP Blocking Considerations
Blocking traffic from specific countries reduces attack surface but impacts legitimate international users. Effective geo-based policies use tiered approaches — blocking, rate limiting, or requiring additional verification based on risk assessment.