
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Imported from old blocklist | Behavioral anomaly detected by automated analysis | +0 | |
| Danger medium hits: 10 | Medium-risk: admin panels, config files | +60 | |
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger medium hits: 16 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 5 | Medium-risk: admin panels, config files | +50 | |
| Danger medium hits: 20 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 30 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 12 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 22 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 36 | Medium-risk: admin panels, config files | +60 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 103.28.0.58 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
IP 103.28.0.58 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 2000 | Unknown | Low | Service on port 2000 |
| 8291 | MikroTik | High | MikroTik Winbox — router management, targeted by VPNFilter malware |
⚠️ 1 high-risk port detected on 103.28.0.58. These services should not be publicly accessible without strict firewall rules.
Data source: Shodan InternetDB. Scanned independently of abuse.mom.
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.
103.28.0.58 has been assigned a threat score of 130/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.
The following attack categories were identified:
Our monitoring infrastructure has identified 103.28.0.58, geolocated to Phnom Penh, KH, operating on the network of Wingel cooperation co., Ltd, as a source of suspicious network activity. Over a period of 67 days, this IP generated 228 malicious requests, averaging approximately 3.4 requests per day. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 65 malicious IPs originating from KH, positioning it as a notable contributor to global threat activity. A score of 130/100 places this address in the top tier of severity. Block and investigate any historical connections.
This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.
RCE vulnerabilities allow attackers to execute arbitrary code on target servers. These critical flaws often arise from deserialization bugs, template injection, or file upload vulnerabilities, and represent the highest severity class of web application weaknesses.
Subdomain takeover occurs when DNS records point to decommissioned services. Attackers claim the abandoned resource and serve content under the trusted domain, enabling cookie theft, phishing, and reputation damage.