
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 146.190.104.0 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
IP 146.190.104.0 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
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 |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 111 | Unknown | Low | Service on port 111 |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 3306 | MySQL | High | MySQL database — should never be exposed to the internet |
| 5000 | Unknown | Low | Service on port 5000 |
| 8888 | HTTP-Alt | Low | Service on port 8888 |
⚠️ 1 high-risk port detected on 146.190.104.0. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2008-3844 | NVD → |
| CVE-2007-2768 | NVD → |
| CVE-2023-38408 | NVD → |
| CVE-2023-48795 | NVD → |
| CVE-2025-26465 | NVD → |
| CVE-2018-15473 | NVD → |
| CVE-2023-51385 | NVD → |
| CVE-2019-6111 | NVD → |
| CVE-2020-15778 | NVD → |
| CVE-2021-41617 | NVD → |
| CVE-2016-20012 | NVD → |
| CVE-2025-23419 | NVD → |
| CVE-2017-15906 | NVD → |
| CVE-2019-6110 | NVD → |
| CVE-2018-20685 | NVD → |
| CVE-2019-6109 | NVD → |
| CVE-2021-3618 | NVD → |
| CVE-2020-14145 | NVD → |
| CVE-2018-15919 | NVD → |
| CVE-2025-32728 | NVD → |
| CVE-2021-36368 | NVD → |
| CVE-2023-51767 | NVD → |
| CVE-2023-44487 | NVD → |
🔴 This host has 23 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.
146.190.104.0 has been assigned a threat score of 110/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.
The following attack categories were identified:
The address 146.190.104.0 originates from Singapore, Singapore, operating on the network of DigitalOcean, LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 1 days, this IP generated 2 malicious requests, averaging approximately 2 requests per day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Two attack patterns were identified (User-Agent Anomaly and Path Enumeration), suggesting a semi-automated campaign that targets multiple vulnerabilities. With 140 flagged addresses, Singapore represents a significant presence in our threat database. At 110/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.
Credential stuffing uses stolen username-password pairs from data breaches to attempt logins across many websites. Since users frequently reuse passwords, these automated attacks achieve success rates of 0.1-2%, which translates to thousands of compromised accounts from millions of attempts.