ABUSE.MOM
THREAT REPORT

IP Threat Report
202.180.20.138

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 09:36:40
First seen: 2026-02-26 07:00:04
Last seen: 2026-03-27 06:00:07
103

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 103/100. Total malicious requests observed: 2.

DANGER_PATHMETHOD
01

Geolocation & Classification

IP Address
202.180.20.138
Type
Residential
Country
🇮🇩 Indonesia
City
Jakarta
ISP
PT. HIPERNET INDODATA
Organization
Hypernet
Autonomous System
AS38758 PT. HIPERNET INDODATA
Hit Count
2
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger medium hits: 2Medium-risk: admin panels, config files+20
POST requests presentBehavioral anomaly detected by automated analysis+8
Σ = 103
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-02-26 07:00:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 3 (+75), Danger medium hits: 2 (+20), POST requests present (+8)
2026-03-27 06:00:07
Last malicious request observed
Total score reached: 103/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

PT. HIPERNET INDODATA
AS38758 · 🇮🇩 Indonesia
06

Recommendations

Actions taken & recommended

  • IP 202.180.20.138 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

⚙️ General Security

Add 202.180.20.138 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (1)
PortServiceRiskDescription
1723PPTPLowService on port 1723

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
Spamhaus ZEN

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

202.180.20.138 has been assigned a threat score of 103/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

📊 Threat Analysis

Threat intelligence analysis has linked 202.180.20.138 to malicious activity originating from Jakarta, Indonesia, operating on the network of PT. HIPERNET INDODATA. The address has been under observation since its initial detection. During its 28-day observation window, we recorded 2 hostile requests from this IP — roughly 0.1 per day on average. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. With 101 flagged addresses, Indonesia represents a significant presence in our threat database. At 103/100, this is an extremely high-risk address. All traffic should be considered hostile.

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.

11

Related Threats

🇮🇩 Top threats from Indonesia

157.15.40.88 (340)203.175.125.130 (340)157.15.40.93 (340)157.15.40.62 (340)157.15.40.89 (340)View all →

🏢 Same network: AS38758

View all →
12

Security Intelligence

💡 Server-Side Request Forgery (SSRF)

SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.

💡 Network Segmentation Benefits

Proper network segmentation limits the blast radius of breaches. Even if attackers compromise one segment, properly configured network boundaries prevent lateral movement to critical systems, databases, and administrative interfaces.

🔍 Check Any IP Address

Share this report: