
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 | |
| Directory Scan | Behavioral anomaly detected by automated analysis | +0 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Block scanning from 196.240.38.142: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
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.
196.240.38.142 has been assigned a threat score of 85/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.
The following attack categories were identified:
196.240.38.142 is registered in Mexico City, Mexico, operating on the network of Orion Network Limited. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 1,243 malicious requests from this address across a 13-day span, reflecting a sustained attack cadence of ~95.6 requests per day. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 101 flagged addresses, Mexico represents a significant presence in our threat database. At 85/100, this IP warrants immediate defensive action.
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.
SSH servers face constant brute force attacks targeting common usernames and weak passwords. Key-based authentication, fail2ban, non-standard ports, and IP allowlisting dramatically reduce the attack surface. Monitoring auth logs reveals active campaigns and compromised credentials.