
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.
IP 91.92.40.39 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
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.
91.92.40.39 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 91.92.40.39 has been traced to Varna, Bulgaria, operating on the network of BULLETGROUP. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Over a period of 5 days, this IP generated 31 malicious requests, averaging approximately 6.2 requests per day. This IP is identified as a VPN or proxy endpoint, commonly used to mask the true origin of attack traffic and bypass geographic or reputation-based blocking. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 68 flagged addresses, Bulgaria represents a notable presence in our threat database. The score of 60/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.
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.
CDNs can inadvertently mask the true origin of malicious traffic, making attribution difficult. Attackers abuse CDN services to proxy their attacks, leverage cached content for amplification, and exploit misconfigurations in CDN-to-origin connections.