
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 36 | Medium-risk: admin panels, config files | +60 | |
| 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 4068 malicious IPs from this autonomous system.
Add 159.89.206.129 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.
159.89.206.129 has been assigned a threat score of 170/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.
159.89.206.129 is registered in Singapore, Singapore, operating on the network of DigitalOcean, LLC. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. During its 2-day observation window, we recorded 31 hostile requests from this IP — roughly 15.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. Singapore currently accounts for 5,127 blocked IPs in our database, making it a major source of malicious traffic. With a threat score of 170/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
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.
Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.
Cross-Origin Resource Sharing misconfigurations can expose sensitive APIs to unauthorized origins. Wildcard policies, reflected origins, and null origin allowlisting create vulnerabilities that attackers exploit for data theft and unauthorized actions.