
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Foreign referer | 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.
We have detected 237 malicious IPs from this autonomous system.
Block scanning from 180.252.161.117: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
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.
180.252.161.117 has been assigned a threat score of 60/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.
The following attack categories were identified:
180.252.161.117 is registered in Tangerang, Indonesia, operating on the network of PT. TELKOM INDONESIA. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. The address has been active for 1 days in our monitoring system, producing 55 flagged requests at a rate of ~55/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. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. Our records show 1,098 malicious IPs originating from Indonesia, positioning it as a major contributor to global threat activity. The score of 60/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.
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.
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.
When multiple IPs in a subnet show malicious behavior, subnet blocking efficiently neutralizes the threat. However, overly broad blocking risks impacting legitimate users. Analysis of subnet ownership and historical behavior guides appropriate blocking scope.