
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| 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 70 malicious IPs from this autonomous system.
IP 222.127.60.136 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
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.
222.127.60.136 has been assigned a threat score of 60/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.
The following attack categories were identified:
IP address 222.127.60.136 has been traced to Lahug, Philippines, operating on the network of Globe Telecom. Our threat detection systems have flagged this address based on observed malicious behavior patterns. During its 3-day observation window, we recorded 83 hostile requests from this IP — roughly 27.7 per day on average. This is a mobile network IP. While mobile addresses are typically shared via CGNAT, persistent malicious activity from this specific address suggests automated abuse. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. Philippines currently accounts for 741 blocked IPs in our database, making it a major source of malicious traffic. At 60/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.
Brute force attacks systematically try username and password combinations to gain unauthorized access. Modern attacks leverage credential databases from previous breaches, testing millions of combinations using distributed botnets across multiple IP addresses.
Responsible disclosure balances public safety with giving vendors time to patch vulnerabilities. The security community generally supports coordinated disclosure timelines, but disagreements about appropriate timeframes and full disclosure continue to drive policy debates.