
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst 11/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 12/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 13/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 19/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 6/2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 24 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| POST seen | Behavioral anomaly detected by automated analysis | +8 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 | |
| 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.
IP 160.153.182.242 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
IP 160.153.182.242 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Address UA spoofing from 160.153.182.242: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
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.
160.153.182.242 has been assigned a threat score of 215/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.
The following attack categories were identified:
Network traffic from 160.153.182.242, located in Tempe, United States, operating on the network of GoDaddy.com, LLC, has been classified as malicious by our automated threat scoring engine. During its 8-day observation window, we recorded 172 hostile requests from this IP — roughly 21.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 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. With 105 flagged addresses, United States represents a significant presence in our threat database. With a threat score of 215/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.
Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.
Certificate Transparency logs record all publicly trusted TLS certificates. Monitoring these logs reveals unauthorized certificate issuance, phishing domain preparation, and shadow IT — providing early warning of attacks targeting an organizations domain.