IP Threat Report
160.187.121.26
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| 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 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 |
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 160.187.121.26 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 160.187.121.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🔎 Directory Scan Defense
IP 160.187.121.26 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Neighbors in 160.187.121.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 |
|---|---|---|---|
| 12436 | Unknown | Low | Service on port 12436 |
| 12441 | Unknown | Low | Service on port 12441 |
| 12444 | Unknown | Low | Service on port 12444 |
| 12451 | Unknown | Low | Service on port 12451 |
| 12455 | Unknown | Low | Service on port 12455 |
| 12465 | Unknown | Low | Service on port 12465 |
| 12479 | Unknown | Low | Service on port 12479 |
| 12481 | Unknown | Low | Service on port 12481 |
| 12485 | Unknown | Low | Service on port 12485 |
| 12486 | Unknown | Low | Service on port 12486 |
| 12487 | Unknown | Low | Service on port 12487 |
| 12489 | Unknown | Low | Service on port 12489 |
| 12494 | Unknown | Low | Service on port 12494 |
| 12499 | Unknown | Low | Service on port 12499 |
| 12502 | Unknown | Low | Service on port 12502 |
| 12503 | Unknown | Low | Service on port 12503 |
| 12511 | Unknown | Low | Service on port 12511 |
| 12512 | Unknown | Low | Service on port 12512 |
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
160.187.121.26 has been assigned a threat score of 105/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.
The following attack categories were identified:
📊 Threat Analysis
Threat intelligence analysis has linked 160.187.121.26 to malicious activity originating from Hanoi, Vietnam, operating on the network of Lienvps Technology Company Limited. The address has been under observation since its initial detection. Over a period of 49 days, this IP generated 4 malicious requests, averaging approximately 0.1 requests per day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. Our records show 140 malicious IPs originating from Vietnam, positioning it as a significant contributor to global threat activity. At 105/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.
Related Threats
Security Intelligence
💡 Prototype Pollution Attacks
Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.
💡 TLS Certificate Misconfigurations
Expired, self-signed, or misconfigured TLS certificates create security vulnerabilities and trust issues. Certificate monitoring, automated renewal through ACME protocols, and proper certificate chain configuration prevent both security gaps and service disruptions.