
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| 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 11 malicious IPs from this autonomous system.
Add 162.240.156.176 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.
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.
162.240.156.176 has been assigned a threat score of 150/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
Threat intelligence analysis has linked 162.240.156.176 to malicious activity originating from Phoenix, United States, operating on the network of Unified Layer. The address has been under observation since its initial detection. During its 2-day observation window, we recorded 67 hostile requests from this IP — roughly 33.5 per day on average. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. With 36,230 flagged addresses, United States represents a major presence in our threat database. At 150/100, this is an extremely high-risk address. All traffic should be considered hostile.
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.
XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.
Command injection occurs when attackers insert operating system commands through application inputs. Successful exploitation grants direct server access, enabling data theft, malware installation, and lateral movement across networks.