
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Danger medium hits: 5 | Medium-risk: admin panels, config files | +50 | |
| 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.
IP 193.151.190.181 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.
193.151.190.181 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.
The following attack categories were identified:
Threat intelligence analysis has linked 193.151.190.181 to malicious activity originating from Amsterdam, Netherlands, operating on the network of Alex Largman. The address has been under observation since its initial detection. Over a period of 4 days, this IP generated 489 malicious requests, averaging approximately 122.3 requests per day. The address operates as a VPN/proxy exit node. Attackers route traffic through anonymizing services to obscure their real location and evade IP-based security controls. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. With 35 flagged addresses, Netherlands represents a notable presence in our threat database. A score of 95/100 places this address in the top tier of severity. Block and investigate any historical connections.
This IP is associated with a VPN or proxy service. Attackers frequently route their traffic through anonymizing services to obscure their true location. This makes attribution more challenging but the malicious behavior patterns remain detectable.
Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.
Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.