
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Burst: 14 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 14 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Foreign referer seen | Referer from unrelated external domain | +10 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Address UA spoofing from 164.92.184.104: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
IP 164.92.184.104 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
IP 164.92.184.104 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
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 |
| 3306 | MySQL | High | MySQL database — should never be exposed to the internet |
⚠️ 1 high-risk port detected on 164.92.184.104. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2013-2765 | NVD → |
| CVE-2012-4001 | NVD → |
| CVE-2022-22721 | NVD → |
| CVE-2024-38473 | NVD → |
| CVE-2024-38475 | NVD → |
| CVE-2022-36760 | NVD → |
| CVE-2022-30556 | NVD → |
| CVE-2007-4723 | NVD → |
| CVE-2023-38709 | NVD → |
| CVE-2022-31813 | NVD → |
| CVE-2025-55753 | NVD → |
| CVE-2025-65082 | NVD → |
| CVE-2022-37436 | NVD → |
| CVE-2025-66200 | NVD → |
| CVE-2025-49812 | NVD → |
| CVE-2022-26377 | NVD → |
| CVE-2013-0942 | NVD → |
| CVE-2024-47252 | NVD → |
| CVE-2024-38472 | NVD → |
| CVE-2024-27316 | NVD → |
| CVE-2022-22719 | NVD → |
| CVE-2025-58098 | NVD → |
| CVE-2013-4365 | NVD → |
| CVE-2025-59775 | NVD → |
| CVE-2024-43394 | NVD → |
🔴 This host has 54 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.
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.
164.92.184.104 has been assigned a threat score of 180/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:
164.92.184.104 is registered in Frankfurt am Main, Germany, operating on the network of DigitalOcean, LLC. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. During its 1-day observation window, we recorded 3 hostile requests from this IP — roughly 3 per day on average. 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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. Germany currently accounts for 102 blocked IPs in our database, making it a significant source of malicious traffic. At 180/100, this is an extremely high-risk address. All traffic should be considered hostile.
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.
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.
XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.