
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| 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 11 malicious IPs from this autonomous system.
Block scanning from 182.62.224.246: 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.
182.62.224.246 has been assigned a threat score of 75/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.
The following attack categories were identified:
IP address 182.62.224.246 has been traced to Kuala Lumpur, MY, operating on the network of DiGi Telecommunications Sdn Bhd. Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 4 days in our monitoring system, producing 94 flagged requests at a rate of ~23.5/day. The address belongs to a mobile carrier network. The sustained pattern of malicious requests indicates either a compromised device or deliberate abuse. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. Our records show 223 malicious IPs originating from MY, positioning it as a significant contributor to global threat activity. The score of 75/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.
Insecure file upload functionality allows attackers to upload web shells, malware, or scripts that execute on the server. Proper validation must check file content, not just extensions, and uploaded files should be stored outside the web root.
Race conditions occur when application behavior depends on the timing of concurrent operations. Attackers exploit these timing windows to bypass limits, duplicate transactions, or escalate privileges by sending carefully timed parallel requests.