IP Threat Report
103.121.199.166
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA bot: Go-http-client | Known bot/crawler User-Agent detected | +40 | |
| Danger strong hits: 14 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 6 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 21 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Burst: 9 req / 2s | 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 103.121.199.166 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
🤖 Bot Detection
Address UA spoofing from 103.121.199.166: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 103.121.199.166.
🔎 Directory Scan Defense
IP 103.121.199.166 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
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 |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 3306 | MySQL | High | MySQL database — should never be exposed to the internet |
| 3478 | Unknown | Low | Service on port 3478 |
| 6379 | Redis | Critical | Redis in-memory database — frequently misconfigured without auth |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| 8800 | Unknown | Low | Service on port 8800 |
| 9111 | Unknown | Low | Service on port 9111 |
⚠️ 2 high-risk ports detected on 103.121.199.166. Open database ports suggest possible data exfiltration risk. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2025-59775 | NVD → |
| CVE-2013-0942 | NVD → |
| CVE-2025-14177 | NVD → |
| CVE-2025-6491 | NVD → |
| CVE-2025-1217 | NVD → |
| CVE-2025-23419 | NVD → |
| CVE-2025-1736 | NVD → |
| CVE-2013-0941 | NVD → |
| CVE-2025-14178 | NVD → |
| CVE-2025-1735 | NVD → |
| CVE-2025-1734 | NVD → |
| CVE-2025-1219 | NVD → |
| CVE-2025-66200 | NVD → |
| CVE-2024-3566 | NVD → |
| CVE-2007-3205 | NVD → |
| CVE-2013-4365 | NVD → |
| CVE-2011-2688 | NVD → |
| CVE-2012-4001 | NVD → |
| CVE-2012-3526 | NVD → |
| CVE-2007-4723 | NVD → |
| CVE-2025-58098 | NVD → |
| CVE-2025-55753 | NVD → |
| CVE-2012-4360 | NVD → |
| CVE-2009-0796 | NVD → |
| CVE-2025-1220 | NVD → |
🔴 Security scanning identified 32 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
103.121.199.166 has been assigned a threat score of 230/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
Our monitoring infrastructure has identified 103.121.199.166, geolocated to Caringin, Indonesia, operating on the network of PT Parsaoran Global Datatrans, as a source of suspicious network activity. During its 1-day observation window, we recorded 2 hostile requests from this IP — roughly 2 per day on average. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. Our records show 101 malicious IPs originating from Indonesia, positioning it as a significant contributor to global threat activity. A score of 230/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 Indonesia
157.15.40.88 (340)203.175.125.130 (340)157.15.40.93 (340)157.15.40.62 (340)157.15.40.89 (340)View all →Security Intelligence
💡 HTTP Header Analysis for Threat Detection
Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.
💡 Data Center IP Reputation
IPs originating from data centers and hosting providers account for a disproportionate amount of malicious traffic. Compromised VPS instances, bulletproof hosting, and abused trial accounts create persistent attack infrastructure that can be difficult to shut down.