
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 3 | Medium-risk: admin panels, config files | +30 |
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 103.59.160.82: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 111 | Unknown | Low | Service on port 111 |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 2379 | Unknown | Low | Service on port 2379 |
| 6443 | Unknown | Low | Service on port 6443 |
| 10250 | Unknown | Low | Service on port 10250 |
| CVE ID | Link |
|---|---|
| CVE-2025-26465 | NVD → |
| CVE-2023-51767 | NVD → |
| CVE-2016-20012 | NVD → |
| CVE-2023-48795 | NVD → |
| CVE-2021-41617 | NVD → |
| CVE-2008-3844 | NVD → |
| CVE-2007-2768 | NVD → |
| CVE-2021-36368 | NVD → |
| CVE-2025-32728 | NVD → |
| CVE-2024-6387 | NVD → |
| CVE-2023-38408 | NVD → |
| CVE-2023-51385 | NVD → |
🔴 This host has 12 known CVEs associated with its exposed services. This volume strongly suggests severely outdated software. Review each CVE in the NVD database.
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.59.160.82 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:
Network traffic from 103.59.160.82, located in Kediri, Indonesia, operating on the network of PT Gunung Sedayu Sentosa, has been classified as malicious by our automated threat scoring engine. The address has been active for 2 days in our monitoring system, producing 43 flagged requests at a rate of ~21.5/day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. With 103 flagged addresses, Indonesia represents a significant presence in our threat database. 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.
SQL injection remains one of the most common web attack vectors. Attackers inject malicious SQL code through input fields to extract database contents, modify data, or gain administrative access. Automated scanners test for SQLi vulnerabilities at massive scale.
Immutable, offline backups remain the most effective defense against ransomware. The 3-2-1 rule — three copies on two media types with one offsite — combined with regular recovery testing ensures business continuity after encryption attacks.