
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 10 | Medium-risk: admin panels, config files | +60 | |
| Foreign referer seen | Referer from unrelated external domain | +10 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Add 114.10.47.143 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
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.
114.10.47.143 has been assigned a threat score of 70/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.
The address 114.10.47.143 originates from Surabaya, Indonesia, operating on the network of PT. INDOSAT Tbk. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per day. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. Our records show 120 malicious IPs originating from Indonesia, positioning it as a significant contributor to global threat activity. The score of 70/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.
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.
Edge computing pushes processing closer to users but expands the attack surface. Edge nodes often run in less secure environments than centralized data centers, creating new opportunities for physical access attacks and supply chain compromises.
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.