
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger strong hits: 15 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 10 | Medium-risk: admin panels, config files | +60 | |
| Burst: 14 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Imported from old blocklist | Behavioral anomaly detected by automated analysis | +0 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 157.20.32.165 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
IP 157.20.32.165 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 23 | Telnet | Critical | Telnet — unencrypted remote access, extremely dangerous if exposed |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 2000 | Unknown | Low | Service on port 2000 |
| 3000 | Unknown | Low | Service on port 3000 |
⚠️ Network scanning reveals 1 dangerous service exposed on 157.20.32.165. Telnet (23) transmits credentials in plaintext — likely a compromised IoT device. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2024-38474 | NVD → |
| CVE-2013-4365 | NVD → |
| CVE-2024-38475 | NVD → |
| CVE-2025-59775 | NVD → |
| CVE-2011-2688 | NVD → |
| CVE-2025-55753 | NVD → |
| CVE-2013-0942 | NVD → |
| CVE-2007-4723 | NVD → |
| CVE-2024-24795 | NVD → |
| CVE-2024-36387 | NVD → |
| CVE-2024-27316 | NVD → |
| CVE-2013-0941 | NVD → |
| CVE-2012-3526 | NVD → |
| CVE-2025-58098 | NVD → |
| CVE-2023-38709 | NVD → |
| CVE-2024-38476 | NVD → |
| CVE-2025-23419 | NVD → |
| CVE-2024-42516 | NVD → |
| CVE-2025-49630 | NVD → |
| CVE-2025-66200 | NVD → |
| CVE-2024-40898 | NVD → |
| CVE-2011-1176 | NVD → |
| CVE-2024-39573 | NVD → |
| CVE-2025-53020 | NVD → |
| CVE-2023-44487 | NVD → |
🔴 Security scanning identified 39 vulnerability entries on this host. This volume strongly suggests severely outdated software. Consult NVD advisories for details.
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.
157.20.32.165 has been assigned a threat score of 220/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:
IP address 157.20.32.165 has been traced to Jakarta, Indonesia, operating on the network of PT Intercloud Digital Inovasi. Our threat detection systems have flagged this address based on observed malicious behavior patterns. During its 1-day observation window, we recorded 3 hostile requests from this IP — roughly 3 per day on average. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The dual attack vectors of User-Agent Anomaly combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. Our records show 101 malicious IPs originating from Indonesia, positioning it as a significant contributor to global threat activity. At 220/100, this is an extremely high-risk address. All traffic should be considered hostile.
This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.
Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.
Analyzing attack patterns at the AS (Autonomous System) level reveals which networks harbor the most malicious activity. Some ASes have abuse rates orders of magnitude higher than average, indicating lax enforcement of acceptable use policies.