
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 |
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 6580 malicious IPs from this autonomous system.
Add 189.75.178.49 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.
189.75.178.49 has been assigned a threat score of 60/100 (High). The IP is rated as a high-level threat. Network administrators should implement blocking rules and monitor for any connections from this address.
Threat intelligence analysis has linked 189.75.178.49 to malicious activity originating from Albuquerque, United States, operating on the network of F.N.S. HOLDINGS LIMITED. The address has been under observation since its initial detection. Over a period of 3 days, this IP generated 53 malicious requests, averaging approximately 17.7 requests per day. This IP is identified as a VPN or proxy endpoint, commonly used to mask the true origin of attack traffic and bypass geographic or reputation-based blocking. With 36,339 flagged addresses, United States represents a major presence in our threat database. At 60/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.
This IP is associated with a VPN or proxy service. Attackers frequently route their traffic through anonymizing services to obscure their true location. This makes attribution more challenging but the malicious behavior patterns remain detectable.
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.