
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 107.175.39.20: 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.
107.175.39.20 has been assigned a threat score of 130/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 107.175.39.20 to malicious activity originating from Buffalo, United States, operating on the network of HostPapa. The address has been under observation since its initial detection. The address has been active for 29 days in our monitoring system, producing 1,253 flagged requests at a rate of ~43.2/day. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 101 flagged addresses, United States represents a significant presence in our threat database. At 130/100, this is an extremely high-risk address. All traffic should be considered hostile.
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.
The impact of data breaches extends beyond immediate financial losses. Regulatory fines, legal liability, reputational damage, and customer churn create long-term costs that often exceed the direct costs of incident response and remediation.