IP Threat Report
192.227.222.17
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger strong hits: 14 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 24 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 27 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Burst: 26 req / 10s | Abnormally fast request rate — automated scanning | +35 |
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.227.222.17 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.227.222.17 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 192.227.222.17.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| CVE ID | Link |
|---|---|
| CVE-2015-5589 | NVD → |
| CVE-2017-11147 | NVD → |
| CVE-2017-11628 | NVD → |
| CVE-2017-9798 | NVD → |
| CVE-2016-4541 | NVD → |
| CVE-2022-37436 | NVD → |
| CVE-2016-4539 | NVD → |
| CVE-2024-42516 | NVD → |
| CVE-2014-5120 | NVD → |
| CVE-2017-3167 | NVD → |
| CVE-2016-5770 | NVD → |
| CVE-2015-2348 | NVD → |
| CVE-2015-6832 | NVD → |
| CVE-2015-4642 | NVD → |
| CVE-2016-6289 | NVD → |
| CVE-2016-8743 | NVD → |
| CVE-2019-10098 | NVD → |
| CVE-2013-7345 | NVD → |
| CVE-2016-2161 | NVD → |
| CVE-2016-6295 | NVD → |
| CVE-2015-4025 | NVD → |
| CVE-2015-6834 | NVD → |
| CVE-2022-31813 | NVD → |
| CVE-2021-44790 | NVD → |
| CVE-2025-68160 | NVD → |
🔴 This host has 374 known CVEs associated with its exposed services. This volume strongly suggests severely outdated software. Review each CVE in the NVD database.
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.227.222.17 has been assigned a threat score of 205/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.
The following attack categories were identified:
📊 Threat Analysis
The address 192.227.222.17 originates from Buffalo, United States, operating on the network of HostPapa. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 2 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~2 requests per day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. The dual attack vectors of User-Agent Anomaly combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. United States currently accounts for 199 blocked IPs in our database, making it a significant source of malicious traffic. A score of 205/100 places this address in the top tier of severity. Block and investigate any historical connections.
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 United States
104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →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.
💡 Zero Trust Architecture Principles
Zero trust eliminates implicit trust based on network location. Every access request is verified regardless of source, minimizing the impact of compromised credentials or network breaches. Implementation requires strong identity verification and continuous authorization.