IP Threat Report
103.18.232.156
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 | |
| 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 | |
| Imported from old blocklist | Behavioral anomaly detected by automated analysis | +0 | |
| Danger medium hits: 10 | Medium-risk: admin panels, config files | +60 | |
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger medium hits: 16 | 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 103.18.232.156 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
🔎 Path Enumeration Protection
Block scanning from 103.18.232.156: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🤖 Bot Detection
Address UA spoofing from 103.18.232.156: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 161 | Unknown | Low | Service on port 161 |
| 2000 | Unknown | Low | Service on port 2000 |
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.18.232.156 has been assigned a threat score of 130/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
The following attack categories were identified:
📊 Threat Analysis
Threat intelligence analysis has linked 103.18.232.156 to malicious activity originating from Demak, Indonesia, operating on the network of PT JARINGANKU SARANA NUSANTARA. The address has been under observation since its initial detection. The address has been active for 18 days in our monitoring system, producing 26 flagged requests at a rate of ~1.4/day. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. The dual attack vectors of Path Enumeration combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. Indonesia currently accounts for 102 blocked IPs in our database, making it a significant source of malicious traffic. At 130/100, this is an extremely high-risk address. All traffic should be considered hostile.
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
💡 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.
💡 Residential Proxy Networks
Residential proxies route traffic through real home internet connections, making malicious traffic appear to come from legitimate users. Some networks install proxy software bundled with free applications, unknowingly conscripting millions of devices.