IP Threat Report
206.189.37.160
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA bot: python | Known bot/crawler User-Agent detected | +40 | |
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 |
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 206.189.37.160 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 206.189.37.0/24
- 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 206.189.37.160 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
🔎 Directory Scan Defense
IP 206.189.37.160 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Neighbors in 206.189.37.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 |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 27017 | MongoDB | Critical | MongoDB — commonly found exposed without authentication |
⚠️ Network scanning reveals 1 dangerous service exposed on 206.189.37.160. Open database ports suggest possible data exfiltration risk. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2022-3996 | NVD → |
| CVE-2026-25610 | NVD → |
| CVE-2026-22796 | NVD → |
| CVE-2009-3765 | NVD → |
| CVE-2024-0727 | NVD → |
| CVE-2023-0464 | NVD → |
| CVE-2025-6706 | NVD → |
| CVE-2025-6711 | NVD → |
| CVE-2026-22795 | NVD → |
| CVE-2024-6375 | NVD → |
| CVE-2023-0465 | NVD → |
| CVE-2024-3372 | NVD → |
| CVE-2023-5363 | NVD → |
| CVE-2022-4450 | NVD → |
| CVE-2022-1434 | NVD → |
| CVE-2025-11979 | NVD → |
| CVE-2023-0466 | NVD → |
| CVE-2024-6119 | NVD → |
| CVE-2014-8180 | NVD → |
| CVE-2025-3083 | NVD → |
| CVE-2025-14847 | NVD → |
| CVE-2025-6707 | NVD → |
| CVE-2024-6384 | NVD → |
| CVE-2025-69420 | NVD → |
| CVE-2009-3767 | NVD → |
🔴 Security scanning identified 81 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
206.189.37.160 has been assigned a threat score of 175/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:
📊 Threat Analysis
Threat intelligence analysis has linked 206.189.37.160 to malicious activity originating from Singapore, Singapore, operating on the network of DigitalOcean, LLC. The address has been under observation since its initial detection. During its 19-day observation window, we recorded 3 hostile requests from this IP — roughly 0.2 per day on average. 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. Two attack patterns were identified (User-Agent Anomaly and Path Enumeration), suggesting a semi-automated campaign that targets multiple vulnerabilities. With 141 flagged addresses, Singapore represents a significant presence in our threat database. A score of 175/100 places this address in the top tier of severity. Block and investigate any historical connections.
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
💡 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.
💡 Emerging Threats from AI-Powered Attacks
Artificial intelligence enables more convincing phishing content, faster vulnerability discovery, and adaptive attack strategies that learn from defensive responses. AI-generated social engineering and automated exploit development represent growing threats.