
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| UA suspicious | Behavioral anomaly detected by automated analysis | +15 |
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 7024 malicious IPs from this autonomous system.
IP 170.64.238.146 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
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.
170.64.238.146 has been assigned a threat score of 85/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.
The following attack categories were identified:
IP address 170.64.238.146 has been traced to Sydney, Australia, operating on the network of DigitalOcean, LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Over a period of 4 days, this IP generated 136 malicious requests, averaging approximately 34 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. Detected suspicious User-Agent anomalies including empty, forged, or rapidly rotating UA strings — characteristic of automated scanning tools. With 1,248 flagged addresses, Australia represents a major presence in our threat database. The score of 85/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.
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.
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.
SSTI occurs when user input is embedded in server-side templates without sanitization. Successful exploitation often leads to remote code execution, as template engines typically have access to powerful server-side functionality.