
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Add 168.144.100.28 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.
168.144.100.28 has been assigned a threat score of 95/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
Network traffic from 168.144.100.28, located in Singapore, Singapore, operating on the network of DigitalOcean, LLC, has been classified as malicious by our automated threat scoring engine. Our sensors captured 88 malicious requests from this address across a 2-day span, reflecting a sustained attack cadence of ~44 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. Our records show 166 malicious IPs originating from Singapore, positioning it as a significant contributor to global threat activity. A score of 95/100 places this address in the top tier of severity. Block and investigate any historical connections.
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.
SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.
Automated response systems can block threats in milliseconds, far faster than human analysts. However, automation requires careful safeguards — rate limits on blocking actions, automatic expiration, and human review queues prevent automated systems from causing self-inflicted outages.